Website internationalization
Open
Nobody has claimed this yet.
E-medium
P-low
S-needs-design
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
Internationalizing the parts of the website that are ours (not rustdoc output) would be a nice thing to have, but it's a lot of work on the software and manpower sides, as it requires multiple native-speakers to translate and verify each language
Contributor guide
No contributing guide indexed for this repository
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. Start by identifying which website parts are owned by docs.rs rather than rustdoc output, then define the translation and verification process for each supported language; done requires those surfaces to be internationalized and checked by native speakers.
Written by the indexing model from the issue text.
Assessment
- Domain
- internationalization, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100