Skip to main content

Why we added a blog to the docs

· 2 min read
Micropage Team
micropage.sh

Micropage started as a tool, not a story. You write a .micropage 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. The 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'll 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'll write it up here instead of just bumping a changelog nobody reads.
  • Behind the scenes — Micropage is a bootstrapped, opinionated tool. We'll 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.
  • Release notes — for releases that need more than a bullet point.

Why it lives inside the docs​

We considered a separate blog subdomain. We decided against it.

Having the blog at docs.micropage.sh/blog means one site to maintain, one deploy, one search index eventually, and one place users can go when they want to learn more about Micropage. The docs and the blog are two sides of the same thing: understanding how to use this tool well.

What comes next​

We're working on the full documentation for Micropage — covering the CLI, the markup format, forms, builds, and custom domains. The blog will accompany that 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.