On this page
Publishing

What happens when you publish

The publish pipeline end to end: readiness checks, the commit plan, the GitHub commit, the deployment trigger and the build status your host reports to GitHub.

OverviewFor EveryoneUpdated November 12, 2026

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:

  1. Readiness checks (preflight) — Acrosite confirms the content and its files are ready, and surfaces any blocking issues to fix first.
  2. Commit plan — Acrosite prepares the exact files and repository paths it will write.
  3. GitHub commit — Acrosite commits the content (and any images it uses) to your repository and records the commit reference.
  4. 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

An authorized publisher can schedule or publish saved content directly from its editor. Review is optional on every plan. See Publish now and Schedule content.

Triggered, then reported by your host

This is the key thing to understand:

Important
Acrosite triggers your deployment after committing, and records the response. A trigger does not mean the build finished or that your site is live. Owners and Admins see the build status your host reports to GitHub for the commit; it says Deployed only when Acrosite recognizes your hosting provider's own status. See Build status.

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.

Next steps

Frequently asked questions

Not exactly. Published means Acrosite committed your content and triggered your deployment. Whether the build finished shows in the build status your host reports to GitHub (Owners and Admins see it in the item's Published File panel); if nothing is reported, confirm the finished build in your hosting provider's dashboard.
The readiness checks flag blocking issues before anything is committed — for example, missing required fields, or an unsaved or changed publishing version, or an unavailable workflow state. Plan limits can also block publishing. Fix the blocking issues, then publish again.
No. Scheduled content stays in Acrosite until its time arrives. Nothing is committed to your repository early; at the scheduled time, the same pipeline runs automatically.