An Uncle's Bequest: On the Database and the Bookshelf

My uncle, a man who ran a used bookstore for forty years, left me his inventory system when he passed. It wasn't a digital file or a complex database. It was a cloth-bound ledger, each page a dense grid of his nearly illegible handwriting. Titles, authors, prices, and acquisition dates filled the columns. It was a marvel of internal consistency, a perfect map of his world. But the shop itself was a glorious, chaotic mess. A book on Antarctic exploration might be shelved next to a volume of Victorian poetry because, as he’d say, "they both speak of a certain kind of longing." The map was rigid; the territory was alive with intuition.

For weeks, I tried to impose the ledger’s order onto the physical shelves. I started moving books, section by section, alphabetizing, categorizing. It felt like the right thing to do, to make the place "efficient." But something was lost. The charming, unexpected connections—the tether between a book on beekeeping and a memoir of a Japanese gardener—vanished. I had replaced his web of meaning with a sterile directory. I had mistaken the structure for the soul.

This is the tension I feel every time I sit down to design a site structure or a URL scheme. The database—the ledger—demands clean, logical hierarchies. It wants a single, canonical path for every piece of content. Page A belongs in Category X, which sits under Section 1. The URLs become predictable, like call numbers in a library: /section-1/category-x/page-a/. This is the logic of the machine. It is correct. It is findable. But is it always right?

My uncle’s bookshelf argued for a different philosophy. His system was built not on exclusivity, but on multiple, meaningful contexts. A single book could exist in several places at once in the mind of a curious browser. In our digital territories, this is the power of internal linking. It allows us to create those intuitive, lateral paths that the rigid hierarchy cannot. We can let the book on beekeeping link naturally to the memoir on gardening, creating an unbeaten path for a reader with a specific, un-categorizable curiosity.

The canonical URL is the single, authoritative home for the content—the book’s primary place on the shelf, if you will. But the internal links are the whispered recommendations, the "if you liked this, you might find that" moments that give a site its humanity. They acknowledge that while a thing has one official address, its meaning is enriched by the company it keeps. A redirect, then, is not just a technical fix for a broken link; it’s the act of politely escorting a visitor from a remembered, perhaps outdated, context to the current, canonical one. It’s a gesture of respect for their original intent.

I never did finish alphabetizing my uncle’s shop. I kept the ledger for accounting, but I let the shelves breathe. I started creating little curated nooks, thematic collections that transcended genre. The lesson was clear: a perfect structure should not be a cage. It should be a scaffold upon which you can hang a tapestry of connection. Our URLs and categories are the necessary ledger, the backbone without which everything collapses into noise. But our links are the soul. They are the unexpected placement of a book that makes a visitor stop and think, "Why is this here?" And in that question, a deeper engagement is born.

Notes & further reading

A few pages I came back to while writing this: