# General Translation Integrations: Configuring Mintlify
URL: https://generaltranslation.com/en-GB/docs/integrations/mintlify/guides/configuring-mintlify.mdx
---

title: Configuring Mintlify
description: "How to connect a Mintlify documentation repository to General Translation: this guide covers choosing languages and setting how translations run."
related:
  links:
    - /docs/integrations/mintlify/guides/translating-content
    - /docs/integrations/mintlify/guides/managing-translations
    - /docs/integrations/mintlify/guides/using-translated-content

---

# Configuring Mintlify

Connect the GitHub repository that holds your Mintlify docs to General Translation, then choose your languages and how translations run. The [Quickstart](/docs/integrations/mintlify/quickstart) covers the fastest route; this guide covers the configuration options in more detail.

The integration runs on [Locadex](/docs/platform/locadex/quickstart), so it is configured from **Locadex > Agent** in the Dashboard, not from a package or a config file you edit by hand.

## Before you start [#before-start]

* A General Translation [Project](/docs/platform/dashboard/get-started) on a plan that includes the `locadex_workflows` feature.
* A GitHub repository containing a valid Mintlify project. Locadex checks that the repository has a `docs.json` whose `$schema` points to Mintlify. It rejects projects that still use the legacy `mint.json` (migrate to `docs.json` first) or that look like a Next.js app.

## Connect and link your repository [#connect]

1. In the Dashboard, open your Project and go to **Locadex > Agent**.
2. Click **Connect GitHub** and authorise the General Translation GitHub App on the repositories you want Locadex to access.
3. Select the repository that contains your Mintlify docs. Each Project links to one repository.

## Set the app root directory [#app-directory]

If your `docs.json` is at the repository root, leave the app root directory empty or set it to `.`. If your docs live in a subdirectory (for example, in a monorepo), set the app root directory to that path so Locadex operates on the right folder. See [Monorepos](/docs/platform/locadex/guides/using-in-monorepos).

## Choose languages [#languages]

Set the **default locale** (the language your docs are written in) and the **target languages** to translate into.

Mintlify supports a fixed set of language codes, and General Translation maps your chosen locales to them. Only locales that map to a supported Mintlify language can be used. See [Locales](/docs/integrations/mintlify/reference/locales).

To change languages later, see [Managing translations](/docs/integrations/mintlify/guides/managing-translations).

## Hide the default locale [#hide-default]

Use the **Hide default locale in URL paths** toggle to control how your source language is served:

* **On** (default): your default-locale pages remain at their existing paths (no locale prefix), and only translated languages get a locale prefix.
* **Off**: every language, including the default, is served under its own locale prefix.

This choice changes how Locadex restructures your files and `docs.json` navigation. See the [configuration reference](/docs/integrations/mintlify/reference/config) for exactly what each mode produces.

## Set how translations run [#triggers]

Locadex opens pull requests for every change it makes. For documentation repositories, it runs on new commits to your default branch and can merge translation pull requests automatically once checks pass, so your docs stay translated without any manual steps. You can review these settings and change the trigger or auto-merge behaviour at any time — see [Auto-merge](/docs/platform/locadex/guides/auto-merging-prs).
## Next steps

- /docs/integrations/mintlify/guides/translating-content
- /docs/integrations/mintlify/guides/managing-translations
- /docs/integrations/mintlify/guides/using-translated-content