Delivery pipelines and release controls
The portal and documentation site have separate Cloudflare deployment targets and separate GitHub Actions workflows. This guide identifies the release path for each and the controls required before a preview implementation is promoted into production use.
1. Portal Worker delivery
The CEDA preview workflow builds the Next.js application for the Cloudflare Worker using OpenNext and deploys it through Wrangler. The preview address is a Worker hostname, not the documentation Pages hostname.
The workflow summary should include the deployed commit SHA and the Operations preview route. A successful workflow is deployment evidence, but it does not prove that identity D1 bindings, private evidence storage or production permissions are provisioned.
2. Documentation build and Pages delivery
The CEDA User Guides workflow builds the documentation with Docusaurus and deploys the static build output to the ceda-user-guides Pages project. The technical diagrams in this section are Mermaid blocks rendered by the Docusaurus Mermaid theme.
A documentation deploy is independent of the portal Worker. When a documentation page describes a new portal behaviour, verify that the corresponding application implementation has already landed or label the page as a planned design.
3. Promotion readiness gates
The release gates are intentionally cumulative. A polished user interface or successful Worker deployment does not compensate for missing access enforcement, unimplemented private file storage or unresolved data-governance decisions.
4. Release verification checklist
Portal
- Confirm the Worker deployment points to the intended feature-branch commit.
- Open the applicant, Operations, Innovation Rules, evaluator, adjudication and administration routes.
- Check each workspace's sidebar links against real section IDs.
- Verify that demo storage warnings and prototype boundaries remain visible.
- Test API routes only in an environment with the required bindings provisioned.
- Confirm the preview hostname has not been confused with the static guide hostname.
Technical diagrams
- Verify the Mermaid theme is installed and enabled in Docusaurus.
- Confirm all Mermaid blocks build without syntax errors.
- Check that every diagram has a title and accompanying explanation.
- Review labels and status names against the current source implementation.
- Label production design foundations and missing adapters explicitly.
Documentation
- Check internal links and sidebars during the Docusaurus build.
- Confirm the Pages workflow deploys the current commit.
- Open the live page and inspect diagram readability on desktop and mobile.
- Update the relevant guide when code changes alter a workflow or data boundary.
Related workflow files
- .github/workflows/ceda-preview.yml
- .github/workflows/ceda-docs.yml
- apps/web/wrangler.ceda-preview.jsonc
- apps/ceda-docs/docusaurus.config.js
- apps/ceda-docs/sidebars.js