# Staging changes

Sites use a two-step publishing workflow: **staging** (preview) and **production** (live).

![State Diagram](https://help.gocapable.com/images/att1077444648.svg)

### [#](#deploying-to-staging)Deploying to staging

Click **Deploy** to start a deployment. The system:

1. Fetches all pages from your assigned Confluence spaces
2. Converts each page to static HTML, processing macros and downloading attachments
3. Uploads the generated files to a staging environment

Once complete, you'll receive a **staging preview URL** (e.g., `<https://<subdomain>>--staging.capable-sites.com`). Use this to review the site before publishing.

![Capable Sites Configuration](https://help.gocapable.com/images/5ebe0d80-ded2-402c-b6b3-70bf72083a6e.webp)

### [#](#deployment-progress)Deployment progress

While a deployment is running, you can track its progress:

* Overall status: `queued → preparing → running → finalizing → success` (or `failed`)
* Per-space progress: how many pages have been processed in each space
* Total page count and processed page count

### [#](#promoting-to-production)Promoting to production

After reviewing the staging preview, click **Promote** to publish the staged version to production. Your site becomes live at `<https://<subdomain>>.capable-sites.com` (and on any custom domain you've configured).

### [#](#discarding-staging)Discarding staging

If you're not happy with the staging preview, click **Discard Staging** to remove the staged files without affecting the live production site.

### [#](#auto-deploy)Auto-deploy

Enable the **Auto-deploy** toggle to automatically redeploy your site whenever a page changes in one of the assigned Confluence spaces. This keeps your published site in sync with your Confluence content without manual deploys.

### [#](#recent-deployments)Recent deployments

The site dashboard shows a history of recent deployments, including:

* Deployment status (success, failed, in progress)
* Who triggered it
* Timestamp
* Number of pages processed