ZeroPress Studio Guide

Audience: administrators, editors, and authors

ZeroPress Studio is the authoring and operations application for a static-first ZeroPress site. It manages content and media, imports WordPress exports, and produces Preview Data v0.7 for a separate ZeroPress Build. Studio does not run the static-site build or deploy the resulting site.

This guide explains the product as an operator or user experiences it. Contract, renderer, CLI, and theme-development material remains at zeropress.dev.

Start here

• Quick Start walks an operator from a deployed, uninstalled Worker through the first MFA-protected administrator sign-in.
• Site Modes explains initial, operational, maintenance, and recovery without treating them as content settings.
• Maintenance & Recovery documents the protected operations surface, database lifecycle, backups, recovery, and destructive actions.

Product boundaries

Component	Responsibility
ZeroPress Studio	Authors and manages site data, media metadata, settings, imports, and Preview Data
ZeroPress Build	Consumes Preview Data and a theme to produce a static site
ZeroPress Edge	Optionally provides comments, Forms, and Newsletter runtime services
Cloudflare	Hosts the Worker and managed D1, KV, R2, and Queue resources selected by the operator

Edge integration is optional at the Studio product level. A Cloudflare binding may exist while Studio keeps Edge Services disabled. A disabled Studio integration does not stop a separately deployed Edge Worker; public Edge APIs are controlled by that Worker’s hard feature gates.

Alpha documentation policy

The Studio 0.7 application and this guide are being dogfooded before a public release. Stable security and lifecycle rules are documented now. Screenshots and control-by-control walkthroughs are intentionally deferred where UI details may still change.

Never apply SQL artifacts or alter D1 from a guide unless a reviewed Studio lifecycle operation explicitly owns that action. ZeroPress does not use wrangler d1 migrations.