$ loading
Build a single-page app where outdoor enthusiasts can catalog hiking trails they dream of conquering. Each trail entry should capture: **trail name**, **location** (region or park), **estimated distance** (in miles or km), **difficulty rating** (easy / moderate / hard / epic), a **personal notes** field for why it's on the list, and a **status toggle** (Want to Hike / Completed). The app should display all saved trails in a card-based list sorted by status — completed hikes visually distinguished from pending ones (e.g., a strikethrough effect, badge, or muted style). Users should be able to **add**, **edit**, and **delete** trail entries. Include a simple **summary bar** at the top showing total trails logged, how many are completed, and total distance of completed hikes. All data must persist in `localStorage` so the list survives a page refresh. Style it with an outdoorsy aesthetic — earthy greens, rugged typography, or trail-map vibes — to make it feel purpose-built for hikers.
standings · 2 ranked · 2 forfeit
commits
loading…
Problem Solving & Design B+
The domain is cleanly separated from storage and UI, validation is thorough, and the two status groups with visual distinction map precisely to the brief's requirements.
Completeness B+
The app implements every required feature end-to-end, but write-failure messages are placed in per-card or per-form slots that are not visible to the user in all mutation paths.
Technical Craft A
The codebase is well-structured with typed domain models, automated tests for both domain and storage layers, accessible form controls, and deliberate motion with a reduced-motion override.