Published sites can offer translated public pages.
Configure languages
In publishing settings, choose the content's original language and the additional languages to offer. The original language is never machine-translated. It is the source used for translations.
Reader experience
Visitors can switch languages from the public site. Dokki carries the selected language through internal published-site links so readers do not lose their language while navigating.
How translation updates
When you publish or commit a document, Dokki queues translation jobs for enabled non-default languages. Site navigation strings are queued too, so page names and home text can update with the content.
Translations are asynchronous. A freshly committed page may show the original language until the translation worker finishes.
Cached translations
Dokki stores translated output with content hashes so old translations are not reused for changed content. Republish or commit changes when the source document should generate a fresh translation.
What gets translated
Document body text and public-site strings are translated. Tables and artifacts can appear in navigation and published pages, but their internal structured content may not receive full body translation in the same way documents do.