OpenRefine / OpenRefine/openrefine.org
Split translation documentation into translator- and developer-oriented pages
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
Our page about translation contributions currently mixes-up content for two different audiences:
- people who want to translate the application (or its documentation, although this process is not documented)
- people who want to make the application translatable (developers)
We should have one page for each.
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
Start with the linked translating-ui page and review how its current content serves translators and developers. Split the material into one page for people translating the application or documentation and one for developers making the application translatable; the result should also make the undocumented documentation-translation process clear where relevant.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100