Thinking in archives
A short reflection on why I keep returning to the idea of accumulation over time — in projects, writing, and technical systems.
I notice I keep building archives.
Or HaZeev is an archive of Sephardic liturgical tradition. Constantine Minhagim is an archive of community custom. LightBen Food is, in a slower way, an archive of techniques and recipes. This site is, ultimately, an archive of how I think and what I make.
This might be temperament. I am drawn to accumulation over time rather than the current and disposable. A project that builds slowly over years interests me more than one that launches and fades.
There is something about the archive as form that resists the dominant logic of the web, which is: generate, distribute, replace. The archive insists instead on staying, on being findable, on getting denser and more useful over time.
The technical implications are real. Archives need stability. They need URLs that do not break. They need search that works across everything, not just the recent. They need to be legible to someone arriving years from now, without the context of when it was created.
Static sites are good for this. Plain text is good for this. Careful naming and structure are good for this.
I have started thinking of the stack choices as archival choices. Not what is most powerful or most current — what will still make sense and still work in ten years.
That is a different optimisation than most web projects make. It is probably the right one for this kind of work.