# General Translation Integrations: Using translated content
URL: https://generaltranslation.com/en-GB/docs/integrations/mintlify/guides/using-translated-content.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: How to serve translated Mintlify docs with multilingual navigation, locale routing and redirects.

Once the setup pull request is merged, your Mintlify site serves every language you selected. This guide explains what the integration changes in your project so readers land on the right language.

## Multilingual navigation [#navigation]

Locadex converts your `docs.json` navigation into Mintlify's multilingual structure, with one navigation entry per language. Mintlify uses this to render a language switcher and to build the per-language page tree. If your navigation lives in a separate file referenced with `$ref`, Locadex writes the changes there and preserves the `$ref` in `docs.json`.

## URL routing and the default locale [#routing]

Each language is served under its own locale segment, such as `/es/...`. Setup started from **Project > Automations** also prefixes the source locale, such as `/en/...`.

Existing projects may have a generated configuration that hides the source-locale prefix. In that layout, source pages keep their original paths and only translated languages are prefixed.

(See the [configuration reference](/docs/integrations/mintlify/reference/config) for what each mode produces).

## Redirects and localised links [#redirects]

In show-default-locale mode, Locadex localises the source and destination paths of existing top-level redirects in `docs.json`. It does not create new redirect entries. Locadex also localises internal links, static URLs and relative asset references so readers remain in their language while browsing. Links to pages without a translation remain on the source URL.

When you run the CLI directly, enable [`options.mintlify.localizeRedirects`](/docs/integrations/mintlify/reference/config#localized-redirects) to add per-locale copies of source-locale redirects when a source page is renamed or removed in the same translation run. Configs generated during setup omit this opt-in setting. The CLI leaves existing entries unchanged and skips locales without a translated destination.

## OpenAPI pages [#openapi]

When your repository contains OpenAPI 3.x specifications in JSON or YAML, Locadex registers the translated specifications in the Mintlify configuration. Mintlify can then serve each specification from its locale path.

OpenAPI registrations outside `navigation.languages` remain attached to the source specification. Registrations inside a target language's navigation point to that locale's translated specification.

## Deploy [#deploy]

The integration only changes files in your repository, so publishing works exactly as it does for any Mintlify project: merge the pull request and let your usual Mintlify deployment build the site. No additional deployment step is required.

## Next steps

- /docs/integrations/mintlify/guides/translating-content
- /docs/integrations/mintlify/guides/managing-translations
- /docs/integrations/mintlify/guides/configuring-mintlify

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.