🌐 [platform] Configure GitHub Pages with verified domain egohygiene.io

[szmyty]

Context

Set up GitHub Pages for the egohygiene organization and connect a verified custom domain (egohygiene.io) managed via SquareSpace DNS.

This will serve as the public-facing entrypoint for:

• Ego Hygiene platform
• documentation
• landing pages
• future tools and systems

---

Current State

• Domain: egohygiene.io (managed via SquareSpace)
• GitHub Pages domain verification initiated
• DNS TXT record required for verification

---

Goals

• Verify domain ownership with GitHub
• Configure GitHub Pages to use egohygiene.io
• Establish a foundation for:
  • documentation site
  • platform landing page
  • future static apps

---

Scope

Phase 1 — Domain Verification

• Add DNS TXT record:
  • Host: _github-pages-challenge-egohygiene.egohygiene.io
  • Value: <verification-token>
• Wait for DNS propagation
• Verify domain in GitHub

---

Phase 2 — Pages Setup

• Enable GitHub Pages for:
  • org-level site OR dedicated repo (e.g. egohygiene/site)
• Configure custom domain: egohygiene.io
• Enforce HTTPS

---

Phase 3 — DNS Configuration (SquareSpace)

• Add required A records (GitHub Pages IPs)
• Add CNAME for www → <username>.github.io
• Validate DNS resolution

---

Phase 4 — Content Foundation

• Create initial landing page:
  • overview of Ego Hygiene
  • links to core repos
  • system explanation
• Optional:
  • integrate static site generator (Astro, Next.js static export, etc.)

---

Acceptance Criteria

• Domain egohygiene.io is verified in GitHub
• GitHub Pages is accessible via custom domain
• HTTPS is enabled and enforced
• Landing page renders correctly
• DNS configuration is stable

---

Notes

This becomes:

🌐 Public interface for the Ego Hygiene ecosystem

Future expansions:

• documentation hub
• AI-generated content pipelines
• developer onboarding portal

[szmyty]

Captured organization-portfolio expansion

Outcome

Expand the existing Pages issue into a canonical map for egohygiene.io, product subdomains, documentation, architecture, landscape, and publication surfaces.

Acceptance criteria

• Record each hostname, source repository, deployment workflow, DNS owner, and certificate path
• Define launch, rollback, preview, and decommission procedures
• Reserve optiflow.egohygiene.io and landscape.egohygiene.io
• Validate that product sites can compose landing, docs, and architecture surfaces

Dependencies

WEB-01, REL-04, OPT-09

Source and decisions

• Portfolio ID: ORG-03
• Priority: P1
• Dependency wave: 1 - Control plane
• Source: architecture discussions; current .github issue inventory
• Assignee: szmyty

This scope expands the existing issue and intentionally avoids creating a duplicate.