Markdown Source
Use Build Pages to turn ordinary Markdown files and public assets into a static ZeroPress site.
Alpha Release
Static-First Document Publishing
With CMS-Grade Workflows
Build document sites from Markdown, structured preview data, or Studio-managed content. Publish durable HTML artifacts, not runtime APIs.
Markdown or Studio
Reusable themes
Static output
Key Characteristics
Designed for durable document publishing workflows that still deploy as static files.
Contract-First Builds
Use preview data and reusable themes directly, including data and themes produced by AI-assisted tooling.
Studio Publishing
Manage content, media, imports, and publish actions in Studio, then trigger a static ZeroPress build.
Static Output
User-facing pages are generated as final HTML at publish time. No server-side rendering is required to view the site.
Clear System Separation
Authoring, build, static hosting, and optional edge features stay in separate layers.
Edge When Needed
Comments, forms, and analytics can live beside the static site without turning every page into an application.
Architecture Overview
Three document authoring paths converge on the same static publishing model.
Choose the entry point that matches the project
Validate contracts, apply a theme, and generate artifacts
Serve HTML anywhere; add runtime features only when needed
- JavaScript is for progressive enhancement, not core rendering
- Published artifacts can be served independently from Studio
- Works with GitHub Pages, Vercel, Netlify, Cloudflare Pages, R2, and Workers
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.
Choose Your Publishing Path
Use the smallest workflow that fits the source of your content.
Markdown Repository
Use Build Pages when the source is Markdown files, public assets, and a static hosting target.
Structured Site Model
Use ZeroPress Build when preview data and a theme are generated, migrated, or maintained directly.
Managed Publishing
Use Studio when authors need an editor, media library, WXR import, and publish workflow.
Ready to publish durable content ?
Start with Markdown, build directly from preview data, or use Studio for managed publishing.