How to Build a Digital Garden in 2026: Setup Guide

A digital garden is a public notes site that looks more like a personal wiki than a blog. There are no dated posts. Notes are evergreen — updated over time rather than frozen on publish. Notes link to each other via backlinks. Readers arrive through search or links, not through a chronological feed.

Digital gardens have been quietly growing since 2020 as an alternative to the social-post economy. They are slower, more considered, and — at their best — more useful to readers than most blogs. Here is how to build one in 2026.

Step 1: Decide why

Before picking tools, be honest about why you want a garden. Valid reasons:

• A public home for notes you'd write anyway — thinking in public
• A reference site on a topic you know deeply
• A portfolio-adjacent site that shows how you think
• A way to publish half-finished ideas without blog-post pressure

Bad reasons: you saw one and it looked cool; you think it'll help your SEO; you want followers. These produce abandoned gardens.

Step 2: Pick a stack

Three realistic options in 2026:

Option A: Obsidian + Obsidian Publish. You write in Obsidian. You mark which notes to publish. Obsidian Publish renders them as a public site at $8/month. Easiest setup. No Git, no deploys, no config. Good default for people who already use Obsidian.

Option B: Obsidian + Quartz (free). You write in Obsidian. You use Quartz, a static-site generator specifically for digital gardens, to build and deploy a site to GitHub Pages, Vercel, or Netlify. Free, flexible, requires Git comfort. My preferred setup.

Option C: Astro / Eleventy with Markdown. You roll your own. Most control, most work. Good if you have specific design ambitions.

Avoid: Notion pages as a "garden." The URL structure and SEO properties are wrong. Avoid: WordPress. It fights the evergreen model.

Step 3: Pick a domain

Use your own domain. $12/year at Porkbun or Cloudflare Registrar. A subdomain of a personal site works (notes.yoursite.com). Avoid publishing under a free platform's domain because the URL is your garden's long-term address and you want to control it.

Step 4: Set up a basic structure

Most gardens benefit from three layers:

• Home page — brief intro, recent notes, entry points.
• Entry notes — high-level overviews on your main topics that link to deeper notes.
• Deep notes — specific ideas, observations, and evergreen content.

Don't over-structure at the start. You will learn what you need after writing 20 notes.

Step 5: Write the first notes

Start with notes you would write anyway. Summaries of books you read. Observations from work. Arguments you want to remember. The first 10 notes should not be ambitious — they should be easy wins so you publish.

Mark notes as "evergreen" or "seedling" or "budding" to signal to readers that you update them. This is a digital-garden convention that readers have come to expect.

Step 6: Link aggressively

The value of a garden is in the links. When you write a new note, link to existing notes. When you update an existing note, add links to new ones. Over time the graph fills in and the garden becomes denser, not longer.

Use Obsidian's [[note-name]] syntax. Obsidian Publish and Quartz both render these as links on the public site.

Step 7: Decide about comments

Most digital gardens skip comments. The slower, more considered pace suits the form better without a comment section. If you want reader interaction, use email — a mailto link is enough. Comment systems are a tax you don't need to pay.

Step 8: Publish in public

Deploy. Put the URL in your Twitter / Bluesky / LinkedIn bio. Start writing.

What to write (and what not to)

Write:

• Evergreen observations on your field
• Book / essay / article summaries with your commentary
• Tools and processes you've figured out
• Questions you're thinking about (half-finished is fine)

Don't write:

• Dated news posts (belongs on a blog)
• Personal diary content (write that somewhere private)
• Anything you'd regret being indexed permanently

Maintenance

Gardens require less maintenance than blogs. Update notes when you learn something new. Add new notes when you want to. Don't force a cadence. The "always on" pressure of blogs is exactly what gardens avoid.

When to stop

If the garden feels like work, stop. The whole point is publishing at the pace of your thinking, not at the pace of a content calendar. Abandoned gardens are better than forced ones.