Why Micropage has a blog
Micropage started as a tool, not a story. You write a .page file, it becomes a website. Clean, fast, done.
But tools need context. The docs cover the what — what syntax to use, what commands to run, what a build is. This blog covers the why — why we made certain trade-offs, what we shipped, how things work under the hood.
What you’ll find here
We use this blog for a few things:
- Tutorials — deeper walkthroughs that go beyond the reference docs. Things like “building a launch page from scratch in 10 minutes” or “how to use forms to collect signups.”
- Product updates — when we ship something meaningful, we write it up here instead of just bumping a changelog nobody reads.
- Behind the scenes — Micropage is a bootstrapped, opinionated tool. We occasionally write about the decisions behind it: why the markup format looks the way it does, how the build pipeline works, why we chose Cloudflare Pages and Cloudflare for SaaS.
- Release notes — for releases that need more than a bullet point.
Where it lives now (and why that changed)
This blog used to live inside the documentation site, at docs.micropage.sh/blog. That made sense when the docs were the only thing we’d built worth reading.
It doesn’t live there anymore. The blog now runs on Micropage itself — these posts are authored with the same .page-and-Posts workflow you’d use for your own site, and served from micropage.sh/content. Old /blog/* links redirect here.
The move was deliberate. The most honest test of a publishing tool is whether we’re willing to publish with it, so our own blog is now a dogfood of the Posts feature: write a Markdown post, micropage posts publish, and it’s live on the web (and optionally emailed to a list). If it’s good enough for our updates, it’s good enough for yours.
What comes next
We keep the full documentation current — the CLI, the markup format, forms, builds, newsletter, and custom domains — and this blog accompanies it with practical examples and updates as we ship.
If there’s something specific you’d like to see covered, micropage.sh is where to start.