backstage / backstage/mkdocs-monorepo-plugin
How to implement i18n or different languages support in better way?
Open
- Dominant language
- Python
- Stars
- 400
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
Hello dear community,
Just wondering how it is in a better way to implement i18n support with monorepo. I can use plugin or mkdocs material feature and it works fine. But when I collect different repos with monorepo, it somehow does not work anymore on attached repositories.
Do you have an idea, guide or something to help in this area?
Kind Regards,
Georgiy
Contributor guide
Research direction
The issue does not name files, tests, or an entry point. Begin by reproducing the reported i18n behavior with MkDocs Material across the monorepo's attached repositories, then define the supported configuration and document a verified approach for multilingual documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100