Language toggle
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
There has been a discussion if the about page should have translations for all fields directly or have a language button on top.
The current way to do do it seems to be the right way to me. If we add a language toggle on top, people might be confused why not the entire page is translated. Generally, I consider it an UX question: If it works well, I am fine with just adding the missing translations.
Related:
- #106
- #103
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 by reviewing this issue and the related issues #106 and #103; no file, test, or implementation entry point is named. The discussion is still deciding between a language toggle and adding missing translations, so the scope and completion criteria need to be resolved before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- internationalization, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100