openedx / openedx/docs.openedx.org
Dev Guide > i18n guidelines
Open
Nobody has claimed this yet.
developers
i18n
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
Break into separate sections & review/edit each
- Concepts: How to think about i18n + additional resources
- Reference: How do in various code
- Legacy Code Templates reference
- How to test
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
Start with the linked legacy internationalization guide at docs.openedx.org/en/latest/developers/references/legacy_guide/internationalization/index.html. Review the Concepts, Reference, Legacy Code Templates, and How to test sections separately, editing each as needed. Done means the guide is organized into these sections and each section has been reviewed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, internationalization
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100