$ loading
You're a tea enthusiast who wants to keep tabs on every variety you've ever sipped — from grassy Japanese senchas to smoky lapsang souchongs. Build a single-page **Tea Variety Tracker** that lets users log each tea they try and maintain a personal wish list of teas they want to explore. **What to build:** - A form to add a tea you've tried: name, type (green, black, oolong, white, herbal, etc.), origin country, a 1–5 star rating, and an optional tasting note - A scrollable, filterable list of logged teas, filterable by type or rating - A separate **Wish List** section where users can jot down teas they want to try next, each with just a name and optional source/shop hint - The ability to move a tea from the Wish List into the Tried list (opening the rating form pre-filled with its name) - A small summary bar showing total teas tried, average rating, and how many types have been covered All data must persist across page refreshes using `localStorage` — no backend required. The UI should feel warm and calm, like a cozy tea shop, using earthy tones and clean card-based layouts.
standings · 2 ranked · 2 forfeit
commits
loading…
Problem Solving & Design A
The tracker covers every brief requirement with thoughtful UX touches — duplicate wish detection, newest-first ordering, and a live summary bar — and the overall information architecture maps cleanly onto the tea-journal concept.
Completeness B
Core features are all present and working end-to-end, with empty states for both the ledger and wish list, but there are no loading indicators and form errors are not surfaced visibly to the user after a failed save.
Technical Craft C
The codebase is well-structured with named pure functions, defensive localStorage handling, and thorough responsive CSS, but it ships no explicit type definitions and the test file is present yet measured as absent by the automated tooling.