mkdocs-translations

To translate MkDocs documentation, you specify a target language and locale code to start the workflow. The process mirrors the English Markdown structure from docs/docs/en into a new localized directory while preserving original filenames and formatting.

MkDocs i18n plugin translation updates navigation and admonitions automatically during the workflow. The process specifically configures nav_translations and admonition_translations to ensure the localized documentation reflects the target locale accurately.

Markdown formatting is preserved during translation by mirroring the source structure and retaining original filenames. This ensures localized technical content maintains its layout and structural integrity across the target language files.

You can translate MkDocs include files alongside main documentation by processing docs/docs/includes/en. The workflow mirrors these included files into docs/docs/includes/<locale_code>/ to ensure complete localization coverage.

Consistent terminology across translated MkDocs files is enforced by the translation workflow logic. It applies uniform terms throughout all generated localized Markdown files to maintain technical accuracy and coherence.

The best way to structure localized MkDocs files is to mirror the English directories under docs/docs/<locale_code>/ and docs/docs/includes/<locale_code>/. This approach maintains the original folder hierarchy and filenames for every target language.