Locales and translations
Every project declares its languages as a list of locale codes (for
example en, nl, es). Fields marked translatable store one value per
language, keyed by locale code; all other fields hold a single value shared
across languages.
Editing translations
Section titled “Editing translations”In the dashboard, a translatable field shows an input per language. A
required translatable field needs a value in every language before the
document saves.
In the API and the SDK
Section titled “In the API and the SDK”Translatable fields come back as a record keyed by locale code, and the
generated types reflect that: a translatable title is typed per language,
not as a bare string, so a missing translation surfaces in your code instead
of on the live site.
Adding a language
Section titled “Adding a language”Languages are set per project. The number of locales depends on your plan (see pricing); mail [email protected] to add one to a running project. Existing documents keep their current translations, and translatable fields show an empty input for the new language until an editor fills it.