This guide takes you through localizing a Doxbrix project: enabling locales, translating content per locale, and publishing a multi-language site where readers a...
This guide takes you through localizing a Doxbrix project: enabling locales, translating content per locale, and publishing a multi-language site where readers a...
This guide takes you through localizing a Doxbrix project: enabling locales, translating content per locale, and publishing a multi-language site where readers automatically get their language. By the end you'll have docs that serve a global audience.
Who this is for
Teams expanding documentation to readers in more than one language — whether translating a whole site or just key pages.
Prerequisites
- A Doxbrix project with content in your default language.
- Admin access to enable localization.
Step 1 — Plan your locales
Decide which languages to support and pick a default. Consider where your readers actually are (check analytics reader locales) and which content matters most to translate first.
Step 2 — Enable localization
Go to Settings → Project → Localization.
Set the Default language and a URL structure (subfolder, subdomain, or query parameter).
In Enabled locales, add each language you want to support and label it.
Turn on Clone structure for new locales so new languages mirror your default-language navigation — translators get ready-made page slots.
See Multi-language for the underlying model.
Step 3 — Translate content
Each locale starts with empty (or cloned) page slots that you fill per locale. In the editor's top bar, the locale switcher (shown once more than one language is enabled) selects which language you're editing.
- In the editor — switch to a locale and write that language's version of each page. The Writing Copilot can help rewrite or rephrase text as you go.
- As code — for an external translation pipeline, pull content with Git sync, translate the
.mdxfiles in your tool of choice, and let the sync bring them back.
Step 4 — Review translations
Translated pages flow through the same review process:
- A reviewer fluent in the language checks accuracy and tone.
- Verify that navigation labels read naturally.
- Confirm code samples and product terms weren't translated when they shouldn't be.
Step 5 — Publish and verify
Publish translated pages as you would any content.
Visit your site — readers now see a language switcher. Its placement is set in Settings → Project → Reader Experience.
Confirm locale alternates are declared so search engines serve the right language (see SEO & site layout).
Keep translations current
When you update the default-language version of a page, revisit its translations so they don't drift. Translate your highest-traffic pages first and expand from there — the fallback keeps untranslated pages readable in the meantime.