How Micropage Works
Micropage converts a simple markup format into a fully deployed static site.
The product is the .page file, the Publish button, and the built-in forms. Everything below is how that gets served.
Pipeline
- Markup files (
.page) — you write plain text - Parser — converts markup to structured JSON
- Generator — builds a static site from the JSON
- Deploy — stored in Cloudflare R2 and served over HTTPS by a Cloudflare Worker (an implementation detail)
Why This Approach
- Simple markup — no HTML or templates to learn
- Fast builds — static output, no server-side rendering at request time
- Static hosting — deploys anywhere that serves static files; Micropage serves it from Cloudflare R2 through a Worker
- Built-in forms — form submissions are handled by the Micropage backend, not your site
Markup Format
A Micropage file is divided into blocks:
[site]— global site settings (title, description, logo)[nav]— navigation links[footer]— footer content[Page Name -> /path]— a page, with sections inside
Each page contains sections (/// hero, /// section) and elements (h1:, p:, img:, form:, etc.).
Images use the img: <- reference syntax, where the reference is a keyword (Unsplash), a filename (project file), or a direct URL. See Images.
See Your First Page for a hands-on introduction.