What you get
Publishing that doesn't require a maintenance window. The site is in exactly one state at any moment — the old version, or the new version. Never a mixed window.
Why that matters
- A typo correction goes live in seconds, atomically
- A bad release is undone by clicking "Roll back" — instant, no rebuild
- Same release can promote staging → prod without rebuilding
- Schedule a release for a future time; it activates at that wall-clock moment
Where it publishes
S3 + CloudFront by default. BYO bucket on Business and Enterprise. GitHub repo as a target if you want a self-hostable mirror. Custom domain wired in with one config change.
Smart rebuilds
If you change one paragraph in one article, the build re-publishes only the pages that depend on that change. A 1M-page site change-1-article rebuild is dozens of file uploads, not millions.