What Is a Digital Garden? The Complete Guide (2026)

What Is a Digital Garden?

You have a folder, or a drafts app, full of half-finished thoughts. Notes you will "clean up and publish someday." Ideas that never became blog posts because they were not polished enough to broadcast, and so they sat there, private and inert. That gap, between the thinking you actually do and the finished work you are willing to show, is the exact gap a digital garden closes.

A digital garden is a space where you keep your notes in the open and grow them over time. Each note is a small, linked page, and the pages connect to each other by meaning rather than by date. There is no "latest post" and no archive of old ones. There is a network of ideas at different stages of ripeness, some just planted, some half-grown, a few fully evergreen, all visible and all still editable.

I am a documentary filmmaker, and I built Storyflow, a visual thinking workspace, after running multiple film projects from first research through pre-production. A documentary is a garden before it is a film: you tend the same pile of sources, interviews, and half-theories for months, and the throughline only appears once the connections between them do. I have kept private research gardens for every project I have made, and the lesson is always the same. The value was never in any single note. It was in the links I could see between them. Working memory does not help here: Cowan's research (Behavioral and Brain Sciences, 2001) put its capacity at roughly four chunks at once, so the connections have to live somewhere outside your head.

That external place is the point, and the mindset behind it is worth naming: the shift from publishing to planting. A blog runs on a publishing mindset. You finish a piece, stamp it with a date, broadcast it, and move on. A garden runs on a planting mindset. You put a rough note in the ground, link it to what it relates to, and come back to tend it when you learn more. Almost everything else about digital gardens follows from that one shift from publish to plant.

How a Digital Garden Differs From a Blog

A blog is a broadcast. A garden is a growing thing. That line is the whole distinction, but it is worth unpacking, because the differences are structural, not cosmetic.

A blog is chronological. The newest post sits on top, and a post's value is assumed to decay as it slides down the feed. A garden is topographical. Notes are arranged by how they relate to each other, so an idea you first planted two years ago can sit right next to one from this morning if that is where the meaning puts it.

A blog post is finished. You publish it, and revising it later feels almost dishonest, like editing the past. A garden note is unfinished on purpose. It is expected to be imperfect, and updating it is the entire point rather than a correction you are embarrassed about. This is what people mean by "learning in public": you show the work at every stage, not just the final cut.

A blog is written for an audience. A garden is written for yourself first, and shared in case it helps someone else. That flips the incentive. You stop performing expertise you do not have yet and start recording what you are actually figuring out. The imperfection is not a flaw you tolerate. It is the feature that makes the whole thing sustainable.

Where Digital Gardens Came From

The idea is older than the phrase. In 1945, Vannevar Bush described the "Memex," a desk that would let a researcher link documents together by association rather than filing them in a strict hierarchy. That associative link, one idea pointing directly at another, is the seed every digital garden grows from.

The gardening metaphor itself was made explicit by Mark Bernstein in his 1998 essay "Hypertext Gardens: Delightful Vistas." Bernstein argued that good hypertext should be cultivated like a garden, balancing wildness and order so a reader can wander without getting lost. It is the founding text most gardeners point back to.

The modern revival has a clearer origin. In 2015, educator Mike Caulfield gave a talk called "The Garden and the Stream: A Technopedia," which framed two ways of being online: the Stream (the dated, flowing feed of blogs and social media) and the Garden (the slow, cross-linked, revisited space of wiki-like notes). Caulfield's garden-versus-stream distinction is the one most 2020s gardeners inherited.

Around 2020, the practice caught fire. Maggie Appleton's essay "A Brief History and Ecology of Digital Gardens" cataloged the patterns that define the form, and Anne-Laure Le Cunff's "Nurture your mind with a digital garden" reframed it as a tool for thinking rather than an audience play. A wave of developers published their own gardens, and the tooling followed. A blog is a broadcast. A garden is a growing thing, and the 2020 revival was mostly a rediscovery of that older, slower way of writing online.

Blog vs Digital Garden vs Wiki: What Actually Differs

People lump these three together because all of them are "collections of pages." The differences that matter are how they are ordered, whether the pages are ever finished, how they link, and who they are for.

The garden sits between the blog and the wiki. It has the personal voice and single author of a blog, and the dense internal linking and non-chronological structure of a wiki, but unlike a wiki it never pretends to be finished or objective. A digital garden is a wiki with a personality and no deadline. That is the honest one-line definition if the table is too much.

The Four Principles Every Digital Garden Shares

Strip away the tools and the aesthetics, and every digital garden runs on the same four principles. Maggie Appleton cataloged a longer list of six patterns in 2020; these four are the ones that actually change how you work.

Topography Over Timeline

Order your notes by how they relate, not by when you wrote them. A blog buries an old idea under newer ones; a garden puts related ideas next to each other regardless of age. The date a note was written stops being its address. Its links become its address instead. This is the principle Appleton names "topography over timeline," and it is the one that most cleanly separates a garden from a feed.

Continuous Growth

A note is planted small and grown over time. You do not wait until an idea is fully formed to write it down. You capture the seedling and add to it as you learn. The corollary is that nothing is ever truly done. A three-year-old note you still edit is not a failure to finish. It is a garden working as designed. This is the planting mindset in practice: you tend, you do not ship.

Bidirectional Links

