Full diff view
Publish with confidence
Every changed, added and deleted file, in one screen. Text changes are highlighted line by line while images are shown visually.
All features Review & Publish
Review every change before it ships.
The review screen shows a full diff of every pending change — text and images — so you know exactly what's going out. Hit Publish and it lands as one clean Git commit, with the message already written for you.
From edits to a clean commit, without the friction.
Changes accumulate as you edit. When you're ready, open the review screen to see everything at once, confirm what should ship, and Zero publishes it as one atomic commit.
Selective publishing
Choose what goes out
Not everything has to ship at once. Uncheck a file to hold it back as a draft and publish only the changes that are ready.
Commit messages
Automatic change summaries
Zero reads the diff and drafts the summary for you. Edit it if you like, or just hit Publish — your Git history reads like a changelog.
In the details
Publishing, the way developers already ship.
Zero borrows the parts of Git review that make code safe to ship — and hides the parts that make it intimidating.
- 01
One atomic commit
Everything you select ships together in a single commit — text, frontmatter and images. Your site never builds from a half-published state.
- 02
Attributed to the editor
Each commit carries the name of the person who published it, even if they have no GitHub account. Git history shows who changed what, and when.
- 03
Images, compared visually
Replaced or added media shows as before-and-after thumbnails, not a binary blob. You see the actual picture that is about to go live.
- 04
Drafts stay drafts
Unpublished changes are held in Zero until you ship them. Nothing touches the repo or triggers a build before you say so.
- 05
Any branch, any pipeline
Publish to main or to a review branch. Vercel, Netlify or GitHub Actions pick up the commit exactly as they do today.
- 06
Nothing to undo by hand
Because every publish is a normal commit, rolling back is a normal revert. Your developers already know how.
Publish with confidence, not crossed fingers.
Connect your repo and every publish becomes a deliberate, reviewable act — not a leap of faith.