Create a guide describing how to approach i18n
Open
docs
feature
pinned
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 383
- PR merge metrics
- No merged PRs in 30d
Description
Generally speaking, I think the approach currently is custom views.
Contributor guide
Research direction
The issue does not name any files, tests, or entry points. It only suggests documenting the current custom-views approach to i18n; first establish that approach in the repository, then define what the completed guide should cover.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, internationalization
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100