Builds
A build represents a version of your website.
Micropage converts your markup into a static site and deploys it to Cloudflare's network, where it is served over HTTPS.
Build lifecycle
- Raw markup files
- Parsed into structured JSON
- Static site generated
- Uploaded to Cloudflare R2 storage and served by a Cloudflare Worker
Save, Publish, Redeploy
- Save creates a draft build. The live URL does not change.
- Publish means this markup is live. The current markup is built and deployed.
- Redeploy makes an older build live again.
Only one build is live at a time. Publishing replaces the current live build.
Using the Web App
Save a draft: click Save in the editor toolbar. The live site does not change.
Publish: click Publish. The current markup is built and deployed. The live site updates.
View build history: open the Builds tab to see all builds with status and timestamp.
Redeploy an older build: click Redeploy next to any build in the Builds tab. That build becomes the active build and the publishing pipeline runs again for the same version (no duplicate build row).
Download a build as a zip: available on Pro and Pro+, from the Builds tab.
Using the CLI
The CLI ships on Pro and Pro+. On Free, use the web app.
Save a draft:
micropage push
Publish:
micropage publish
List builds:
micropage builds list
Redeploy an older version:
micropage builds redeploy 3
Download a build archive (Pro and Pro+):
micropage builds download 3
Downloading a build
The zip is the generated static site. Host it on Cloudflare Pages, Netlify, S3, or your own box.
The download is the paid convenience, not access to your work. Your source .page file is always yours, including on Free — copy it out of the editor at any time.
Build retention
Micropage keeps the most recent builds per project. Older builds are pruned automatically when new ones are created.