What happens when you publish
The publish pipeline end to end: readiness checks, the commit plan, the GitHub commit, and the deployment trigger — and what Acrosite does and does not track.
Publishing in Acrosite is more than saving a file. When you publish a content item, Acrosite runs a short pipeline: it checks readiness, plans the commit, writes to GitHub, and triggers your deployment. This page explains each stage and what Acrosite does — and does not — track.
Who this is for
Everyone who publishes content, and anyone who wants to understand what happens behind the Publish Now and Schedule Publish actions.
The publish pipeline
A publish runs through these stages:
- Readiness checks (preflight) — Acrosite confirms the content and its files are ready, and surfaces any blocking issues to fix first.
- Commit plan — Acrosite prepares the exact files and repository paths it will write.
- GitHub commit — Acrosite commits the content (and any images it uses) to your repository and records the commit reference.
- Deployment trigger — Acrosite sends your configured deployment trigger so your host rebuilds the site.
For scheduled or retried publishes, a background worker carries out these stages at the right time.
Where it starts
Approved content can be scheduled or published now from its editor. See Publish now and Schedule content.
Triggered, not tracked to completion
This is the key thing to understand:
Where it is recorded
Every stage is recorded so you can confirm what happened: the commit side in Publish Logs, and the deployment trigger in Deployment Logs. On success, the item's status becomes Published.