Skip to main content

Builds

A build represents a version of your website.

Micropage converts your markup into a static site and deploys it to Cloudflare Pages.

Build lifecycle​

  1. Raw markup files
  2. Parsed into structured JSON
  3. Static site generated
  4. Deployed to Cloudflare Pages

Draft vs deployed​

  • A draft build is saved but not live. Editing and saving in the web app creates a draft.
  • A deployed build is the active version of your site.
  • 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).

Using the CLI​

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:

micropage builds download 3

Build retention​

Micropage keeps the most recent builds per project. Older builds are pruned automatically when new ones are created.