Knowledge Concepts
A digital garden is a personal website or note collection that grows in public over time — with ideas in various states of development, linked to each
A digital garden is a personal collection of notes and ideas — often published publicly — that grows and evolves over time rather than existing as finished, timestamped content. Unlike a blog (which publishes polished articles in reverse chronological order), a digital garden contains notes in various states of development — seeds (early ideas), growing (in progress), and evergreen (mature thoughts) — all linked to each other and continuously tended as the gardener's thinking develops.
The metaphor: a garden grows; a blog publishes. A garden is tended over time; a blog archives finished work.
The term "digital garden" was coined by Mark Bernstein in "Hypertext Gardens" (1998), but the modern concept was largely shaped by Mike Caulfield's 2015 essay "The Garden and the Stream: A Technopastoral." Caulfield contrasted the "garden" (a non-linear collection of linked ideas that grows over time) with the "stream" (the reverse-chronological social media feed of ephemeral posts).
The concept gained significant cultural traction in the PKM community around 2019-2020, partly through Maggie Appleton's visual essay "A Brief History & Ethos of the Digital Garden" (2020), which catalogued dozens of practitioners and articulated the philosophy clearly.
Key practitioners who shaped the concept include: Gwern.net (long-form essays updated over years), Andy Matuschak (notes on learning and education published openly as interconnected notes), and Joel Hooks (the term "digital garden" as a philosophical stance on learning in public).
| Feature | Blog | Digital Garden |
|---|---|---|
| Organization | Reverse chronological | Topically linked |
| Status | Published = finished | Notes in various development stages |
| Update pattern | Archive (old posts unchanged) | Continuous revision (notes evolve) |
| Discovery | Browsing by date | Browsing by connection |
| Voice | Polished, authoritative | Exploratory, thinking-in-progress |
| Publishing threshold | Only publish when complete | Share at any stage of development |
| Goal | Audience engagement | Personal thinking + optional sharing |
The core difference: blogs treat publishing as the destination; digital gardens treat publishing as an ongoing practice.
Digital gardeners typically categorize their notes by development stage:
Seeds: Early, undeveloped ideas. A rough observation, an interesting question, a link with a brief reaction. Seeds are planted but not yet developed. They might become something or they might wither.
Sprouts / Budding: Ideas that have been developed a bit — more than a seed, but still actively growing. Some research done, some thinking recorded, but not yet refined.
Evergreen: Mature, stable notes that represent the gardener's settled thinking on a topic. These are the most developed notes — regularly referenced, frequently linked to from other notes.
The stages aren't rigid — different practitioners use different terminologies (seeds/seedlings/trees; notes/essays/evergreens; draft/developing/stable). The principle is consistent: notes exist on a spectrum of development, not as either "drafts" or "published."
A product designer starts a digital garden.
Month 1 — Planting seeds: After reading an article on design systems, they add a note titled "Design systems and design debt" — just a few sentences capturing a rough idea: "Design systems reduce short-term inconsistency but can create long-term debt if they become too rigid. Need to think about how to keep them evolving."
Month 3 — A seed grows: They've worked on two projects involving design systems. They add notes from each project to the design systems note, plus a link to another note on "technical debt vs. design debt." The note is now 500 words but still labeled "growing."
Month 8 — An evergreen emerges: They've now gathered enough examples, read several papers on the topic, and formed a clear view. They write a 1,500-word note that clearly articulates their position, connects to 4 related notes, and includes a comparison table of design system evolution patterns. This note is labeled "evergreen."
The compound value: The note they created in month 1 would have been too undeveloped to publish as a blog post. Published as a digital garden note, it was visible to others — attracting a reader who left a comment that influenced the month 8 revision. The garden's value compounds over time; a blog's posts are typically fixed at publication.
Step 1 — Choose your tool:
The most important criterion: you'll actually use it. Simple and used beats powerful and neglected.
Step 2 — Start with a few seeds: Pick 3-5 topics you think about regularly. Create a note for each. Don't try to make them comprehensive — start with what you actually think right now, labeled "seed."
Step 3 — Create links between notes:
When you write one note and realize it connects to another: link them with a wiki-link ([[Note Name]]). Links are what make a digital garden different from a collection of documents — they form the pathways visitors follow.
Step 4 — Tend regularly: Set a weekly practice of returning to existing notes and adding recent thinking, new sources, or revised positions. A digital garden that isn't tended becomes static — which defeats the purpose.
Step 5 — Decide on privacy: Not all digital gardens are public. A private digital garden is still valuable as a personal thinking tool. If you publish publicly: be comfortable with imperfection — the value of a garden is showing thinking in progress, not only showing finished ideas.
The capture → garden connection: Web clipping tools (like WebSnips) are natural feeders for digital gardens. You clip an article, add a note about what you found interesting, and that note becomes the seed of a garden entry on the topic. Over time, multiple clips on the same topic provide the raw material for a growing note.
The difference between a clipping and a garden note: A clipped article with a reaction note is raw material. A garden note synthesizes that material into your own thinking, developed over multiple captures and sessions. The clip says "I found this interesting"; the garden note says "here's what I think about this topic, developed over time."
The workflow:
This creates a virtuous cycle: clipping feeds the garden; the garden organizes the clips into developed thinking.
"A digital garden is just a private blog." The critical difference is the non-linear, interconnected structure and the continuous revision ethic. A blog has a chronological index; a digital garden has topical links. A blog publishes finished work; a digital garden evolves.
"I need to publish my digital garden publicly." No. A private digital garden — notes you tend for yourself, never shared — is still a digital garden. The public-sharing aspect is one possible expression, not a defining feature.
"My notes aren't good enough to publish." The digital garden philosophy explicitly rejects the "publish-only-when-perfect" standard. Seeds — rough, early, incomplete — are intended to be visible. The imperfection is the point: it shows thinking in process, not just conclusions.
Second brain: A broad concept for an external, personal knowledge system. Digital gardens are one implementation of a second brain, with the specific "garden" metaphor emphasizing evolution over time.
Zettelkasten: A linked note-taking method that shares the networked structure of digital gardens. Many digital gardeners use Zettelkasten principles internally.
Personal wiki: A related concept — a personal, editable wiki for accumulated knowledge. A personal wiki typically emphasizes reference; a digital garden emphasizes thinking in progress.
What's the best tool for a digital garden? There's no single best tool. Popular options: Obsidian (local-first, great for private gardens and publishable with Obsidian Publish), Quartz (open-source static site generator for Obsidian notes), Notion (easy to share, limited backlinking), Roam Research (strong graph structure, limited publishing options). Start with what you already use for notes rather than switching systems.
Do I need to code to have a digital garden? No. Tools like Obsidian Publish and Notion let you create a public digital garden without any coding. Coding gives you more control (custom themes, specific URL structures) but isn't required.
How is a digital garden different from a personal knowledge base? A knowledge base is primarily a reference repository — you look things up. A digital garden is primarily a thinking tool — you develop ideas and see how they connect. The distinction is subtle; in practice, many personal knowledge bases function as digital gardens, and many digital gardens serve as personal knowledge bases.
A digital garden is a different way of relating to your own ideas: not producing finished content, but tending a living collection that grows with you. The blog asks "is this ready to publish?" The digital garden asks "what do I think about this, and how is my thinking developing?" For knowledge workers who read widely, think deeply, and want their accumulated thinking to compound over time rather than evaporate, the digital garden is a powerful framework — not just for what you know, but for how you know it.
For more on this, see AI Knowledge Management in 2025.
More WebSnips articles that pair well with this topic.
Knowledge transfer is the deliberate process of moving knowledge from where it exists — an individual, team, or system — to where it is needed, in a form
A browser extension is a small software add-on installed in a web browser that adds features or modifies behavior — blocking ads, saving passwords
A content calendar is a planning tool that schedules what content will be published, when, where, and by whom — turning a content strategy from vague
A context window is the maximum amount of text an AI language model can process in a single interaction — everything in the prompt, the conversation
A knowledge silo is a condition where knowledge, information, or expertise is isolated within a team, department, or individual — inaccessible to others
A large language model (LLM) is a neural network trained on massive amounts of text to predict and generate language.