DEV Community: Asdra

The Way of Markdown

Asdra — Fri, 04 Sep 2026 21:32:41 +0000

Markdown quietly won. Google Docs speaks it, WhatsApp speaks it, Slack and Discord speak it, every AI chat speaks it — and almost nobody notices, because markdown itself was never really the point. What you can build on top of it is.

We've been contributing to The Way of Markdown, a free site that makes the case for working this way: keep your content as plain files you actually own, then build whatever you need on top of them — a website, a knowledge base, a wiki, even something Notion-shaped — using tools you can swap out whenever you want. No renting a platform, no lock-in.

A few things worth knowing about it.

It's a real guide library, not just a manifesto with nothing behind it. There are 25 guides so far — eleven cover markdown in specific apps like WhatsApp, Slack, Discord, Notion, ChatGPT, Google Docs, Obsidian, GitHub, Reddit and Telegram (Apple Notes gets one too, as the last real holdout), and the other fourteen walk through what to actually build: websites, wikis, docs, databases, blogs, digital gardens, a proper way out of Notion, and more.

It also practices what it teaches. The whole site is just markdown files sitting in a public GitHub repo, published with Flowershow — every single page has an "edit this page" link that goes straight back to the source. Full disclosure since it matters: Flowershow is our tool, so of course it gets recommended. But every guide names the real alternatives too — Hugo, Jekyll, Astro, MkDocs, Docusaurus — because the whole point of working this way is that the tools stay swappable. Ours included.

The part we think doesn't get enough credit: markdown has basically become the default language AI reads and writes. That's not a stylistic choice on their part — it's just what they were trained on. If your notes live in plain markdown, an AI agent can read them, edit them, reorganize them directly. If they're stuck inside a proprietary format, there's an export button standing in the way first.

If you're in the middle of getting out of Notion, or you're just tired of your notes app fighting your AI tools instead of working with them, it's worth a look: wayofmarkdown.com

Notion vs Markdown: the honest comparison

Asdra — Fri, 28 Aug 2026 22:16:16 +0000

"Notion vs Obsidian" is the wrong framing — that's app vs app. The real comparison is app vs stack: can a markdown setup give you what Notion gives you, out of files you actually own? Mostly yes. Sometimes better. Occasionally, no.

We ran the full comparison on The Way of Markdown. It's not a hit piece — Notion wins some of these outright. Here's the shape of it.

Notion isn't competing against "markdown" — that's just a format — it's competing against a small stack: Obsidian for the editor, Bases for database-style views over your files, git for sync and history, a publisher for the "share to web" button, and AI tools that read your files directly.

A few categories go one way or the other with no real contest.

Markdown wins wikis and linking (native, not bolted on), offline use (total — the files just sit on your disk), history (a full git log going back to day one), lock-in and exit (there's nothing to export, because nothing was trapped to begin with), and AI on your content (agents work directly in your vault, no API required).

Notion wins real-time co-editing — genuinely good, and git is asynchronous by design so this isn't close. It wins page-level permissions, since repo-level access is the ceiling on the markdown side. And it wins zero-setup polish: sign up versus assembling two or three tools yourself.

Databases are closer than people assume. Notion's relational views are still ahead for heavy use, but Obsidian Bases closed most of the gap this year for lighter use — which covers most people's actual needs.

The trend line matters more than the snapshot. The database gap has been closing from the markdown side, and AI closed the smart-features gap from the other side, almost overnight. Meanwhile Notion's real advantages — real-time editing, granular permissions — come from the same centralized database that creates the lock-in. You can't get one without the other, in either direction.

Full scorecard (14 categories, feature by feature) and the honest "choose X if" breakdown: wayofmarkdown.com/notion-vs-markdown

The Markdown Database Pattern

Asdra — Fri, 28 Aug 2026 00:13:10 +0000

Your filesystem is already a database. Most tools just don't treat it that way.

That's the core idea behind the Markdown Database Pattern — written up properly on The Way of Markdown, a site we've been contributing to that makes the case for building things on plain markdown instead of locked-in platforms. We think it's a pattern worth more attention, so here's the short version.

Treat a folder of markdown files as a database. Each file is a record. Frontmatter fields are columns. Directories are tables. Tags, wikilinks, and tasks in the body become queryable relations.

Filesystem              Database
──────────────────────────────────
markdown file      →    record
frontmatter field  →    column
directory          →    table
#tag               →    tag relation
[[wikilink]]       →    link relation
- [ ] task         →    task relation

You get portability, version control (git works perfectly on plain text), no framework lock-in, and full queryability. You give up scale and real relational joins — this isn't for millions of records. It's a lightweight database, honest about its limits.

Once you name it, you start seeing it everywhere. Obsidian Bases and Dataview already do versions of this, half-consciously. A team wiki where every page has a status and owner field is one. A blog with date and tags in frontmatter is one — it just doesn't know it yet.

Sweet spot: up to roughly 10k files. Past that, reach for a real database. Below it, this gets you almost everything a database gives you, at a fraction of the complexity, with none of the lock-in.

The full writeup — the complete tradeoff analysis, a worked example with actual queries, how to implement it in a weekend, and the tool (MarkdownDB) that does it for you — is here: wayofmarkdown.com/markdown-database