A directory of car manuals sounds like an asset until you have one. Ten thousand PDFs in folders named by someone’s personal logic is indistinguishable from zero PDFs — the information is all there and none of it is findable. carmanualspdf.info is the fix: the whole tree, browsable as manufacturer → model → year → manual, with a URL for everything.
The filesystem is the database
The site’s engine is a Go web app that renders templates over a directory tree: brand folders hold model folders, model folders hold year folders, and the PDFs hang off the end of it. That’s the entire content model. There’s no CMS to log into, no admin interface to secure, no database schema that drifts out of sync with reality — the manuals on disk are the catalogue. Adding a thousand manuals means putting files where they belong; the site reflects it on the next request.
Why not a database?
Because the source of truth is already files, and every table you derive from them is a second copy that can rot. A database would buy fast arbitrary queries, but the access pattern here isn’t arbitrary — people arrive knowing the brand, narrow to the model, then the year. That’s exactly a directory walk, which Go does quickly and which maps straight onto URLs people can guess, share, and bookmark. When the question is “the 2011 diesel manual, please”, a tree answers it without an index. When the catalogue eventually wants full-text search across model names, that becomes a build-time index over the same files — a view, not a migration.
Cheap to run, cheap to grow
Serving mostly-static pages from a filesystem is the least demanding workload in computing, and the hosting reflects that: the whole site runs as a single small machine on Fly.io, comfortably handling browse traffic for the cost of a coffee a month. Growth is additive — more diskspace, more manuals, same architecture. There’s no scale cliff hiding in it, because there’s nothing in the request path heavier than template rendering and file reads.
The shape of the thing
What I like about this build is what it refuses to do. It doesn’t wrap a folder of PDFs in a framework with a login page and a database to feed. It takes the collection as it actually exists — messy, filesystem-shaped, growing — and makes it navigable with the minimum machinery that survives contact with real users. Pick your manufacturer and start browsing at carmanualspdf.info.