Static-First Publishing
User-facing pages are generated as final HTML at publish time. No runtime rendering, no request-time content APIs.
Alpha Release
Static-First, File-Native
Content Management
Publish durable HTML artifacts, not runtime APIs. Built for developers who value performance, reliability, and long-term maintainability.
Publishes as files
Zero runtime dependency
Deterministic output
Key Characteristics
Designed for longevity, debuggability, and operational clarity.
File-Native Architecture
Published content lives as files in object storage. HTML, metadata, and sitemap are first-class artifacts.
Deterministic Output
Published pages are deterministic results of content + templates + build logic.
Zero Runtime Dependency
User-facing delivery requires no backend application, no rendering engine, and no runtime content APIs.
Clear System Separation
Admin is an application. User pages are documents. Clean boundaries, minimal attack surface.
Edge-Native Deployment
Static artifacts fit Pages, R2, Workers, GitHub, S3, and multiple delivery layers.
Architecture Overview
A clear separation between the admin application, published artifacts, and the delivery layer.
Content editing, publishing, operational workflows
R2, GitHub, S3
Cloudflare Workers, GitHub Pages, Cloudflare Pages, CloudFront
- JavaScript is for progressive enhancement, not core rendering
- Published artifacts can be served independently from the admin backend
- Connects to R2, GitHub, S3, and multiple delivery layers
Why ZeroPress?
An alternative to WordPress and API-centric Headless CMSs.
vs WordPress
- Content storage
- File-oriented output
- Rendering
- Publish-time static HTML
- Failure mode
- HTML remains available
- Mental model
- Documents, not applications
vs Headless CMS
- Content delivery
- Static HTML files
- Frontend
- Not required
- SEO
- Native
- Runtime dependency
- None
Vision
“Published content should outlive frameworks, APIs, and runtimes.”
ZeroPress optimizes for longevity, debuggability, operational clarity, and content survivability.
Recoverable by Design
If you can rebuild it, you don't need to restore it.
Single Source of Truth
D1 stores canonical content and publishing intent. Everything else is derived.
Deterministic Publishing
Published pages are deterministic outputs of content + templates + build logic.
Currently in Alpha
Ready to publish durable content?
Join early contributors who value clear architecture, explicit decisions, and minimal magic.