The project overview
See where a project stands, language by language, and go straight to the work that is holding it up.
The overview is the page a project opens on. It answers "where is this project up to?": how much is translated and approved in each language, what is running, and what to do next. Everyone who can open the project sees it.
The header
Under the project name, a line gives the source language, the number of target languages and the number of keys, for example en → 3 locales · 1,204 keys. When the project reused translations from memory this month, it adds how many words, as in "90 words from memory this month".
On the right, Open editor opens the editor, and Deploy → opens the project's releases, where you publish a locale. A project with no keys yet shows Add source strings → instead, which opens the setup page where you import content.
The pipeline
A strip of five figures sums up the project's work, left to right. Each one opens the place where that work is done.
| Figure | Counts | Opens |
|---|---|---|
| source | Source strings (keys) in the project | The project |
| translate | Target strings that have a translation, of all target strings | The editor, filtered to untranslated strings |
| review | Translated strings flagged as needing a check by a person | The editor, filtered to strings that need checking |
| approve | Translated strings a person has approved | The quality dashboard |
| deploy | Target languages whose next publish would carry every string the project expects them to hold | Releases |
Locales
The Locales table has one row per target language. A sentence at the top totals the project, for example "1,040 of 1,200 translated, 610 approved, 12 need checking". Rows are sorted by what blocks shipping: languages with strings that need checking first, then the least translated.
| Column | Shows |
|---|---|
| Locale | The language name and its tag. |
| Coverage | A bar of translated strings, and the same sentence for this language alone. |
| Approved | Approved strings, out of the language's total. |
| Quality | How many strings need checking, or clear. |
| State | What is happening to the language now: "GLOSSA is translating, started 4 minutes ago", "queued to translate", "all keys translated", or how many strings are not translated. If the last run for the language failed, the state links to that run so you can see which strings failed. |
| Next | The one thing to do next in this language, as a link into the editor. |
The Next link is:
- Review when the language has strings that need checking and you can review it. It opens the editor on exactly those strings.
- Fill gap when strings are untranslated. It opens the editor on the untranslated strings.
- Approve when everything is translated but some strings are not approved yet, and you can review. It opens the editor on the strings waiting for approval.
- Import when the project has no source strings yet.
Select anywhere on a row to follow its Next link. Remove at the end of a row deletes that language; see Remove a language.
Add a language
Below the rows, Add a language adds a target language: search by name, native name or tag, then select Add. See Add a target language.
What to do next
The foot of the Locales table names the single most useful next step for you, worked out from the project's real state. While the project is being set up, it is the first unfinished setup step (add a target language, bring in source strings, run the first translation) with Continue setup. After that, it points at strings waiting for review first, then untranslated strings, with Open editor. When nothing is left that you can act on, it says nothing.
Recent activity
Recent activity lists the latest changes to the project. Translation runs opens the list of every AI translation run, with its counts and any strings that failed. View all opens the full project activity.
If something looks wrong
- "No target languages yet": the project has a source language but nothing to translate into. If you have the Developer role or above, add one in the row below.
- Every language reads "waiting for source strings": the project has no keys yet. Select Add source strings →.
- Add a language and Remove are not shown: managing languages needs the Developer role or above, with access to the language.
- Review or Approve is missing on a row: you cannot review that language. Members with the Reviewer or Admin role, and account Owners, can.