Point Zero at your GitHub repo, and it reads your content collections, Astro components, understands your schemas, and gives your team a visual editor for everything.
Zero reads your existing Astro content collections and components directly from GitHub. No sync, no migration, no vendor-specific config files.
No code changes
Zero reads your existing content collections and infers the schema from your Zod definitions. Codebase stays clean, because you don't add anything to your repo — not a config file, not a package, not an API key.
Git is the source of truth
Every change an editor makes is committed directly to your repo, whether it's Markdown, MDX, or images. All content remains in Git, just like your code.
Schema-aware
Zero reads your Zod schema and builds a structured editor that matches exactly — required fields, enums, references to other collections, all of it. No manual configuration.
After connecting your repo, Zero immediately understands your site structure. No onboarding wizard. No data import. It just works.
01
Zero scans your content configuration and surfaces every collection as a browsable list. Add a new collection in code, and it shows up automatically.
02
Each content type gets a form built from its schema — text fields, dates, image pickers, reference selectors. Editors never touch raw Markdown.
03
Editors work on any branch, not just main. Review content changes in isolation before they merge, the same way your team handles code.
04
Your content is still Markdown files in your own GitHub repo. Walk away from Zero any time and nothing changes — your files are exactly where you left them.
Connect your GitHub repo and your team can start editing content right away. No code changes, no plugins, no setup calls.