Release Readiness Center
Make publishing a separate decision.
Check a specific publication plan before putting that version online.
Make publishing a separate decision.
Immediately before an intended publication.
A locally working result may still have unresolved release concerns. Readiness checks collect findings before you approve an external publication.
Inspect the current project, delivery evidence and outstanding issues. Keep preparing a release separate from purchasing hosting or deploying it.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Prepare the publication plan and destination.
- 02
Run the available checks against that version and plan.
- 03
Review findings and authorise publication separately.
How it could work for you.
Review an approved site and discover a contact form still needs an email service.
How to assess the result
A ready label reflects the available checks, not a guarantee that every production requirement has been independently audited.
Where to find it.
Project help → Publish online → Check before publishing
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Evidence remains linked to the publication plan.
What you need to know
The check publishes nothing. The supported route targets static publication plans and does not automatically cover every backend or host.