# General Translation Integrations: Supported content
URL: https://generaltranslation.com/en-US/docs/integrations/mintlify/reference/supported-content.mdx
---

title: Supported content
description: Reference for the files and content General Translation translates in a Mintlify project. Reference for Mintlify supported content.

---

# Supported content

This page lists exactly what General Translation translates in a Mintlify project, what it leaves untouched, and which files are always excluded.

## Overview [#overview]

| Topic | Description |
| --- | --- |
| [Translated content](#translated) | The pages, frontmatter, snippets, and navigation that are translated. |
| [Preserved content](#preserved) | Code and structure that translation never alters. |
| [Excluded files](#excluded) | Repository files that are always skipped. |
| [Project requirements](#requirements) | What makes a repository a valid Mintlify project. |

## Translated content [#translated]

Locadex translates the human-readable content in your docs.

### Pages

All `.mdx` and `.md` files matched by the configured globs are translated. Translation happens at the Markdown/MDX syntax level, so headings, paragraphs, lists, tables, callouts, links, and custom components keep their structure. General Translation also adds stable heading anchor IDs (`experimentalAddHeaderAnchorIds: 'mintlify'`) so in-page links keep working across languages.

### Frontmatter

Frontmatter fields such as the page title and description are translated so navigation labels and SEO metadata work in every language. When a page has no explicit title, Mintlify infers one from the filename (`mintlify.inferTitleFromFilename`).

### Snippets

Reusable snippets under `snippets/` are translated and localized using the `docsImportPattern` (`/snippets/[locale]`), so imported content is served in the reader's language.

### Navigation

`docs.json` is localized with a Mintlify preset: navigation labels are translated, and the navigation is restructured into Mintlify's multi-language layout with one entry per language. Redirects are generated so existing links keep resolving.

## Preserved content [#preserved]

Translation never alters the following:

- Code blocks, inline code, and syntax highlighting. Only comments and documentation strings inside prose are translated.
- Custom MDX components, links, and formatting.
- File structure — translation does not rename or restructure your components or code.

## Excluded files [#excluded]

The locale folders themselves are excluded so translated output is not re-translated. In addition, these common repository files are always excluded from translation:

| File | File |
| --- | --- |
| `README.md` | `HISTORY.md` |
| `LICENSE.md` | `CODE_OF_CONDUCT.md` |
| `COPYING.md` | `CONTRIBUTING.md` |
| `NOTICE.md` | `SECURITY.md` |
| `CHANGELOG.md` | `GOVERNANCE.md` |
| `AGENTS.md` | `OWNERS.md` |
| `MAINTAINERS.md` | |

If your repository keeps translatable content in one of these files, adjust the `exclude` list in the generated [configuration](/docs/integrations/mintlify/reference/config) after setup.

## Project requirements [#requirements]

General Translation validates the repository before setup and rejects projects that are not valid Mintlify sites:

- The repository must contain a `docs.json` whose `$schema` points at Mintlify (`mintlify.com/docs.json`).
- Projects that still use the legacy `mint.json` are rejected — migrate to `docs.json` first.
- Projects that look like a Next.js app (they contain a `next.config.*` file) are rejected, because the Mintlify workflow is only for Mintlify documentation sites.