Localise your documentation

Translation converts content from one language into another. Internationalisation (i18n) prepares your site to support multiple locales: routing, navigation, dates, and plurals. Localisation (l10n) is the umbrella: adapting the whole product for each locale, from the words to the formatting. On a docs site, internationalisation is the locale routing and multilingual navigation, translation is your pages in each language, and General Translation handles the whole localisation workflow, continuously.

Looking for translation specifically? See documentation translation.

For a one-off pass, yes. But shipping docs you can trust every week, in every language, takes a system around the model.

Your pages aren’t just text. MDX components, imports, and code blocks must come back exactly as written, frontmatter keeps its keys, and heading IDs like {#configure-client} stay attached so deep links don’t break.

Your docs are a site, not a page. Navigation needs a version per language, locale codes have to fit what your platform accepts, and “workspace” must translate the same way on page 1 and page 400 (and in your app, for which we also support localisation).

Your docs change every week. Each update should translate only what changed, keep your reviewers’ hand edits, and land as a pull request on the right branch. Adding a language later shouldn’t break the ones you have.

Multiple team members need control and visibility: see every line side by side with its source, history, comments, roles, and tone rules for each language.

General Translation runs all of this end-to-end. We handle thousands of localisation PRs for our customers, so they can focus on building a product the world loves.

Locadex sets up Mintlify, Fern, and Docusaurus projects and opens a pull request with the configuration and your translated pages. For docs built with anything else, the gt CLI translates Markdown and MDX files from a gt.config.json.

Minutes, not a migration. Connect your repository, choose your languages, and merge the pull request General Translation opens; translation runs at scale from there (Ramp translated 40,000 keys, millions of words, in a few minutes). You can also hand set-up to your coding agent with the Set-up for Agents button.

It depends on your platform. A Mintlify site can use every language Mintlify supports, and Markdown and MDX files translated with the gt CLI can use any of the 120+ locales General Translation supports.

Yes, continuously. Our Locadex agent runs on the pull-request, commit, or manual triggers you choose, translates what changed instead of the whole site, and delivers through a pull request, so every release ships in every language with the change that introduced it.

General Translation lets you set Custom Prompts with your tone and style, and a Glossary that pins product names and key terminology. Context is applied consistently across all of your translations, including your app, website, docs, slides, and design files.

No. Translation preserves MDX syntax and component structure while translating the human-readable content.

Usage-based billing with no seat charges and no subscriptions. $0 platform fee on Starter with unlimited projects, users, and languages, and a free allowance to start. See the pricing page for full rates.