Why Markdown-based?

Rufus Pollock · updated July 2026

Here's a secret: nobody actually cares about markdown.

Markdown is a formatting syntax: a few conventions for headings, bold, links. Caring about markdown is like caring about ASCII. Learning it takes ten minutes, and that's not why this site exists.

What you actually care about is what you can do: publish a website, keep a knowledge base, run a blog, organize a catalog of books or recipes or research, collaborate on documents, build something Notion-shaped. Today, the default way to get those things is to hand your content to a platform (a CMS, a wiki service, a notes app) and accept its format, its editor, its pricing, and its exit barriers.

The markdown-based approach is the alternative: keep your content in plain markdown files, and get those same capabilities from an ecosystem of tools that work on top of them.

Why this wins

You own the files. Your content is a folder of plain text on your disk (and in your git repository). No export button needed — there's nothing to export from.

The format is open, so tools are interchangeable. Edit in Obsidian today, VS Code tomorrow, a phone app next week. Publish with Flowershow now, something else later. When your content isn't trapped inside a tool, switching tools is a choice, not a migration project.

Plain text is future-proof. Markdown files from twenty years ago open perfectly today; they'll open perfectly in fifty. Platforms die, formats rot — plain text doesn't.

It's the lingua franca of the AI era. Every major AI tool reads and writes markdown natively. A markdown knowledge base is one AI agents can directly read, edit, and organize — your notes become programmable.

Everything speaks it now. GitHub, Slack, Discord, Reddit, Google Docs, Apple Notes, every static site generator, every AI chat. The world has converged on markdown as the common tongue for structured text. That ubiquity is itself the argument: an investment in markdown is an investment the whole ecosystem keeps paying interest on.

The ecosystem is the point

One file of markdown is a note. A folder of markdown files plus the right tools is:

• a website or blog — publish with Flowershow or any static site generator
• a knowledge base or digital garden — wiki-links, backlinks, and graph views in Obsidian
• a database — files with structured frontmatter, queried and viewed like Notion or Airtable (see The Markdown Database Pattern)
• a collaborative workspace — versioned, branched, and reviewed with git and GitHub
• docs, books, papers — converted to anything via pandoc and friends

In other words: the markdown ecosystem can reproduce most of what proprietary platforms offer, without the lock-in. That's why we talk about a markdown-based approach: markdown is just the substrate; the value is in what's built on it.

Why the MOGF stack?

For building and publishing websites, our recommended starting stack is Markdown + Obsidian + GitHub + Flowershow:

• Markdown — the open format everything else operates on.
• Obsidian — a free, polished editor for markdown folders: live preview, wiki-links, thousands of plugins.
• GitHub — free hosting for your files with full history, plus branching, review, and collaboration when you need it.
• Flowershow — turns the repository into an elegant website automatically; push a change, the site updates.

Each piece is replaceable (that's the point) but together they take you from empty folder to published, collaborative, version-controlled website without writing code or paying anyone. The tutorial series walks you through exactly that.

The way of markdown

So "the way of markdown" isn't devotion to a syntax. It's a practice built on a simple principle: keep your content in open plain-text formats that you control, and choose your tools freely on top. Simplicity, portability, ownership — demonstrated, not proclaimed.

Want the declaration rather than the argument? Read The Markdown Manifesto.

Ready? Start learning.