Overview
Where a module lives between "I wrote some code" and "it's in the marketplace".
The developer portal is where a module becomes a product. Your code stays in GitHub; the portal handles everything around it — building it, running it somewhere private while you test, giving it a name, and eventually putting it in front of other people.
The dashboard
Your projects are listed with their status, whether the last build succeeded, the connected repository, and when they were last touched. You can search by name, filter by status, and sort by name, status, or when they were created or updated.
Gateways are listed separately below, as Gateways under a team organization — a gateway can never belong to your personal one, so nothing appears there. They have no repository and no build, so most of what's on this page doesn't apply to them — the search box narrows them too, but the status filter is a project-only idea.
The tabs
A project opens on seven tabs, roughly in the order you'll need them. Statistics and Logs show only to someone who can see statistics and logs on the module, and Inspector only to someone who can use the inspector.
Identity and settings. The display name, tagline, and icon; the version number; the GitHub
connection; and the Module ID — the @org/name your module is published under, which has to
be set before you can publish at all. The category is shown too, but it follows from what kind
of module this is, so there's nothing to choose.
Also here: User Secrets — no values — where you declare which credentials each user is asked for when they install, each one required or optional. That's a different thing from the bindings on the Deployments tab, which are your own static values; this list is the user's half.
The path through
Create the project
Pick Connect GitHub Repository, choose the repo, and name it. See creating modules.
Deploy to dev
From the Deployments tab. Your code builds and runs, reachable only by you.
Test with the Inspector
Call the tools. Read what comes back.
Set the Module ID
On the Overview tab. This is the marketplace name, and publishing is blocked until it's set.
Publish
Promotes the module to production and lists it. See publishing.
Steps two and three are a loop, and most of the work happens there. Publishing is deliberately a separate decision at the end rather than something that happens on every push.