The connection between two notes is a first-class object, and it works in both directions. When note A links to note B, note B knows it is being referenced by A. These backlinks are what turn a pile of pages into a network, because they let you arrive at an idea and immediately see everything else that touches it. The note-taking tools of the 2020s finally made two-way links normal, decades after Ted Nelson first argued for them. In a garden, the link is not a footnote. It is the structure.

Epistemic Status

A garden is honest about how sure you are. Because notes are public while still unfinished, gardeners label each note's maturity so readers know what they are looking at. The most common convention, popularized by Maggie Appleton, uses three stages: seedling for a rough early thought, budding for an idea taking shape, and evergreen for a note you have tended into something stable. Marking epistemic status is what makes it safe to publish something imperfect. You are not claiming it is true. You are showing where it is in its growth.

The Tools People Use to Grow One

There is no single "digital garden app," which surprises newcomers. A garden is a format, not a product, and gardeners assemble it from whatever tool matches how they think. Four broad options cover almost everyone.

For publish-to-web gardens, Obsidian plus Obsidian Publish leads. You write linked markdown notes locally, then publish the ones you choose as a public, browsable site with working backlinks. Obsidian owns this lane because the notes are plain files you keep forever and the published garden preserves the link structure. The open-source Quartz project does something similar for free if you are comfortable with a static site.

For no-code gardens, Notion works. Public Notion pages with internal links get you a garden without touching a terminal, and the low friction is the draw. The trade-off is lighter backlinks and pages that read more like a wiki than a living garden.

For developer gardens, static-site generators like Jekyll, Eleventy, and Gatsby dominate. Templates such as the popular digital-garden Jekyll template, plus tools like Foam in VS Code and TiddlyWiki, give full control over the look and the linking. The cost is setup and maintenance time.

For the private thinking side, a visual canvas fits. Not every garden is meant for the public web. Much of the actual gardening, the tending of rough, interconnected notes, happens privately before anything is ever shared. This is the friction a canvas tool addresses. On a Storyflow board, a note is a card and a connection is a line you draw between cards, so the relationship between two ideas is something you can see and rearrange rather than a backlink buried in metadata. The AI reads your full active canvas board by default, plus up to 1 Tactic and up to 3 Documents you @-mention in the chat, so you can ask it to surface a missing link between two cards and it reasons over the actual board. For growing and connecting ideas visually, that is the planting mindset with a map.

Storyflow is deliberately the private half of this, and it is worth being blunt about where it does not fit, because pretending otherwise would undercut the point. Storyflow is not a publish-to-web digital garden tool: you cannot turn a board into a public, browsable website of backlinked notes the way Obsidian Publish or a Jekyll garden does, so for a public garden you want one of those instead. It is cloud-only, with no local-first or offline mode, so for notes you need to own as plain files on your own disk, Obsidian wins outright. And it is a newer platform with a smaller ecosystem and fewer templates than Notion or Obsidian have built over a decade. The tool only matters once you have decided which half of the garden, the private tending or the public showing, you are actually building.

How to Start a Digital Garden

You do not need permission, a domain, or a design. You need a place to put linked notes and the willingness to plant rough ones. Five steps get a garden growing.

1. Pick where it lives. Decide public or private first. For a public web garden, choose Obsidian Publish, a Quartz or Jekyll template, or public Notion. For private tending, a canvas or a local Obsidian vault. Do not agonize; you can move notes later.

1. Plant three seed notes, not a homepage. Skip the "about this garden" page. Write three short notes on things you are actually thinking about right now, one idea each. Rough is correct. Seedlings are supposed to look like seedlings.

1. Link them to each other. Find the connection between at least two of your three notes and make the link explicit. A garden with three linked notes is already a garden. A hundred unlinked notes is just a folder.

1. Label maturity. Mark each note seedling, budding, or evergreen. This one habit gives you permission to publish before you are ready, which is the barrier that stops most gardens before they start.

1. Tend on a schedule, do not publish on one. Instead of "post every Tuesday," set a recurring time to wander your own garden, expand a note, add a link, or promote a seedling to budding. The garden grows through tending, not through shipping.

The whole method is captured in the shift this guide keeps returning to: you are not publishing, you are planting. Start smaller than feels respectable, link relentlessly, and let the structure emerge.

Which Approach Should You Use?

Match the format to what you actually want, not to what looks impressive.

If you want reach and rhythm, keep a blog. Chronological, finished, broadcast posts are still the best format for growing an audience on a cadence. A garden makes a poor newsletter.

If you want your thinking to compound, grow a garden. If you keep having the same ideas, re-researching the same topics, and losing the connections between them, a garden is the fix. It rewards revisiting over shipping.

If you want both, do what experienced gardeners do: tend a private garden of linked notes, and harvest the occasional evergreen note into a polished blog post or newsletter when it is ready. The garden feeds the broadcast.

The bottom line: a digital garden is not a fancier blog. It is a different shape of writing entirely, ordered by links instead of dates, tended instead of published, and honest about being unfinished. A blog is a broadcast. A garden is a growing thing. If your ideas are dying in a drafts folder because they are not polished enough to publish, stop trying to publish them. Plant them instead. Take the ten notes you have been meaning to "clean up someday," put them on one surface, link the ones that relate, and tend that for a month. By the end you will have something no blog gives you: a map of how you actually think, growing in the open. Start a private thinking garden on a Storyflow canvas.

Author

By Justkay, Documentary Filmmaker and Founder of Storyflow. I have kept private research gardens of sources, interviews, and half-formed theories across multiple documentary projects, and the throughline always lived in the links between notes, not the notes themselves.