Publication Flow
- Push changes to
docs/onmain. - Workflow
.github/workflows/pages.ymluploads docs artifact. - GitHub deploys the artifact to Pages URL.
- Root-level redirect pages preserve compatibility when Pages serves root paths rather than only
docs/deep links.
Audience Page Map
- Recruiter page: business impact, role fit, and hiring summary.
- Hiring manager page: delivery quality, architecture choices, maintainability, and execution signal.
- IT / engineering page: runtime architecture, security, testing, and CI/CD details.
- Case study and share kit: narrative and reusable wording for outreach and interviews.
Architecture Design Coverage
Review Pack Coverage
Publication Boundary
Client Design
Each audience page shows the client-side experience and state structure visually.
API Design
The review pack consistently surfaces the layered API design and business flow.
Data Design
Repository-backed persistence is visible across the site, not hidden in one technical page.
Shared architecture story across recruiter, manager, IT, and case-study paths
The architecture board is repeated across the review pack so the system design remains visible in every audience flow.
- Every public page now includes architecture design context so reviewers do not need to switch pages to understand the system structure.
- The shared architecture story is a layered design: client, API, and data model, with testing and operations treated as part of the design.
Troubleshooting
- Check Settings -> Pages -> Source is GitHub Actions.
- Check Actions logs for the Pages workflow run.
- Verify docs files exist and commit reached main branch.
- If a deep link returns 404, verify the matching root redirect page exists and points to the intended docs page.
- Retest after short CDN propagation when Pages deploys successfully but content has not refreshed yet.