Digital Garden as Community Memory
A way of tending knowledge together — not as a stream of announcements flowing past, but as a landscape you can walk through, where older things are still reachable and newer things are woven in rather than pushed on top.
The Idea
In 2015, Mike Caulfield gave the opening keynote at the dLRN 2015 conference at Stanford and called it “The Garden and the Stream: A Technopastoral.” The talk distinguished two models for organizing information online. The stream is what most of the web had become: chronological, self-assertive, persuasive, built for now. Every post declares itself and scrolls away. The garden is older and slower: an interconnected space where ideas link to other ideas, where what you wrote three years ago is still findable and still able to be revised, where reading is an act of wandering rather than consuming. “Every walk through the garden creates new paths, new meanings,” Caulfield wrote.
The distinction is partly technical — feeds vs. linked pages — but mostly about intent. A stream is optimized for reach and immediacy. A garden is optimized for depth and return.
Origins
Ward Cunningham launched WikiWikiWeb in March 1995, the first wiki, installed on c2.com as part of a pattern repository for software design. The idea was simple: any visitor could edit any page, links could be made to pages that didn’t exist yet, and the network of pages would organize itself through use. The name came from the WikiWiki shuttle bus at the Honolulu airport — Hawaiian for “quick.” What Cunningham built was fast to update but slow to exhaust; the Portland Pattern Repository is still there, still readable, three decades later.
Andy Matuschak developed the evergreen notes framework as a personal knowledge practice: notes that are atomic (one idea per note), concept-oriented rather than topic-or-source-oriented, and densely linked to other notes. The evergreen label is about the temporal relationship to the idea — these notes don’t expire when the book that prompted them is shelved. The note lives and grows. Matuschak publishes his working notes as a public garden at notes.andymatuschak.org, showing the practice rather than just describing it.
The modern digital garden movement coalesced around 2018-2019, with writers and developers publishing personal knowledge sites that rejected the reverse-chronological blog format in favor of linked, lightly-dated notes. By 2020 it had a name and a small literature of its own.
The Community Shift
Most of what’s been written about digital gardens treats them as personal practice — one person’s mind, made traversable. The harder question is what it means for a community, not an individual, to keep one.
A community garden has to solve problems that don’t arise in personal practice. Whose voice speaks when facts conflict? Who decides a page is ready to be shared? What happens when a founding member leaves and their notes are the only record of why a decision was made? A personal garden can afford to be idiosyncratic; a community garden needs at least a light governance layer, or it fragments into siloed accounts of the same events.
The session log is one answer we’ve found ourselves using: write down what happened, why the decision was made, what the open questions are. Not for posterity — for the next session, which might be three hours later or three weeks. This Arboretum is another answer: a public-facing garden maintained collaboratively, with entries that point to each other and to the actual work, so the knowledge doesn’t live only in one person’s memory.
The Tension
Gardens require tending. A personal garden can survive neglect — the gardener just doesn’t revisit it. A community garden that goes untended becomes an artifact of a moment rather than a living record, and people stop trusting it. The wiki that was current in 2019 and hasn’t been updated since is worse than no wiki, because it carries authority it hasn’t earned.
There’s also the question of who the garden is for. Individual gardens can be genuinely private or semi-private — rough notes, half-formed thinking. Community gardens often become performative, written for an imagined audience, and lose the quality that makes them useful: the willingness to record what you don’t know yet.
Connections
- commons — shared knowledge as commons, governed by similar principles
- embodied-knowledge — what gardens can hold that streams cannot
- holding-contradictions — a garden can let two incompatible things stay true
- local-first — local-first knowledge infrastructure over cloud-dependent platforms
- reciprocity-with-land — the gardening metaphor as more than metaphor: tending, returning, seasonal attention
Further Reading
- Mike Caulfield, “The Garden and the Stream: A Technopastoral” (2015) — https://hapgood.us/2015/10/17/the-garden-and-the-stream-a-technopastoral/
- Maggie Appleton, “A Brief History & Ethos of the Digital Garden” — https://maggieappleton.com/garden-history
- Andy Matuschak’s working notes — https://notes.andymatuschak.org/