mkdocs-translations

MkDocs i18n configuration is updated by this Skill to include new locale entries in the mkdocs.yml file, ensuring the i18n plugin correctly registers and serves the translated Markdown files alongside the original English sources.

Yes, MkDocs translation through this Skill requires a dedicated git branch. It integrates with your git workflow to isolate the automated translation work and generated localized Markdown files from the main branch.

Adding multilingual i18n support involves generating translated Markdown files and updating the mkdocs.yml configuration. This Skill automates that process, requiring only a target locale code to comply with the i18n plugin format.

Automating MkDocs translation requires a git branch name and a target locale code. The Skill then handles file discovery, translation generation, and the mkdocs.yml configuration updates needed for the new language.

Translating MkDocs files preserves the original folder structure completely. The Skill generates localized Markdown copies that mirror the English source directory hierarchy, maintaining project organization for the i18n plugin.