The Humility of the Relative Path
I was moving the furniture around again. It’s a habit, this need to shift the digital topography of the blog, to find a more pleasing arrangement for thoughts that have grown stale in their old containers. This time, the project was the archive section. I had grand plans: a new taxonomy, a cleaner layout, a better home for words that had served their purpose but deserved a dignified retirement. As with any such upheaval, it meant changing addresses. Pages that once lived at `/thoughts/2024/spring-reflection` were to be moved to a new neighborhood, `/archive/2024/spring-reflection`.
And so I began the work, updating menus, rewriting the rules in the server’s configuration file, setting up the grand redirects that would shepherd any lost visitors from the old door to the new. It’s the responsible thing to do, this explicit mapping of the past onto the present. We call these absolute redirects, pointing a full, specific path to another with bureaucratic precision. Yet, as I scrolled through the lines of code, my eye caught on something else, something I had written long ago and forgotten: a simple link, nestled in the body of a post, pointing to another article with just `../winter-solitude`.
A relative path. It is the web’s quietest, most unassuming gesture. It doesn’t shout its own importance. It doesn’t begin with a grand pronouncement of the domain name. It simply points, from where it is, to a place nearby. It says, “From here, go to there.” Its meaning is entirely dependent on its context. Move the page it lives on, and its destination changes without you having to lift a finger. It is a link that understands its place in a structure.
This is its peculiar humility. The absolute path is a sovereign, declaring its complete and unchanging identity from the root of the domain downward. It is confident, but brittle. Change the domain, change the structure, and it shatters, becoming a dead letter unless meticulously updated. The relative path, by contrast, is flexible, relational. It accepts that it is part of a whole, and its purpose is to connect its immediate surroundings. It works because it acknowledges it is not the center of the universe.
There is a profound lesson in this for anyone who builds things on the web, or perhaps for anyone who builds anything at all. We are so often counseled to build for scale, to future-proof with absolute declarations, to make everything resilient to change by making it rigid. But the relative path suggests another kind of resilience—the resilience of adaptability, of understanding one’s part in a living system. It trusts the structure to hold, and in doing so, it helps to hold the structure together.
I left that link untouched. My grand redirects will handle the visitors coming from search engines or old bookmarks, the traffic from the outside world. But for the quiet, internal conversation between my own pages, the relative path will continue its work, a silent and reliable bridge that I don’t have to maintain. It is a small pact between the pages themselves, an agreement that as long as they remain in relation to one another, they will always know how to find each other. In the end, it is not the loud, engineered permanence of the absolute that sustains a site, but the countless, humble relations woven through it.
Notes & further reading
A few pages I came back to while writing this:
- a helpful reference
- The Cathedral's Blueprint: On Architecture, URLs, and Enduring Structure
- a place-by-place guide
- The Ghosts in the Machines: On the URLs We Remember and the Servers That Don't
- a local resource
- The Quiet Custodian: On the Man Who Tends the Lost Paths
- a regional guide
- a useful directory
- one area's overview
- a practical rundown
- a nearby resource
- New York
- Nebraska