# General Translation Integrations: Using translated content
URL: https://generaltranslation.com/en-US/docs/integrations/mintlify/guides/using-translated-content.mdx
---

title: Using translated content
description: How does General Translation set up multi-language navigation, routing, and redirects in your Mintlify docs?
related:
  links:
    - /docs/integrations/mintlify/guides/translating-content
    - /docs/integrations/mintlify/guides/managing-translations
    - /docs/integrations/mintlify/guides/configuring-mintlify

---

# Using translated content

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.

## Multi-language navigation [#navigation]

Locadex converts your `docs.json` navigation into Mintlify's multi-language 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 (for example, `/es/...`). Whether your default language is served with or without a locale prefix depends on the **Hide default locale in URL paths** setting you chose during setup:

- **Hidden** (default): default-locale pages keep their existing paths, and only translated languages are prefixed.
- **Shown**: every language, including the default, is served under a locale prefix.

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

## Redirects and localized links [#redirects]

Locadex generates redirects in `docs.json` so existing links keep resolving after the navigation is restructured. It also localizes internal links, static URLs, and relative asset references so readers stay within their language while browsing.

## 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 normal 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