Collection manager
Use with: build-web-app. Resume line when done: Built {project_name}, a searchable collection manager with export — live at {url}
Brief
A manager for a collection you actually keep: cards, sneakers, vinyl, plants, books, minifigs. Structured records with at least four fields, search or filter across them, and an export (JSON or CSV). Your real collection is the seed data; entering it is part of the build.
Personalize
- The collection. Yours, physically existing. The app is worth building because the collection is worth keeping.
- The four-plus fields. What matters about each item: condition, year, cost, rarity? You decide, and defend the choice in the README.
- Search or filter. Pick the one lookup you actually do ("all rares", "everything under $20") and build that first.
Milestones
- Data model in the README: what is one item, its fields, why those.
- Add + list working, deployed.
- Ten real items from your collection entered; persistence across reloads.
- Search or filter working against the real data.
- Edit and delete; designed empty state.
- Export (JSON or CSV) downloads your collection. Final README.
Done means
- Live URL responding; data survives a reload
- At least 10 real items; search/filter returns correct results
- Add, edit, delete, export all work
- At least 10 commits across at least 7 distinct days, authored by you
- README documents the data model and field choices in your words
- SESSIONS.md has an entry per session, written by you