Browse documentation
Publish your website
Build a staging release, inspect it, and promote the version you want visitors to see.
Where to find it
- Editor menu
- Project settings
- Publishing
In this guide
A completed production release and a public URL that serves the version you checked.
Before you start: You need publishing permission. Finish pending edits, check page routes, and resolve any required review approvals.
Understand the release steps
Saving an editor change updates your working draft. Publish staging builds a release for verification. Promote latest staging makes a completed staging release the production version.
- 01
Draft
Edit the website
- 02
Staging
Build and inspect
- 03
Review
Approve if required
- 04
Production
Release to visitors
- 1Build staging. Create a release from the current draft.
- 2Promote the checked release. Make the latest completed staging version live.
Build and check staging
Open Editor → Project settings → Publishing. The page checks readiness while loading.
- 1
Resolve readiness blockers
Read Resolve before publishing if it appears. Address the named route, asset, accessibility, or other issue and check again.
You should see: The page shows Ready to publish and the staging action is available.
- 2
Publish staging
Choose Publish staging once. Follow Publish Queue, then inspect Recent Releases or History for the completed release.
- 3
Inspect the release
Open the available staging page links for the completed release. Check navigation, mobile layout, media, forms, metadata, and scroll behavior. Create a review from this release if required.
Promote to production
Promotion uses the completed staging release. Edits made after that release was built are not automatically included.
- 1
Confirm the staging candidate
Check that the latest completed staging release is the one you tested. Complete the required review decisions if the project has an approval gate.
- 2
Promote latest staging
Choose Promote latest staging. Follow the release status until the production operation completes.
- 3
Open the public website
Use Open live site. Check the homepage and at least one inner page, then test the primary visitor action.
You should see: Production identifies the completed release, and the public URL shows the version you approved.
Restore a previous live release
Use rollback when you need a previous completed release to serve visitors again. It changes the selected environment’s release; it does not rewrite your current editor draft.
- 1
Choose the environment
Open Rollback Production for the live website, or Rollback Staging for staging.
- 2
Select a target release
Choose an available previous release under Target release and select Roll back.
- 3
Verify the restored version
Check the environment’s current release and open the website. Confirm that the expected page content and critical links work.
Before you move on
- Production shows a completed release.
- The public URL loads the intended page.
- Navigation and the primary form or call to action work.
- The custom domain is verified if you are using one.
Screenshots use a local sample workspace.