The Tide Pool and the River: On Two Kinds of Site Refreshment
Walking along the coast, you find two distinct bodies of water adjacent to the sea. One is a tide pool, a seemingly self-contained world that is only occasionally, dramatically replenished by the high tide. The other is a river mouth, where freshwater from upstream constantly mingles with the salt, a perpetual, incremental exchange. In managing a website’s content, these two metaphors define the fundamental, contrasting approaches to the problem of freshness. Is your site a tide pool, or is it a river?
The tide pool model is one of monumental, scheduled updates. Think of the corporate ‘About Us’ page that only changes when there’s a massive rebranding, or the academic course catalogue published once a year. This approach values stability and authoritativeness. The water in the pool is clear for long stretches; the facts are settled, the presentation is polished. The effort is focused and immense, a high tide of editorial labor that sweeps in, changes everything at once, and then recedes, leaving the new ecosystem to remain static until the next celestial alignment of budget and deadlines. The risk, of course, is stagnation. Between tides, the water can grow warm, oxygen can deplete, and the vibrant life within can become isolated from the changing ocean just over the rocks.
In direct contrast, the river model embraces a state of continuous, small-scale flow. This is the domain of the active blog, the news site, the community wiki, the product knowledge base. Content here is never truly ‘finished’; it is a living document. A statistic is updated when a new report lands, a paragraph is clarified after user feedback, a broken link is mended the moment it’s spotted. There is no single ‘update event.’ Instead, there is a constant, low-grade hum of maintenance, a thousand tiny corrections flowing downstream, ensuring the water never sits long enough to grow stale. The authority of this model is not derived from a final, printed-state perfection, but from its demonstrable currentness and responsiveness.
Neither approach is inherently superior; each serves a different purpose. The tide pool offers a refuge of permanence in a chaotic digital sea. We need pages that act as bedrock, whose unchanging nature is a feature, not a bug. The river, however, thrives on its connection to the present moment, building trust through its visible, flowing activity. The peril lies in applying the wrong model to the wrong content. A tide pool news site is a ghost town. A river-like legal disclaimer is a liability.
The most effective content strategist, then, is like a coastal geographer, mapping the site’s landscape. They identify which pages are the bedrock—the tide pools that should only change with significant shifts—and which are the waterways, requiring a constant, gentle current of attention. The goal is not to choose one over the other, but to understand the unique ecology of each page and manage its refreshment accordingly, ensuring the entire coastline remains both stable and alive.
Notes & further reading
A few pages I came back to while writing this:
- Warren, MI
- The Jar of Paperclips: On the Unmade Decision of an Unemptied Cache
- Saint Paul, MN
- The Archivist’s Leaking Cistern: On the Seasonal Loss of What Stagnates
- Springfield, MO
- The Gardener's Vigilant Fallow: On Letting Soil Lie Unseeded
- St Louis, MO
- Jackson, MS
- Cary, NC
- Charlotte, NC
- Fayetteville, NC
- Greensboro, NC
- Raleigh, NC