Proposal - Internationalization
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 19
Description
Conversation inspired by https://github.com/prometheus/docs/issues/2059 we want to start looking at how we can make internationalization possible on prometheus docs
- (Potentially unrelated) Do we want to migrate off of nanoc?
- Should there be owners for languages?
- How do we deal with URLs: /en/something should be changeable to /fr/something or /de/something to work
- How do we deal with missing translations?
- We could model things a bit off of Kubernetes
Translations:
- #2059
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points to start from. First map the documentation generator and translation workflow, then resolve the questions about language ownership, localized URLs, missing translations, and a possible migration from nanoc. Done means an agreed internationalization design with an implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, internationalization, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100