Languages and translations
Two different things are translated, and they work differently.
| What | Translated how |
|---|---|
| The interface — buttons, labels, messages | Installed language catalogues |
| The content — records, terms, menus, media | Per record, by an editor |
Interface language
Install a language and the back office, the ERP and the public channel speak it. The source strings are English throughout — that is the base language of the product, not a default nobody changed.
Content translation
A record has a translation per language. Each has its own values, its own publication state and its own address, while remaining the same record.
Taxonomy terms translate too, which matters more than it sounds: category names appear in listings, in breadcrumbs, in reference fields and in menus. A term that is not translated shows up in the original language in every one of those places.
A silent fallback is worse than a missing translation
If a visitor reading in Slovak sees an English label with no indication that it is the original, they cannot tell it apart from a bad translation. Every public rendering goes through the same lookup, and a place that does not is a defect worth reporting.
Adding a language
Back office → System → Languages. Adding one creates the translation tab on every content type and every vocabulary; nothing else has to be configured.
Translating documentation
Documentation pulled in by Sourcebook is
translated in the repository — either page.sk.md beside the original or a
sk/ directory. A translation is the same page in another language and
shares the original's tags, version and place in the tree.