Cloudflare static deployment guide
The value of a static site is not only low hosting cost. It has a smaller build surface, predictable delivery and a straightforward path back to a known Git version.
Keep production as simple as possible.
The main branch contains deployable HTML, CSS and JavaScript. Cloudflare Pages pulls from Git and distributes through its CDN. Large changes should use preview branches before production merge.
Production branch
Keep main limited to files that have passed checks.
Preview branches
Review major UI, content and structural changes before production.
Custom domains
Set primary domain, www, HTTPS and redirects intentionally.
Security and rollback
Include headers, version history and recovery in the release process.
Typical scope
Understand the current workflow
Map current tools, people, data and the real bottleneck.
Ship the useful core
Deliver the highest-value part that can be verified quickly.
Expand after real use
Add features, automation and integrations based on real usage.
Common questions
Does a static site need a build command?
If the repository already contains final HTML, CSS and JavaScript, a build step may be unnecessary depending on Pages settings.
Why use preview branches?
They let the team review mobile, desktop, links and content without affecting production.
Start with one concrete problem.
Tell us where the work is slow, error-prone or hard to manage. We will suggest a practical first phase.