You’ve been collecting notes for months. Maybe years. Ideas about your work, your craft, things you figured out the hard way. Some are polished. Most aren’t.

Now you want to put them on the internet. And the first question everyone asks is: should I start a blog or a digital garden?

It’s the wrong question.

#What People Mean When They Say “Digital Garden”

The term traces back to Mike Caulfield’s 2015 essay “The Garden and the Stream” and was popularized by people like Maggie Appleton, Andy Matuschak, and the tools-for-thought crowd.

The idea is simple. A blog is a stream — reverse chronological, each post a finished artifact with a date stamp. A garden is a network — interconnected notes that grow and change over time. No pressure to be polished. No obligation to be linear.

In a garden, you might have a page on “distributed systems” that starts as three bullet points and evolves into a full essay over two years. There’s no publish date because it’s never really “done.” Ideas link to other ideas. You tend them.

It’s a beautiful concept. And the people who do it well — Andy Matuschak’s working notes, Maggie Appleton’s illustrated garden — make it look effortless.

#The Problem Nobody Talks About

Most digital gardens are abandoned within six months.

Not because the idea is bad. Because the tooling is brutal.

The canonical path is: use Obsidian (great), install a static site generator (less great), configure a theme that supports backlinks and graph views (painful), set up a build pipeline (why), and deploy to Vercel or Netlify (fine, but now you’re debugging Node.js dependency conflicts instead of writing).

Obsidian Publish is the simpler option at $8/month, but it locks your site into Obsidian’s ecosystem and aesthetic. Quartz is free but requires you to maintain a GitHub repo and a build process.

The overhead is real. And it undermines the whole point of a garden — which is supposed to be low-friction, evolving, alive.

Blogs have the opposite problem. The tooling is mature. WordPress, Ghost, Substack — all straightforward to set up. But they impose a rigid chronological structure. Every post needs to feel “done” before you hit publish. That pressure is where most writing goes to die.

#The False Binary

Here’s what I think people actually want:

1. A place to publish rough ideas without guilt
2. A place to publish finished pieces when they’re ready
3. The ability to update anything at any time
4. A site that looks good without requiring a design degree or a build pipeline

That’s not a garden or a blog. That’s both.

The distinction between gardens and blogs is a tooling limitation, not a philosophical one. We treat them as different things because the tools that support one don’t support the other.

A static site generator can do backlinks and graph views but makes publishing feel like deploying software. WordPress can publish a polished post in minutes but makes iterating on old content feel awkward — everything’s trapped behind a dashboard, stamped with a date, implicitly “finished.”

#What If the Format Was Just Files?

Think about how files work on your computer.

You create a document. You save it. You come back to it later and change it. Sometimes you rename it. Sometimes you move it to a different folder. The file doesn’t care whether it’s a draft, a note, a finished essay, or something in between. It’s just a file.

That’s closer to how a garden works than any dedicated gardening tool I’ve seen.

A markdown file in a folder is the most natural unit of evolving thought. It has no publish date unless you add one. It has no status unless you give it one. It can be three bullet points today and a thousand-word essay next month. The file doesn’t impose structure. You do.

This is why I built FolderPress around files rather than a database. Your content lives as markdown files in a Dropbox folder. That’s it. No CMS. No build step. No deploy.

Want to publish a rough note? Drop a file in the folder. Want to update it six months later? Open the file and edit it. Want to move something from “draft” to “published”? Rename it. The file system is already a content management system — we just forgot.

#You Can Garden and Blog at the Same Time

The most productive writers I know don’t pick one mode. They do both.

They have a handful of evergreen pages — notes on topics they care about that grow slowly over time. And they have a stream of timestamped posts for things that are tied to a moment: announcements, reflections, tutorials.

The garden feeds the blog. A note you’ve been tending for weeks becomes the raw material for a polished post. The blog feeds the garden. Writing a post surfaces gaps in your thinking that send you back to your notes.

This isn’t a new insight. It’s how most writing actually works. Notebooks and essays. Drafts and publications. The private and the public.

The tools just need to get out of the way.

#How to Start Without Overthinking It

If you’re stuck choosing between a digital garden and a blog, try this:

Start with files. Create a folder. Put markdown files in it. Some will be rough. Some will be polished. That’s fine.

Don’t worry about backlinks and graph views. Those are nice features but they’re not what makes a garden a garden. What makes a garden a garden is the practice of returning to old ideas and developing them. You can do that with files and a folder structure.

Give yourself permission to publish incomplete thoughts. A note with three paragraphs and a heading is more useful to someone than a perfect essay you never write.

Update things. The most powerful thing about treating your site as a garden is that nothing is frozen. That post from eight months ago that’s slightly wrong? Fix it. That note you published as a stub? Flesh it out when you’re ready.

Use a publishing tool that doesn’t punish iteration. If updating a post requires logging into a dashboard, re-uploading, and re-publishing — you won’t do it. If updating a post means editing a file and saving — you will.

#The Best Personal Sites Blur the Line

Look at the personal sites you actually admire. Most of them aren’t purely chronological blogs or purely networked gardens. They’re something in between. A mix of evergreen reference material and timestamped writing. Notes alongside essays.

The garden-vs-blog debate is interesting philosophically. But in practice, the constraint isn’t the concept. It’s the tooling. Pick tools that let you publish easily, update freely, and own your files. The format will follow.

Your writing doesn’t need a category. It needs a home.