The Museum's Dilemma: When Preservation Is Not an Option
There’s a quiet, almost sacred piece of advice that floats through content strategy circles: treat your archive like a museum. The idea is seductive. It suggests a reverence for past work, a commitment to preserving the integrity of a piece exactly as it was first published. We are told to be curators, to protect our creations from the wear and tear of time, to let them stand as monuments to a moment since passed. But I want to challenge this. I want to argue that for most of us, this is not only a misguided luxury but an active disservice to our readers.
The museum model fails because it misunderstands the fundamental nature of the web. A museum is a physical space built for preservation; its objects are removed from the flow of time, placed under glass, their context carefully explained by a placard. The web is the opposite. It is a river, not a vault. It is a living conversation, not a recorded speech. A page from 2018 isn't a curated artifact for a visitor; it is a participant in the present-day search results, competing for attention with pages written yesterday. It is judged not by its historical significance, but by its current utility.
When we treat an old tutorial, a technical guide, or a product review as a museum piece, we are asking the reader to do all the interpretive work. We are handing them a tool without telling them if it’s still sharp, a map without indicating which bridges are now out. The un-updated page, proud under its glass case, becomes a potential trap. The information isn't framed by history; it's presented as truth, until the reader discovers it is obsolete. This isn't preservation; it's negligence dressed up as respect.
The Responsibility of the Living
The alternative isn't a frantic, meaningless update of every comma. It is a shift in philosophy: from curator to gardener. A gardener does not simply preserve a plant. They assess it, prune it, feed it, and sometimes, yes, they uproot it entirely to make way for something new that will better serve the garden's ecosystem. Our content is the same.
This doesn't mean erasing the past. It means being a responsible host to the present. A simple, dated note at the top of a page—'This guide reflects our understanding of the software as of 2021'—is a act of radical honesty. It contextualizes. It tells the reader where they stand. Better still is the gentle revision, the quiet amendment that notes a change without rewriting history. 'The process described below still works, though version 4.2 now offers a simpler method via the settings panel.' This isn't vandalism; it is stewardship.
The romantic ideal of the untouched archive is just that—a romance. For the vast majority of websites, our job isn't to build a time capsule for our own vanity. It is to maintain a useful, truthful, and living library for the people who rely on it right now. Sometimes, the most respectful thing you can do for your old work is to gently bring it into the present, or to acknowledge that its time has passed. The museum is for the dead. Our pages, and our readers, are very much alive.
Notes & further reading
A few pages I came back to while writing this:
- Las Vegas, NV
- The Tide Pool Method: Cultivating Content That Updates Itself
- North Las Vegas, NV
- The Sourdough Theory of Content: Why Some Pages Should Never Be Updated
- Reno, NV
- The Monk's Margin: Scribes, Scratching, and the First Content Patches
- Buffalo, NY
- New York, NY
- Rochester, NY
- Syracuse, NY
- Yonkers, NY
- Akron, OH
- Cincinnati, OH