The Gardener's Trellis vs. The Mason's Arch: On Two Philosophies of Site Structure
When we consider the underlying framework of a website, we often speak of architecture. It’s a telling metaphor, conjuring images of blueprints, load-bearing walls, and permanent foundations. But is this the only way to conceive of a site’s structure? I’d argue that two distinct, almost oppositional philosophies govern how we build the pathways of our digital spaces: one of masonry, and one of gardening.
The mason’s approach is one of deliberate, permanent hierarchy. Every page is a precisely cut stone, and its place in the grand arch of the site is predetermined and unchanging. The URL structure is a direct reflection of this blueprint, with categories and subcategories laid out in a logical, predictable cascade. A page’s location—its path—is its primary, immutable identity. The internal linking strategy here is like the keystone in an arch; it is calculated to distribute authority and reinforce the intended hierarchy, guiding users along a pre-ordained route. This method values clarity, predictability, and a sense of ordered permanence. It is a structure built to last, resistant to the whims of change.
In stark contrast, the gardener does not build with stone, but cultivates living, growing things. The site structure is a trellis, a supportive framework designed not to confine, but to guide organic growth. The hierarchy is not a rigid law but a suggestive form. Individual pages (the plants) are valued for their content and relevance, and their connections are formed contextually, based on semantic relationships rather than a fixed architectural plan. The URL might be clean and logical, but it is a label on a pot, not a fixed coordinate on a map. Internal links are planted where they are most naturally relevant, creating a web of associative meaning rather than a prescribed navigation. This structure is inherently flexible, adaptable, and responsive to new content, which can be woven into the existing trellis without requiring a redesign of the entire garden.
Neither philosophy is inherently superior; they are tools for different purposes. The mason’s arch is ideal for a large institutional site, an encyclopedia, or an e-commerce platform with a stable, deep hierarchy where users expect and require a clear, logical path. Its permanence is its strength. The gardener’s trellis, however, thrives for blogs, evolving knowledge bases, or creative projects where content emerges organically and relationships between ideas are more important than their position in a file cabinet. Its flexibility is its virtue.
The tension between these two approaches becomes most apparent during a site migration or a content overhaul. The mason must carefully draft new blueprints and rebuild the arch, stone by stone, ensuring every redirect perfectly maps the old permanent location to the new one. The gardener simply ensures the new growth is trained properly on the trellis, trusting that the living connections between content will maintain the site’s coherence. The choice, then, is not merely technical, but philosophical: are you building a monument, or are you tending an ecosystem?
Notes & further reading
A few pages I came back to while writing this: