Localise your Markdown docs

Translate every Markdown file in your docs in minutes with General Translation

Get Started

content/docs/en-US/platform/locadex/quickstart.md

  1. ---
  2. title: Quickstart
  3. description: Use Locadex, the AI agent which connects your codebase, translations, and content sources. It’s the fastest way to run General Translation's full-stack localization.
  4. ---
  6. Locadex is the General Translation AI agent which connects your codebase, translations, and content sources.
  8. After setup, Locadex can configure your project and automatically translate it into the languages you choose.
  10. Locadex currently supports **Next.js**, **Mintlify**, **Fern**, and **Docusaurus** projects, along with React applications built with Vite, Gatsby, Redwood, React Router, TanStack Start, Bazel, esbuild, Rollup, Rolldown, or webpack.
  12. ## How Locadex works [#locadex-works]
  14. Locadex works inside your GitHub repository and automatically opens or updates PRs with generated changes. Three automation templates keep your localization up to date:
  16. - **Generate code** wraps source code with the right internationalization (i18n) library calls, such as `t()` and the `T` component.
  17. - **Generate translations and push** translates source content into every target language and updates translation files.
  18. - **Keep locales in sync** updates project files when languages are added or removed.

npx gt translatees, fr, ja

Localise your docs into any language, in just a few steps

Production-grade translations of your full documentation site in just minutes

  1. Run the set-up wizard

    Run npx gt init in your docs repo, choose Markdown as your file format, and pick your target languages.

  2. Point it at your files

    The wizard adds one glob for your .md files to gt.config.json, with a [locale] folder for each language. There is no code to change.

  3. Translate and ship

    Run npx gt translate and the CLI writes a translated copy of every file, with all Markdown syntax and formatting preserved. Commit the translated files and publish them with your docs site.

How do I keep translations up to date with every deployment?

Transcript

In Montreal, your French page shows the line you added this week in English. Your build script runs next build alone, so the line was never translated. General Translation keeps translations current when your CI runs npx gt translate before the build. Create an API key for CI with the file, context and translation queue permissions. Store it and your project ID as secrets in your CI provider. Add npx gt translate to your build script, before the build command. Run that build on every push to main, for example with a GitHub Actions workflow. Each build then ships current translations in Spanish, Japanese and French.

Trusted by the world’s best companies

General Translation builds the full localisation stack for a frictionless developer experience

  • 11+ locales across dashboard, landing page, iOS

  • 14+ locales across web, docs

  • 47+ locales across platform, docs

  • 2+ locales across web, iOS, Android

  • 7+ locales across web, GTM

  • Open-source i18n libraries
  • Context-aware translation
  • Team review platform
  • Content integrations
  • Locadex agent

Native-level translations with full context

The highest-quality translations that understand your product and check against your entire docs site

Context at every layer

Translations follow your voice and style rules, and understand the context and logic of your product.

Consistent across every page

Each page is proofread, compared with your source, and checked for consistency against your other pages.

Review and edit with your team

Every line is editable in the Dashboard, with side-by-side languages, history, and comments.

Continuous localisation as you ship updates

Run npx gt translate before your docs build, and each run translates only what changed, so every deploy ships in every language

  1. Push a docs change
  2. Your build runs the CLInpx gt translate
  3. Only what changed is translated
  4. Deployed in every language

Connect and localise your full product suite

General Translation connects your code, content, translations, and review in one platform

Docs

Frequently asked questions

What’s the difference between translation, internationalisation, and localisation?

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. For Markdown docs, internationalisation is the folder per locale your site serves, translation is each file in each language, and General Translation handles the whole localisation workflow, continuously.

Looking for translation specifically? See Markdown translation.

Can’t I just translate my docs with an AI API?

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 in your repo with your build. 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.

How long does set-up take?

Minutes, not a migration. Run npx gt init, choose your languages, and run npx gt translate; 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.

Which languages are supported?

Any of the 120+ locales General Translation supports, including regional variants like pt-BR and zh-Hant and right-to-left languages like Arabic and Hebrew. List them in gt.config.json and add more whenever you like. See the supported locales.

Will translations stay updated as my docs change?

Yes, continuously. Run npx gt translate in CI before your docs build. It translates only content whose source changed and keeps your local edits, so every release ships in every language with the change that introduced it.

Will the translations match our voice and terminology?

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.

Will translation break my Markdown formatting?

No. The CLI keeps all Markdown syntax and formatting in every translated file, and explicit heading IDs such as {#id} stay attached to their headings.

What does it cost?

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.

Bring your Markdown docs to a global audience

Start for free with no monthly fees

Get StartedGet a demo