Most landing pages need at least one image: a hero image, a logo, a product screenshot, or an illustration.

Micropage keeps this simple by treating uploaded assets as project files that can be referenced from markup.

If you want to test Micropage quickly, the fastest path is simple: create a project, add one page, and publish it.

This guide shows the smallest possible flow to get a real page live.

Micropage is not limited to a single landing page.

You can define multiple pages and connect them through a shared navigation block using the same markup format.

A contact form is one of the first things people need on a landing page.

Micropage includes built-in form handling, so you can collect submissions without wiring your own backend for a basic contact workflow.

Micropage turns page markup into a deployed static site.

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

Forms are one of the few parts of a static site that usually force you to add backend logic.

Micropage includes a built-in form flow for basic use cases like contact and newsletter forms.

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.