The Project Graveyard
Abandoned side projects, dug up as honest handoff notes for the next builder.
🪦 Browse the graveyard (sample data)
Demo data is clearly fictional. The real idea: builders "bury" projects with notes on what worked, what failed, and what's worth reviving — next builders adopt with context instead of starting from zero.
Why people love it
The graveyard is the uncomfortable truth about side projects: most of them die. Folders full of half-built apps, abandoned domains, and "v1 never shipped" code are the default outcome for motivated people who run out of time. This idea treats that as a resource instead of a failure. Every abandoned project gets a tombstone — what it was, why it stopped, what worked, and what's genuinely worth salvaging — and new builders can adopt the ones that fit their skills and energy.
People love it for the honesty. Hustle culture only shows wins; a graveyard normalizes the 90% of attempts that stall, and turns "I gave up" into "here is my documented lesson". For adopters, it's a head start: someone already fought the domain problem, picked the stack, and found the first ten bugs. You inherit a learning curve instead of a blank page.
Try the demo: search the tombstones, read a handoff note, and adopt something that speaks to you. That click is the whole point — dead code becoming somebody's starting point.