-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Problem Statement
The language dropdown selector on this site is much dumber than many that are out there.
Currently, it only does one thing: takes you to the homepage of whatever language you select.
Ideally, it would also switch between languages for the term page you're on.
Proposed Solution
When you're on a term page, and you change langauge, it takes you to that term's page in that language, if it exists. If it doesn't, it takes you to a (localized) page that says that term doesn't have a translation yet, and points the reader to the submission flow.
Use Case
While there are links to different languages at the bottom, it is in line with modern web UX.
Impact on Different Languages
I think it would help people discover words in their best languages.
Technical Considerations
This is mainly an impact on the js files in ./public/src/js, and maybe on the build script(s).
Alternatives Considered
There are modern framework-based solutions out there that do this, but I've tried them, and it sucked.
e.g. react-i18next.
Design Philosophy Alignment
Explain how this feature aligns with our principles:
- Maintains simplicity ("for the ages")
- Supports decentralization
- Enhances accessibility
- Preserves language neutrality
Implementation Scope
- Large (architectural changes needed)
Additional Context
Add any other context, mockups, or examples here.
Checklist
- This feature maintains the project's low-tech approach
- ^^ kinda
- This feature works across all supported languages
- This feature doesn't introduce unnecessary dependencies
- ^^ if we do it right
- This feature considers IPFS deployment implications