The dashboard is a React app served by the server on the same origin
as the API. It’s where translators do their work: browse a project and edit values inline.
The dashboard is Alpha. It covers the core editing loop; the limits below are real and
called out honestly.
Signing in
Open the server’s URL and sign in with an email and password. Every page except sign-in
requires a session and redirects you back to sign-in if it expires.
There is no sign-up or password-reset page yet — accounts are created out of band (see
Self-hosting → First user and organization).
Projects
The home page lists your organization’s projects and has a New project form. Creating a
project takes a name, a URL-safe slug, a source language, and a key format (nested
i18next-json, or flat with literal dots). A new project is empty until you
push source strings into it.
Browsing and editing a bundle
Open a project to reach its detail page. Pick a language and a namespace from the two
selectors, and the bundle loads as a Key → Value table (the header shows the slug and the
source language).
To edit, click a value, change it, and click away — the edit saves on blur. Each save
overwrites just that one value. If the server refuses (for example a case-collision or a
non-editable key), the reason is shown on the cell.
Managing tokens
The Tokens page lists the organization’s API tokens (safe
metadata only — never the secret). Owners and admins can also mint and revoke them; a
member sees the list read-only. A freshly minted token’s plaintext is shown once, with a
copy button, and is dropped from memory as soon as you dismiss it — so copy it immediately.
What the dashboard can’t do yet
- Only simple string values are editable. Non-string leaves (arrays, numbers) and
plural / context keys are read-only — the editor doesn’t understand them yet, so they’re
shown but not editable.
- No adding or deleting keys, languages, or namespaces — those arrive only through
push and i18next saveMissing.
- No organization or member management in the UI — no org switcher, invitations, or member
roles screen, and no sign-up.
These are the natural next steps; for now the dashboard is a focused inline editor on top of a
complete HTTP API. 
