Strings
Strings are wording that belongs to the whole site rather than to one page: button labels, form messages, navigation items.
They live under Strings, grouped into namespaces, one row per key with a column per language.
| Key | English | Portuguese |
|---|---|---|
common.buttons.save | Save | Guardar |
forms.email.invalid | Enter a valid email. | Introduza um email válido. |
Click a cell, type, click away. It saves.
List values
Some strings hold a list rather than one line — a set of bullet points, for instance. Those show as a List chip instead of a text box; click it to edit the items.
A key that is a list in one language is a list in every language. A language that has not been translated yet shows Not translated, and opening it gives you the structure of a language that does have it, with the original text in place to translate over.
Text on a page
Copy that belongs to one page (its headings, body, FAQ, pricing cards, image alt text, the page title and description search engines show) is translated under Translate.
A page keeps one layout for every language. Its images, links and sections are shared, and only its words are translated. Change the layout once and every language follows.
Translate opens on the worklist: every page and how far it is in the language chosen at the top right. Choose a page and each piece of text is shown with the source beside it. Type the translation, click away, and it saves.
Which text is offered is decided by the content model: a field set to Separate value per language is translated. Settings, links and identifiers are not, because they are the same in every language.
Saving, and going live
A translation is saved into the page's draft, exactly like an edit to the page. Visitors see it once the draft is submitted and published in a release, and not before. Translating a privacy policy goes through the same review as rewriting it.
While a page is waiting for review it cannot be changed, translations included.
When the source changes
Each translation remembers the text it was made from. When someone changes that text in the source language, the translation is marked To review.
It still shows on the site until it is updated, because a page that switches language halfway through a paragraph is worse than one a little behind its source. If the change did not alter the meaning (a typo, a comma), choose Still correct and the mark clears without retyping anything. Saving the source with the same words does not mark anything.
Rich text
Long text such as a legal page is edited as HTML. A translation must link to exactly the same places as the source, or it is refused: the release checks the source's links, and nobody would check new ones. Placeholders such as {count} must be kept too.
Which one to use
Use strings for wording that repeats across the site, and page text for wording that belongs to one page. A heading used on one page only should not be a string.
What is not here yet
Being straight about the current limits:
- Rich text is translated as HTML in a text box, not in a visual editor.
- A long field (a whole legal page body) is one piece. Changing one sentence of the source marks the whole field To review.
- Strings: plural forms and references between messages are stored and delivered correctly, but nothing checks them. If a translation loses a placeholder such as
{count}, you will see it on the page rather than being warned here.