Skip to main content

Online Publication

Deployment​

After the governed merge, the docs-*.yml GitHub Actions workflow:

  1. Checked out main.
  2. Installed Node.js dependencies.
  3. Ran npm run build.
  4. Uploaded the build/ directory as a Pages artifact.
  5. Deployed to GitHub Pages.

The deployment health check (scripts/check-docs-build.ps1) verified:

  • HTTP status 200 for https://bee1xgroup.github.io/ASF50/.
  • Homepage renders the ASF50 title.
  • Sidebar navigation works.
  • All internal links resolve.

The orchestrator wrote evidence/ASF50_DOCS_PORTAL_001/deployment_health.txt.

What this means​

The documentation portal is now live at:

https://bee1xgroup.github.io/ASF50/

(URL subject to GitHub Pages configuration; the canonical URL is recorded in the deployment health evidence.)

Owner gating for Pages​

If GitHub Pages was not previously enabled, the owner must enable it once via the GitHub repository settings. This is the one unavoidable owner action for this goal. After enabling, subsequent deployments are automatic.

See Playbooks → Promote a release to production for the canonical production-promotion flow.