How to Start a Markdown Blog in 2026
You want to start a blog. You’ve decided on markdown. Good choice — portable, readable, future-proof. Now you need to figure out how to get those .md files onto the internet.
This is where it gets complicated. Not because there aren’t options. Because there are too many, and they all optimize for different things.
I’ve tried most of them. Here’s what I’ve learned.
The Four Paths
Every markdown blogging tool falls into one of four categories:
- Static site generators — you build the site yourself
- Hosted platforms — someone else runs everything
- Minimal blogging tools — stripped-down, writing-first
- File-based publishing — your files become your site
Each makes a different bet about what matters most. The right choice depends on what you actually care about — not what sounds impressive on a landing page.
Static Site Generators: Hugo, Jekyll, Astro
These are developer tools. You write markdown, run a build step, and deploy HTML files to a hosting service.
Hugo is fast. Absurdly fast. Thousands of pages build in milliseconds. Its templating language is confusing until it clicks, then it’s powerful. The Go ecosystem means a single binary — no dependency hell.
Jekyll is the original. GitHub Pages runs it natively, so deployment is “push to a repo.” It’s slower than Hugo and the Ruby dependency chain can bite you, but the ecosystem of themes and plugins is mature.
Astro is the modern option. Component-based, framework-agnostic, excellent performance. If you’re already writing React or Svelte, Astro feels natural. If you’re not, it’s a lot of machinery for a blog.
What they cost: Free to host (Vercel, Netlify, GitHub Pages), but expensive in time. Expect a weekend of setup before your first post goes live. Longer if you want it to look good. Theme selection alone can eat an afternoon — I know because I’ve lost entire weekends to it.
Who they’re for: Developers who want full control over every pixel and don’t mind a build step. If you enjoy tinkering with templates and config files, this is your path. If the word “build pipeline” makes you tired, keep reading.
Hosted Platforms: Ghost, WordPress, Substack
These give you everything: editor, hosting, audience tools, analytics.
Ghost is the best CMS for writers who want a professional publication. Clean editor, built-in newsletters, membership and payments. The markdown support is real — the editor renders it live. Self-hosting is an option. Managed hosting starts at $15/month.
WordPress powers more than 40% of the web and has markdown support through plugins or the block editor’s markdown shortcuts. It does everything. That’s the problem — it does everything. A blog shouldn’t need a security plugin.
Substack is free to start, takes 10% when you charge for subscriptions. The distribution is real — people discover you through the Substack network. The tradeoff: your content lives on their platform, your audience is in their system, and your options narrow if you leave. The export situation hasn’t improved much.
Who they’re for: Ghost is genuinely excellent for professional publications and newsletters. WordPress is for people who need an ecosystem of plugins. Substack is for writers who value built-in distribution more than ownership. Each is a legitimate choice with clear tradeoffs.
Minimal Blogging Tools: Bear Blog, Mataroa, Write.as
These strip away everything except writing and publishing.
Bear Blog gives you a blog with no trackers, no JavaScript, and a chronological feed. It’s almost aggressively simple. Free tier, paid plan for custom domains and extras.
Mataroa is similar — markdown in, blog out, nothing else. Clean and opinionated. No analytics, no comments, no nonsense.
Write.as goes further with federation support, letting your blog connect to the fediverse. Minimal editor, privacy-focused, paid plans starting at $6/month.
Who they’re for: Writers who want to publish and nothing else. The limitation is real — you write in their editor, on their platform. If you already have a markdown workflow in your own editor, you’re giving that up.
File-Based Publishing: FolderPress
This is the tool I built, so take the following with appropriate skepticism.
FolderPress connects to a folder in your Dropbox. Save a markdown file, it’s a page on your site. Rename it, the URL changes. Add .draft to the filename, it’s unpublished. The folder is the CMS.
What it costs: There’s a free tier. Paid plans for custom domains and additional sites. No build step. No editor to learn. No dashboard to manage content.
What it doesn’t do: No themes to choose from — your site gets clean typography and a reading-focused layout. No plugin ecosystem. No built-in analytics. No comments system. If you want to customize your site’s design, this isn’t the tool.
Who it’s for: People who already write markdown in an editor they love, already sync through Dropbox, and want the shortest possible path from “I saved a file” to “it’s on the internet.” That’s a narrow audience, and I’m fine with that.
The Decision Framework
Instead of comparing feature lists, ask yourself five questions:
How much do you want to build? If tinkering is part of the joy, go with a static site generator. Hugo for speed, Astro for modern tooling, Jekyll if you’re already on GitHub Pages. If you want zero setup, look at the minimal tools or FolderPress.
Do you need audience tools? Newsletters, memberships, paid subscriptions — Ghost does this well. Substack does it with less control but more built-in distribution. If you just want to put words on the internet, you don’t need any of this yet.
How much do you care about ownership? Markdown files on your computer are yours forever. Every static site generator gives you this. FolderPress gives you this — your files live in Dropbox, readable with any text editor, with or without FolderPress. Hosted platforms give you an export button and varying degrees of portability.
What’s your budget? Static site generators are free to host. Bear Blog and Mataroa have free tiers. Ghost starts at 25+/month managed.
Will you actually write? This is the question that matters most. The best blogging setup is the one that doesn’t get in the way of writing. For some people that’s a powerful CMS. For others it’s a text file and a save button. Be honest about which one you are.
Why Markdown at All
Regardless of which tool you choose, writing in markdown gives you something no proprietary format can: independence.
Your files work in every text editor on every operating system. They convert cleanly to HTML, PDF, EPUB. They’ll be readable in thirty years. AI tools already speak markdown natively — paste a draft into any LLM and the formatting survives the round trip.
A deeper look at why markdown outlasts every CMS is worth reading if you’re on the fence.
Pick One and Write
The tool doesn’t matter as much as you think. I mean that. I’ve spent more hours evaluating blogging platforms than I’ve spent writing blog posts, and I suspect I’m not alone.
The best time to pick a platform is today. The best time to write your first post is today. If you pick wrong, markdown makes switching easy — that’s the whole point of the format.
Your words are more durable than any tool you publish them with.