Skip to content

Console overview ​

The console at console.extension.dev is where a repository becomes an extension with builds, releases and store submissions. Reach for this page when you are signed in and want to know where everything is.

Quick start ​

https://console.extension.dev/<workspace>/<repo>

The project opens on its Overview tab, and the other four tabs hang off that address as /activity, /builds, /releases and /submissions.

How it works ​

Two layers ​

The console has two layers. Global routes belong to you. Everything else belongs to a workspace, which answers at /<workspace>.

Three global addresses hand off to another surface. /import, /templates and /new/templates land you on the surface that owns them, which is why the address bar changes.

Workspace settings ​

Workspace settings live at /<workspace>/settings in six sections, each at its own address: Workspace, Members, GitHub connections, Plan and limits, Usage and Danger zone. Plan and limits prints what the plan allows beside what the workspace has spent. Usage prints what those builds cost. See Usage and limits.

A project ​

A project lives at /<workspace>/<repo> under a five-tab strip. Overview is the project root, and the other four hang off it. A sixth address, /checks, answers without a tab: the console has no verdict to show there yet.

Project settings are a dialog with its own address, /<workspace>/<repo>/settings/<section>. Every section is linkable, so you can send a teammate straight to the one that matters. /settings on its own redirects to general, and closing the dialog returns you to the project overview.

Visibility decides who can open this project's builds. It offers public and private, and only workspace owners and admins can change it. The section lists what the change means before you confirm it, and it warns you when the setting saved but the public pages have not caught up. Visibility also decides whether a share link carries a token. See Publish a build and Public project pages.

The lifecycle ​

Every project moves through the same four verbs.

Connect. /import or /new links a repository, and the template gallery behind /new/templates creates one from a template. The console reads the manifest and configures a build per declared browser.

Build. Push a commit. The project builds one artifact per browser and records it under Builds. Open /builds/<buildId>/<browser> for the artifact, its logs and its integrity record.

Release. A build becomes a release at /releases/new, in a channel. Every project starts with two, preview and stable. The form shows the build's version as a fact and never changes it. preview takes any build; stable and every channel you create take a build made for Stable. When the build was not, the form offers Rebuild for Stable · 1 build. Until something lands on stable, the Releases tab reads Nothing on Stable yet. Release a build here, or submit one to a store.Create release dispatches one release run per browser and hands you to the release page at /releases/<releaseId>, where the release id is the channel name. Its Rollout section reports each browser's release run and refreshes on its own while a run is in flight. The page also holds the channel's current build and the timeline of what entered it. The Roll back control sits in its header. Owners see it once the channel has an earlier build to return to. Members see it disabled, with a note that only owners roll back. To ship a version no build carries yet, Bump version at /releases/bump opens a pull request that raises the manifest version and reads Pull request opened from GitHub's answer. See Releases.

Submit. A build that passed goes to the stores from the Submissions tab. A submission takes a build made for Stable, and stable moves for that browser once the store records the submission. Each submission is tracked at /submissions/<store>/<submissionId> until the store answers. Credentials are held by the project under Store publishing, never by your machine.

Reference ​

Global routes ​

RouteWhat it does
/Sends you to your workspace. Signed out, it sends you to the home page, which brings you back once you sign in
/newPick a repository to connect, with doors to the template gallery and the code app above the picker
/new/templatesBrowse the template catalog. Answered by templates.extension.dev
/new/codeOpen the code app when that lane is on. Otherwise it returns you to /new
/importConnect a repository you already have. Answered by www.extension.dev/import
/templatesThe same door as /new/templates
/helloCreate a workspace: name, description and developer URL
/sharesSends you to your workspace home. Share links live in project settings under share-links
/founders-noteHands you to the one copy of the note on www.extension.dev
/bulk-deleteOperator-only cleanup of projects and their mirrors

Workspace settings ​

SectionAddress
Workspace/<workspace>/settings/workspace, also the bare /settings
Members/<workspace>/settings/members
GitHub connections/<workspace>/settings/connections
Plan and limits/<workspace>/settings/plan
Usage/<workspace>/settings/usage
Danger zone/<workspace>/settings/danger

Project tabs ​

TabAddressContents
Overview/<workspace>/<repo>The manifest, configured browsers and current state
Activity/activityWhat happened, in order
Builds/buildsOne row per build, one artifact per browser
Releases/releasesBuilds released to a channel
Submissions/submissionsStore connections and submissions

Project addresses ​

AddressOpens
/builds/<buildId>One build
/builds/<buildId>/<browser>One browser's artifact, logs and integrity record
/releases/newThe new release form. It releases a build that exists. A ?version= link with no build sends you to /releases/bump
/releases/bumpThe Bump version page. It opens a pull request that raises the manifest version
/releases/<releaseId>One channel's release page, with its Rollout section
/submissions/<store>One store
/submissions/<store>/historyEvery submission to that store
/submissions/<store>/newA new submission
/submissions/<store>/<submissionId>One submission
/submissions/newSends you to project settings, Store publishing
/stores...Old addresses. Each redirects to its /submissions twin
/checksAnswers without a tab
/onboardRead-only. Prints the steps an operator runs to attach a repository the platform holds no project for

Project settings sections ​

SectionAddress
general, team, environment, build, deployment, github, channels, stores, visibility, access-tokens, share-links, danger/<workspace>/<repo>/settings/<section>

When it fails ​

  • A workspace route says it is not available to you. You are signed in to an account that is not a member. Check Members from an account that is.
  • A push builds nothing. The GitHub connection lapsed. Reconnect under project settings, github.
  • A release page shows no rollback control. The channel has nothing behind its current build. See Releases.
  • A link to /releases/new opened Bump version. The link carried a version and no build. The release form reads the version from the build, so a version alone asks for a bump, and the link lands on /releases/bump with that version and channel.
  • A submission sits in review. That wait belongs to the store. The submission page shows the last state the store reported.
  • A submission reads Unknown. The run ended without a state the console could read from the store. It is not a submission that succeeded. Open the run and read the failure. See Publishing.
  • A stranger cannot open a build page you expected to be public. The project is not declared public, or the public pages have not caught up. Check Project settings, Visibility. See Public project pages.

Next ​