The Librarian's Map: On Dewey and the Original Site Structure
We talk about site architecture as if it were a new problem, born with the web. We wrangle over taxonomies and parent-child relationships, debating the perfect semantic breadcrumb trail. But the struggle to impose order on chaos, to create a navigable system for human knowledge, has a much longer history. Before there were URLs, there were call numbers. And before there were information architects, there was Melvil Dewey.
Dewey, with his infamous decimal system devised in 1876, wasn't just organizing books. He was creating the first widely adopted, scalable information structure for a physical network—the public library. His system functioned as the ultimate internal linking strategy. Each decimal point was a deliberate decision, a hierarchical path. A book on 20th-century French painting didn't just sit anywhere; its code (709.44) placed it precisely within a lineage: 700 for Arts, 709 for Historical treatment, .44 for France. To find it, you followed the path. This is the pure, pre-digital essence of a well-structured URL: /arts/history/france/20th-century-painting.
The Canonical Copy in the Stacks
Dewey’s system also grappled with a canonical problem. What do you do with multiple editions of Moby-Dick, or commentaries on it? Which one gets the prime, authoritative spot in the 813 section? The librarian must choose a primary copy—the definitive edition, the most complete text. The others, while accessible, are derivative branches. This is the canonical tag in oak and cloth: a silent, physical declaration that while many instances exist, this one is the source of truth for this location in the system. The redirect, then, is the librarian seeing your confusion at the card catalog and physically walking you from where you thought the book should be to where it actually is, updating your mental map.
His rigidity, however, reveals the dark side of over-structuring. Dewey’s personal biases—particularly his racism and sexism—were baked into the numbers. Subjects related to Christianity received vast, detailed subdivisions, while non-Western religions were crammed into comparatively tiny slots. “Women’s professions” were often separated from the main profession. The structure itself became a censor, not just an organizer. It’s a stark, century-old warning: the logic you hard-code into your URL paths and categories doesn't just organize content; it silently teaches users what is important, what is normal, and what is ‘other.’
Modern site architects are the digital heirs to Dewey’s ambition and his folly. We still seek that perfect, mappable hierarchy. We still fight the chaos of duplicate content and broken links. But Dewey’s legacy reminds us that no structure is neutral. Every slash in a URL, every hub page, every decision to canonicalize one page over another is a tiny act of philosophy. It asks: how do we want people to think about this information? Are we building a rigid, decimalized maze that reflects our own blind spots, or are we creating a living, adaptable map that guides without confining? The answer isn’t in a schema, but in remembering that every system, digital or not, is built for a human hand to follow.
Notes & further reading
A few pages I came back to while writing this: