Projected from ADO Feature #5699 (Project 42). This issue is bot-managed — edits here are not reflected back to ADO and will be reverted.
Project 42 currently serves the landing page, learning experience, and Field Guide from one repository and one hostname. Separate public sites are required so each experience has a clear purpose, independent content ownership, and an independent release surface while retaining one product identity.
Why now: The owner approved Learn and Field Guide as separate public experiences at dedicated subdomains.
In scope:
- Keep project-42.dev as the landing site.
- Create public Learn and Field Guide repositories and GitHub Pages sites.
- Publish learn.project-42.dev and guide.project-42.dev through Cloudflare DNS.
- Split authored curriculum and Field Guide content while retaining shared platform contracts.
- Preserve legacy URLs, learner progress, branding, accessibility, and rollback.
- Align ADO, GitHub, PMO, release, and operational evidence.
Out of scope:
- OpenAI Sites hosting.
- Changing the private PMO boundary.
- Implementing the deferred virtual-instructor runtime.
- Publishing stale legacy content without re-verification.
Projected from ADO Feature #5699 (Project 42). This issue is bot-managed — edits here are not reflected back to ADO and will be reverted.
Project 42 currently serves the landing page, learning experience, and Field Guide from one repository and one hostname. Separate public sites are required so each experience has a clear purpose, independent content ownership, and an independent release surface while retaining one product identity.
Why now: The owner approved Learn and Field Guide as separate public experiences at dedicated subdomains.
In scope:
Out of scope: