Learn

The digital garden: a complete guide

What is a digital garden?

A digital garden is a personal website or knowledge space where notes, ideas, and writing are published in various stages of development, organised by connection rather than by date, and allowed to evolve openly over time.

The term was popularised by Mike Caulfield in his 2015 keynote essay The Garden and the Stream: A Technopastoral, and further developed by Maggie Appleton, who wrote the most comprehensive history and analysis of the concept in 2020. The metaphor contrasts with the "stream": the feed-based, chronological, performative mode of content that dominates social media and most blogs. The stream rushes past. The garden grows slowly, can be tended to over years, and rewards wandering rather than scrolling.

Caulfield's core observation was that the web had become mostly a tool for self-expression rather than a tool for thought. The stream prioritises recency and reaction. The garden prioritises accumulation and connection. In a garden, an old note is no less valuable than a new one. Ideas link to each other in ways that reveal relationships you couldn't see when each note was written. The garden grows more interesting the longer you tend it.

The idea has roots in personal wikis, hypertext literature, and the early web's ethos of linked, non-linear information. But it gained broader cultural traction in 2020, particularly among people working with tools like Roam Research and Obsidian, as a way of thinking about the relationship between personal knowledge management and public publishing.

Garden vs stream

The distinction is worth dwelling on because it explains why digital gardening feels different from blogging.

A blog is a stream. Posts are dated, presented in reverse chronological order, expected to be complete, and implicitly settled. A post published in 2019 is an artefact of 2019. You might update it occasionally, but the expectation is that a published post is finished.

A digital garden is topography, not timeline. Notes are presented by their relationships and content, not by when they were written. A note might be a rough early idea; it might be a well-developed piece of thinking built up over years. Both belong in the garden. The point is the network, not the publication date.

This changes what it feels like to write in public. Blogs implicitly demand that you have something to say before you publish. Gardens allow you to think out loud, to publish half-formed ideas with the expectation that they'll grow, to show your working as it happens. The imperfection is part of the point.

The six patterns

Maggie Appleton identified six patterns that characterise digital gardens, which she described in her 2020 essay:

1. Topography over timelines. Navigation by theme, concept, and connection rather than by date. You wander through a garden; you scroll through a stream.

2. Continuous growth. Notes are expected to change. You return to a note when you learn something new that relates to it, add the new perspective, update the formulation. The garden is never finished.

3. Imperfection and learning in public. Ideas are published before they're ready. The process of developing an idea is visible, not hidden. This is the opposite of most academic and professional publishing norms.

4. Playful, personal, and experimental. Digital gardens tend to reflect their authors as individuals in a way that blogs often don't. The form encourages experimentation with structure, presentation, and voice.

5. Intercropping and content diversity. Gardens mix different types of content: fleeting notes, long essays, lists, resources, sketches, book notes, quotes. A blog has posts; a garden has everything.

6. Independent ownership. Gardens tend to be self-hosted or on platforms the author controls, reflecting a preference for owning your own information rather than publishing on platforms that can change or disappear.

Note maturity stages

One useful practice in digital gardens is tagging notes by their stage of development. Appleton uses a botanical taxonomy:

Seedlings: rough, early ideas. A thought worth capturing and returning to, but not yet developed. These might be a paragraph or a few sentences.

Budding: notes that have been worked on, have some structure, and are becoming more coherent. Still in development.

Evergreen: mature notes that represent your best current thinking on a concept. Well-developed, refined over time, ready to stand on their own.

This taxonomy is honest about incompleteness in a way that most publishing isn't. A note doesn't have to be finished to be published. The label does the work of setting expectations.

This connects directly to evergreen notes as a concept: the most mature notes in a digital garden are evergreen notes in Matuschak's sense, written and organised to evolve over time.

Digital gardens and Zettelkasten

The concepts overlap significantly. Both are built around linked notes that accumulate over time and generate unexpected connections. Both reject the folder-and-hierarchy approach to organisation in favour of networked knowledge.

The main practical difference is audience. A Zettelkasten is primarily a private thinking tool. A digital garden is a public one. The notes in a Zettelkasten are written for yourself, by default; the notes in a digital garden are written with the awareness that others might read them. This affects how you write: a bit more context, a bit more care about explanation, even if the audience is small.

Caulfield's garden metaphor and Luhmann's Zettelkasten share the conviction that accumulation and connection are more valuable than any individual note. The garden just takes this public.

Starting a digital garden

The simplest possible digital garden is a collection of interlinked notes on a public website, where the notes are connected by content and can be browsed by topic. You don't need custom software or technical skills, though many people with those skills build elaborate tools to bring gardens to life.

A few decisions to make before you start:

How public is it? Some gardens are fully public, discoverable by search engines. Others are published online but not promoted or indexed. Others are shared only with specific people. There's no obligation to make it broadly public if your goal is thinking rather than audience.

How linked are the notes? The more links between notes, the more garden-like it feels. Unlinked notes published online are a collection of articles; densely linked notes are a proper garden. Building the habit of linking each new note to existing related notes is the most important practice.

How do you handle incompleteness? Decide whether you'll use a maturity system (seedlings, budding, evergreen), a status label (draft, developing, stable), or no labelling at all. Some transparency about the stage of a note is useful for readers and honest about the nature of the work.

What goes in? Gardens work best with diversity: some long developed pieces, some rough ideas, some useful links, some book notes, some resources. Starting with what you're already writing or thinking about is better than trying to design the perfect structure before you have any content.

For the personal knowledge layer that feeds a digital garden, Fabric's notes and docs and search work well for capturing and connecting ideas privately before they're ready to publish. The publishing feature can turn a folder into a public, searchable page, which is one way to create the public layer without a separate website.

What digital gardens are good for

Digital gardens suit people who think in public, who want their ideas to accumulate and connect, and who are interested in the process as much as the product. Researchers, writers, designers, developers, educators, and anyone whose work is primarily intellectual and who wants a space that reflects their thinking over time.

They're less suited to people who primarily want to broadcast finished work to an audience, build a professional portfolio of completed projects, or reach a large readership. For those purposes, a traditional blog or portfolio site serves better.

The most compelling digital gardens are deeply personal. They reflect a specific person's way of seeing, the connections they find interesting, the questions they're sitting with. That particularity is what makes them interesting to read, even when the individual notes are rough.

Digital gardens and other systems

Zettelkasten: The private version of a digital garden in some ways. Both are built around networked atomic notes. A digital garden is often the public expression of a Zettelkasten-style thinking practice.

Evergreen notes: The mature, developed notes in a digital garden are evergreen notes. The seedling/budding/evergreen taxonomy maps directly onto Matuschak's note development model.

Building a Second Brain: BASB is oriented toward personal capture and creative output. A digital garden is one possible output channel for the express step, where you take what you've developed privately and publish it in an exploratory, evolving form.

Commonplace book: The digital garden is a modern, linked, public version of what a commonplace book was in the pre-digital era: a personal collection of interesting passages, ideas, and observations accumulated over time.

Note-taking basics: The note-taking basics guide covers the foundation; digital gardening is one approach to what you do with notes once you've developed a practice of taking them well.

Frequently asked questions

Do I need to know how to code to build a digital garden?

Not necessarily. Tools like Obsidian Publish, Roam Research's publish feature, and Notion allow you to publish notes publicly without coding. For more control over the appearance and structure, tools like Jekyll, Hugo, and Gatsby are popular among the technically inclined. Fabric's publishing feature lets you publish any folder as a public, searchable page without technical setup.

How is a digital garden different from a personal wiki?

The concepts overlap. A wiki is typically more reference-oriented: it aims to be accurate, complete, and collaborative. A digital garden is more exploratory and personal: it reflects ongoing thinking rather than settled knowledge. Many digital gardens function as personal wikis, but the garden framing emphasises growth and incompleteness where wiki implies something more authoritative.

How much should I write before publishing?

Appleton's answer is that publishing incomplete ideas is the point. A seedling note might be a paragraph. The expectation is that readers understand they're encountering thinking in progress, not finished work. The discomfort of publishing rough ideas is worth getting comfortable with if you want a real garden rather than a curated portfolio.

What should I do if nobody reads my garden?

Most digital gardens have very small audiences, and that's fine. The primary value of a digital garden is the practice of maintaining it: the thinking, the connecting, the gradual accumulation. Readers are a bonus. Caulfield's framing is useful: the garden is for thought, not for self-expression or audience-building. If you're gardening to get readers, you'll probably be disappointed; if you're gardening to think better, the audience is secondary.

What's a good first note for a digital garden?

Something you're already thinking about, not something you feel obligated to publish. A rough note on a question you've been sitting with, a summary of something you read recently that surprised you, a half-formed idea about your own work. The entry point doesn't matter much; what matters is starting the habit of writing, linking, and publishing rather than waiting until you have something finished to say.