Explore support for i18n
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- CSS
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Capturing this from recent conversations with community members: one thing that would increase the reach of Unison's presence and accessibility would be to support i18n in some capacity for our website.
Considerations:
- Could the i18n take place via transformations of the underlying Doc type?
- Machine vs human translations - programmatic translation services exist but aren't always great for texts of any measurable complexity.
- Moderation and review of translations would need to take place before publication.
- The website in its entirety is a large text body so supporting a subset of internationalized docs may be best.
- Many many others! Please continue discussion, requests, or ideas in this ticket thread.
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
No files, tests, or implementation entry points are named. Start by reviewing the existing issue discussion and defining whether a subset of documents, machine translation, or human translation is in scope. Done means an agreed approach supports internationalized website content with translation moderation and review before publication.
Written by the indexing model from the issue text.
Assessment
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100