Skip to main content

Deploy a Static Site to Cloudflare Pages Using Micropage

· 2 min read
Cosmin
Founder, Micropage

Micropage turns page markup into a deployed static site.

Under the hood, the publishing flow is based on builds and deployment to Cloudflare Pages.

The basic pipeline​

At a high level:

  1. write page markup
  2. save or push content
  3. Micropage parses the markup and creates a build
  4. the build generates static output
  5. the static output is deployed to Cloudflare Pages

Web App flow​

In the Web App:

  1. open a project
  2. edit content in the editor
  3. click Save to create a draft build (the live site does not change)
  4. click Publish to deploy the current markup

The app handles the build and deploy workflow for you.

CLI flow​

From the CLI:

micropage push
micropage publish

Use push to save a draft build without deploying.

Use publish to build and deploy immediately.

Why builds matter​

A build gives you a versioned snapshot of the site. That means you can always know:

  • what is currently live
  • what is still a draft
  • whether you can redeploy an older version

Redeploying a previous version​

If needed, you can redeploy an older build:

micropage builds redeploy 3

This is useful when you need to roll back to an earlier version without editing content again.

You can also redeploy from the Builds tab in the Web App.

Why Cloudflare Pages is a good fit​

The final output is static:

  • fast to load globally
  • easy to cache at the edge
  • no server to maintain

Custom domains​

By default, your site is available at a .pages.dev URL. You can connect your own domain using a CNAME record.

See Custom Domains for setup instructions.

Next steps​

If deployment makes sense, the next useful concepts are: