# General Translation Integrations: Configuring Mintlify
URL: https://generaltranslation.com/en-US/docs/integrations/mintlify/guides/configuring-mintlify.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: How to connect a Mintlify documentation repository to General Translation and configure languages and translation triggers.

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 path; this guide covers the configuration options in more detail.

The integration runs on [Locadex](/docs/platform/locadex/quickstart), so its repository and automation are configured from **Project > Integrations** and **Project > Automations** in the Dashboard.

## Before you start [#before-start]

- A General Translation [project](/docs/platform/dashboard/get-started).
- A GitHub repository with a valid Mintlify project. Locadex checks that the repository has a `docs.json` whose `$schema` points at 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 **Project > Integrations > Catalog**.
2. Connect GitHub and authorize the General Translation GitHub App on the repository that contains your Mintlify docs.
3. Open **Project > Automations** and choose **Generate translations and push**.
4. Select the repository, target directory, and **Mintlify** framework.

## Set the target directory [#target-directory]

If your `docs.json` is at the repository root, set **Target directory** to `.`. If your docs live in a subdirectory, such as in a monorepo, set **Target directory** to that path so Locadex operates on the right folder. (See [Using Locadex in a monorepo](/docs/platform/locadex/guides/using-in-monorepos)).

## Choose languages [#languages]

Set the **source 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 onto 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).

## Choose the default-locale URL layout [#default-locale-url]

When you run setup from **Project > Automations**, **Hide default locale in URL paths** is on by default. Keep it on to serve source pages at their existing paths and place only translated pages under locale-prefixed paths.

Turn it off to place every language under a locale-prefixed path. For example, English source pages then move under `/en/...`.

Your choice is recorded in the generated `gt.config.json`. It changes how Locadex restructures files and `docs.json` navigation, so review the setup pull request before merging. (See the [configuration reference](/docs/integrations/mintlify/reference/config#modes)).

## Set how translations run [#triggers]

Locadex opens or updates pull requests with its changes. It reuses an open PR for the same automation branch and opens a new one after the previous PR is merged or closed.

New translation automations default to **A pull request changes**, with **Auto-merge** off. Choose **A commit is pushed** to translate changes after they reach the target branch, and turn on **Auto-merge** when reliable required checks can protect the branch. (See [Auto-merging Locadex PRs](/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

## Sitemap

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