Documents
A product isn't only labels and buttons. Articles, guides, and pages need translating too. Link a content document from the CMS and localize the whole thing, per language, with the same care and the same workflow.
Link & translate
Point a localization project at an existing content document and it becomes the source. Each language gets its own translated version, stored as structured content that mirrors the source — not a flat copy — so formatting and structure carry across intact.
Round-trip
Translators often live in their own tools. A document can be exported to HTML, translated wherever your team works, and imported straight back — the structured content rebuilt from the HTML, no copy-paste, no lost formatting.
Two units, one system
A project holds both. Strings cover the interface; documents cover the content. Linking a document doesn't shred it into strings — it stays whole, translated as a document, while your UI strings stay strings.
Keys, placeholders, and plurals — the interface layer, translated key by key.
Whole content items — articles, guides, pages — translated as a structured whole.
Keep exploring