# 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 and configure languages and translation triggers.
related:
  links:
    - /docs/integrations/mintlify/guides/translating-content
    - /docs/integrations/mintlify/guides/managing-translations
    - /docs/integrations/mintlify/guides/using-translated-content

---

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 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 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 **Project > Integrations > Catalogue**.
2. Connect GitHub and authorise 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 are 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 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).

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

Setup initiated from **Project > Automations** creates a locale-prefixed layout for every language, including the source locale. For example, English source pages are served under `/en/...`.

Existing Projects configured to hide the source locale keep serving source pages at their original paths. That behaviour is recorded in the generated `gt.config.json`; see the [configuration reference](/docs/integrations/mintlify/reference/config#options).

The layout changes how Locadex restructures files and `docs.json` navigation. Review the setup pull request before merging.

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