Console overview
You signed in at console.extension.dev and want to know where everything is. This page is the map: every route the console answers, and the lifecycle those routes carry a project through.
The shape
The console has two layers. Global routes belong to you; everything else belongs to a workspace.
| Route | What it does |
|---|---|
/new | Create a project from a template |
/import | Connect a repository you already have |
/templates | Browse the template catalog |
/shares | Every preview link you have minted, live and dead |
A workspace answers at /<workspace>. Its settings live at /<workspace>/settings in five sections: workspace, members, connections, usage, and danger.
A project
A project lives at /<workspace>/<repo> under a five-tab strip:
| Tab | Contents |
|---|---|
| Overview | The manifest, configured browsers, and current state |
| Activity | What happened, in order |
| Builds | One row per build, one artifact per browser |
| Releases | Builds promoted to a channel |
| Stores | Store connections and submissions |
Each tab is a path. A build drills to /builds/<buildId>/<browser>. Releases list at /releases, mint at /releases/new, and open at /releases/<releaseId>. Stores list at /stores, connect at /stores/new, and a submission opens at /stores/<store>/submissions/<submissionId>.
Project settings open as dialogs over whatever route you are on, so configuring never loses your place. The sections: general, team, environment, build, deployment, github, channels, stores, visibility, access-tokens, and danger.
The lifecycle
Every project moves through the same four verbs.
Connect. /import links a repository, or /new 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 hash.
Promote. A build the team agrees on becomes a release at /releases/new, bound to a channel. Channels are configured in project settings under channels.
Submit. A released build goes to the stores from the Stores tab. Each submission is tracked at /stores/<store>/submissions/<submissionId> until the store answers. Credentials are held by the project under project settings, stores, never by your machine.
When it fails
- A workspace route 404s: you are signed in to an account that is not a member. Check
/<workspace>/settingsunder members from an account that is. - A push builds nothing: the GitHub connection lapsed. Reconnect under project settings, github.
- A submission sits in review: that wait belongs to the store. The submission page shows the last state the store reported.
Next
- Usage and limits for what the platform meters
- Access tokens to drive these routes from CI
- Share an unpublished build for review when a build needs eyes before it needs a release