Decision: Card review UI — how the review screen works #11
Labels
No labels
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:prototype
wayfinder:research
wayfinder:research
wayfinder:task
wayfinder:task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#8 Decision: SRS algorithm — SM-2, FSRS, or custom variant?
gaetan/knowledgify
#9 Decision: Tech stack — Go framework and frontend approach
gaetan/knowledgify
Reference
gaetan/knowledgify#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #1
Question
What does the card review screen look like, and how does the user interact with it?
The content model (Q&A + Vrai/Faux) and user model (no auth, single user) are settled. Now we need to decide the review experience.
Review flow:
Rating mechanisms:
Screen layout:
This decision is tightly coupled with the SRS algorithm (#8) and the tech stack (#9).
Dependencies
Resolution
Card review UI decided:
Interaction model: Anki-style. Space to reveal, 1-4 to rate (1=Again, 2=Hard, 3=Good, 4=Easy). No mouse needed. On-screen hints show shortcuts.
Card display: Minimal card centered on screen. Large text. Category badge (colored, small). Progress indicator ("3/25") in corner.
Q&A flow:
Vrai/Faux flow:
Session: All due cards in one sitting. Optional category filter. No forced breaks.
Post-session: Summary stats (cards reviewed, retention rate, new cards learned) + quick actions ("Review all cards", "Review hard cards").
Template structure (Go templates):
Alpine.js components:
x-data="{ card, revealed, rating }"— manages card state/review/ratefor rating submission