Repository navigation
Design Guidelines
github-actions[bot] edited this page Oct 26, 2026
·
1 revision
Source of truth: this wiki page.
There are a lot of this superfluity in the UI. Record this as a design guideline, avoid superfluity everywhere and write direct sentences.
Said on the "Not quite" banner after a spoken answer: it repeated the answer that the card above it already showed, and did not say what was wrong.
- Show nothing the learner already sees on the same screen.
- Say what happened, in one direct sentence. No lead-in, no softening.
- A message tells the learner what was wrong, not what was right: the card already shows the right answer.
- Cut a line, a label or a word that changes nothing the learner does next.
- Where there are several scripts, show the one being learnt; where several are being learnt, the first.
- Review each screen with: "What would the learner miss if this went?" If nothing, remove it.
1. Learner guides
- Learner Guide
- Getting Started
- Today and Daily Lessons
- Drills and Skills
- Courses and Paths
- Proficiency Levels
- Scripts and Readings
- Readings ISO 15919
- Speaking and Listening
- Progress and Stats
- Profiles and Settings
- Backup and Restore
- Reporting a Problem
2. Deck building guides
- Deck Building Guide
- Deck Format
- Romanising Indic Languages
- Deck Licences and Quoted Books
- Deck Tools
3. Review guides
4. Translation guide
5. Building on iOS
6. Roadmap
7. Sources and attributions
8. Contribution and agentic coding