Digital Garden

A digital garden is a personal website built around evolving notes that link to each other, instead of a chronological feed of finished posts. The format trades the polish and timeliness of a blog for the interconnection and growth-over-time of a wiki. Pages are explicitly works-in-progress; revisions are normal, not embarrassing.

The term gained currency through Mike Caulfield's 2015 essay "The Garden and the Stream," which contrasts two web modes:

• The Stream — Twitter, blogs, RSS. Time-ordered, ephemeral, optimized for novelty. You consume, react, move on.
• The Garden — wikis, hypertext, digital gardens. Topology-ordered, persistent, optimized for revisiting and weaving connections. You walk paths, plant new ideas next to old ones, prune.

Quartz's philosophy page leans heavily on this framing. The garden metaphor isn't decorative — it specifies the affordances the tool needs.

The two modes ask for different skills, and picking the garden is partly a way of opting out of the stream's. Sarna and Dunlop's writing-for-developers is the craft manual for the side a garden skips: choosing a topic someone will actually read, structuring a post around one claim, editing, and shipping it once rather than tending it forever.

What makes a garden

Common conventions across digital gardens:

• Notes are continuously revised. A page is the current state of a thought, not a record of what the author thought on a specific date.
• Wikilinks dominate over chronological navigation. The reader follows interest, not time.
• Half-baked notes are published. The opposite of "publish only when polished" — Hamming's "door open" principle. Feedback compounds the value of each note.
• Frontmatter or visual cues mark maturity. Many gardens use 🌱 (seedling) → 🌿 (budding) → 🌳 (evergreen) to signal how settled a note is.
• No imposed hierarchy. Folder structure is light or absent; topology emerges from links.
• The graph is visible. A graph view, backlinks panel, or both, so readers see the network shape, not just one node at a time.

This is rhizomatic, not arborescent — to use the Deleuze/Guattari distinction Quartz cites. Tree structures (Notion-style nested pages, Zettelkasten's strict ID system) impose order before thinking. Rhizomes let order emerge from the linking pattern.

Relation to other PKM models

The digital garden is the public-facing cousin of several private knowledge-management practices:

• Zettelkasten is a private system for generating new ideas through atomic notes and forced linking. A digital garden is what happens when you publish a Zettelkasten and let readers walk through it. Mechanically related, philosophically different — Zettelkasten emphasizes upfront discipline (atomic notes, unique IDs); digital gardens accept messiness as the cost of low publishing friction.
• PARA (para-method) organizes notes by actionability — Projects, Areas, Resources, Archive. PARA is operational; gardens are exploratory. They can coexist (private PARA, public garden), but PARA's actionability axis doesn't naturally produce something publishable.
• LLM Wiki (llm-wiki-pattern) is a garden where the gardener is an LLM. The output structure — interconnected notes, frontmatter, no chronological feed — is the same. The maintenance discipline is delegated.

Tools

quartz is the most prominent dedicated digital-garden publisher. Other paths:

• Obsidian Publish — official Obsidian hosted publishing, paid, Obsidian-only.
• Astro + an Obsidian theme — popular for users who want a general-purpose SSG with garden-like rendering.
• TiddlyWiki — older tradition, single-file wiki with native garden ergonomics, predates the term.
• Notion shared workspaces — gardens by accident; possible but not native.

The defining test isn't the tool — it's whether the published site rewards walking versus scrolling. A WordPress blog can host a garden if the author writes garden-shaped notes; a Quartz site can host a stream if the author posts chronologically. The format is content-shaped, not engine-shaped.

Why it matters here

A digital garden is one viable publication target for the LLM Wiki this Second Brain follows. The vault structure (Markdown + wikilinks + frontmatter) already satisfies garden conventions; publishing requires only a render layer. The decision is whether the wiki is private-by-default with selective publication, or public-by-default with the garden as the primary surface. This wiki currently follows the former.