GoCommerce’s admin panel moves to /dash

The GoCommerce admin panel has new addresses. Every store screen now sits under /dash. The screens you use before you have a session — sign-in, password reset, accepting an invitation — sit under /admin/auth.

Old bookmarks and links already emailed still work. They redirect, and they keep their query string. The one exception is a link to a module’s screen, covered below.

The API does not move. Nothing that calls /api has to change.

Where things are now

The panel is still served at the root of the store’s address, by the same binary.

Why

The KitCommerce admin keeps its screens under /dash and its sign-in at /admin/auth/login. GoCommerce now uses the same scheme, so a person who works in both finds orders at /dash/orders in each.

Most screens keep GoCommerce’s own names, so the two panels share the shape of an address, not every address. A few screens were renamed in the move; the table below lists them.

The move was also done first, before custom roles and the planned store switcher, so that later work lands on the final addresses.

What happens to old addresses

The panel redirects old screen addresses to their new ones. The query string is kept, and so is the part after #. So /orders?status=open lands on /dash/orders?status=open.

If you are signed out, you sign in first and then land on the screen you asked for. The panel carries that screen in a next value and follows it only to a /dash address on the same store. Anything else lands on /dash.

The live demo link on this site still fills in the demo account. The redirect to sign-in keeps the part after #, where those details travel.

Which status code

The code asks for a 308, a permanent redirect. But the panel is a single-page app that never renders on the server, so the redirect happens in the browser. The engine answers the old address with the panel’s page and a 200. Then the panel’s router moves to the new address.

A person with a browser never notices. A tool that does not run JavaScript — curl, an uptime check, a link checker — sees a 200 at the old address, not a 308.

The one redirect the server sends itself is the oldest. /_ and /_/… answer with a 301 to /, and drop the rest of the path.

What to check

What it does not change

• The API. Every path under /api, a module’s /x/ routes, /health, /doc (the OpenAPI document) and /docs (the API reference) stay where they were. The only engine code that changed is the two links it writes: invitations and staff password resets.
• The other apps in the panel. /platform, the platform console, and /portal, the trade portal for business buyers, do not move.
• The screens. Only their addresses moved. What each one shows and does is the same.

How the mapping is held in place

One function, dashPath in admin/src/lib/paths.js, holds the whole mapping from old address to new. The same function drove the rewrite of the panel’s own links and now runs the redirects, so the two cannot disagree.

Tests pin the renames and the paths that must never move: the panel’s files, /api, /docs, /platform and /portal. They also pin the rule that next never leaves /dash. Another test fails if any link in the panel’s source still points at an old address.

Further reading

• The GoCommerce admin — every screen, captured from one seeded store.
• GoCommerce — the engine in full: its modules, its admin and the one-command start.
• Updates — every change to GoCommerce, as it ships.
• How the panel is served — docs/admin-panel.md in the repository.