ZeroPress Studio Documentation

ZeroPress Studio manages content, media, and site settings in your browser. It runs on Cloudflare Workers and publishes site data to a separate static-site build. These documents explain how Studio stores data, controls access, and handles publishing and recovery.

Start Using Studio

• Quick Start: deploy Studio, create the first administrator, and connect a public site.
• WordPress Migration: import content and move existing media to R2.
• Publishing: prepare Preview Data, download it, or commit it to a GitHub repository.

Find a Topic

Topic	Documentation
Editing, autosaves, revisions, and body preview	Content
Media storage, references, and public delivery	Media
FTS5 indexing, search behavior, and rebuilding	Content Search
GitHub commits, unchanged data, and conflicts	GitHub Publishing
Passwords, mandatory MFA, and sign-in limits	Authentication
Passkey names, hostname scope, and sign-in methods	Passkeys
Session limits, expiry, and revocation	Sessions
Roles and infrastructure access restrictions	Access Control
Recorded activity and data retention	Audit Log
Edge, mail, Analytics, and AI	Service Integrations
Database upgrades, backups, and recovery	Operations

How the Components Fit Together

Component	Responsibility
Studio	Stores and manages content, accounts, settings, and media metadata; generates Preview Data
GitHub publishing	Optionally commits Preview Data to the public site’s repository
ZeroPress Build and a theme	Turn Preview Data into the public site’s static files
Hosting provider	Builds and deploys the public site from its connected repository
ZeroPress Edge	Optionally serves public comments, forms, and newsletters

Saving a published Post in Studio updates Studio’s database. Preparing data and publishing it updates the build input. The public site changes after its build and deployment finish.

For themes, CLI tools, and the Preview Data specification, use ZeroPress Documentation. For repository setup and local development commands, use the Studio README.