mkdocs-translations

This Skill translates MkDocs documentation by processing Markdown files in `docs/docs/en` and `docs/docs/includes/en`, converting content into a specified target language while preserving folder structure and Markdown formatting.

Yes, the translation process preserves the original folder structure, filenames, and Markdown formatting, ensuring the localized output matches the source directory layout without breaking internal links.

Yes, the Skill automatically updates `mkdocs.yml` for internationalization (i18n) support during the translation process, ensuring the MkDocs configuration recognizes the newly generated localized content.

Yes, Git is required to automate MkDocs localization. The Skill uses Git specifically for creating branches to manage and isolate the translated documentation output effectively.

The best way is using an automated process that applies strict translation rules for technical terminology while preserving Markdown syntax. This ensures your technical writing remains structurally intact during localization.

Limitations include requiring source files to be strictly located within `docs/docs/en` and `docs/docs/includes/en` directories, and depending on Git for branch creation to manage the translated output.