lightspeedwp · ashleyshaw · Jun 3, 2026 · Jun 3, 2026 · Jun 3, 2026 · Jun 3, 2026
@@ -2,7 +2,7 @@
 file_type: documentation
 title: "Issue Execution Plan - Awesome GitHub Site"
 description: "Ordered issue plan for the Awesome GitHub website, covering the phase 1 MVP and the phase 2 expansion."
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-06-03"
 last_updated: "2026-06-03"
 status: active
@@ -21,57 +21,58 @@ tags:
 
 ## 3-Bullet Summary
 
-- Value: gives the website a strict delivery sequence so the first release stays small and useful.
+- Value: gives the website a strict delivery sequence so the first release stays small, useful, and deployable on GitHub Pages.
 - Risks: phase 2 material leaking into phase 1, unclear page ownership, and copy drift away from the source briefs.
-- Next step: lock the phase 1 issue chain, then hold phase 2 as the expansion path after the MVP is stable.
+- Next step: lock the phase 1 Pages setup chain, then hold phase 2 as the expansion path after the MVP is stable.
 
 ## Delivery Order
 
 ### Phase 1
 
-1. Source audit and scope lock
-2. Phase 1 information architecture and page map
-3. Phase 1 copy normalisation from the briefing docs
-4. MVP site scaffold and page build
+1. GitHub Pages domain and DNS audit
+2. Hosting runbook and repository settings alignment
+3. Astro GitHub Actions publishing workflow
+4. MVP site scaffold, pages, and custom `404`
 5. Validation and launch readiness
 
 ### Phase 2
 
 1. Full information architecture and content model
-2. Layout and browsing system expansion
-3. Content migration and page population
-4. Search or discovery enhancements
-5. Visual polish, accessibility pass, and full launch validation
+2. Resource catalogue and category browsing
+3. Search, discovery, and navigation refinement
+4. Accessibility, content, and metadata expansion
+5. Visual polish and full launch validation
 
 ## Suggested Issue Structure
 
 ### Phase 1
 
-- Parent: `Awesome GitHub Site - Phase 1 MVP`
-- Child 1: `Source audit and scope lock`
-- Child 2: `Information architecture and page map`
-- Child 3: `Copy normalisation and content model`
-- Child 4: `MVP site scaffold and page build`
-- Child 5: `Validation and launch readiness`
+- Parent: `Awesome GitHub Site - Phase 1 MVP and GitHub Pages Launch` (`#756`)
+- Child 1: `Research GitHub Pages, custom subdomain, and HTTPS setup` (`#757`)
+- Child 2: `Document the GitHub Pages publishing and DNS runbook` (`#758`)
+- Child 3: `Configure Astro GitHub Pages publishing workflow` (`#759`)
+- Child 4: `Build phase 1 pages and custom 404` (`#760`)
+- Child 5: `Validate build, DNS, HTTPS, and routing` (`#761`)
 
 ### Phase 2
 
-- Parent: `Awesome GitHub Site - Phase 2 Full Website`
-- Child 1: `Full information architecture and content model`
-- Child 2: `Category browsing and layout system`
-- Child 3: `Content population and resource structure`
-- Child 4: `Discovery, search, and supporting guides`
-- Child 5: `Accessibility, polish, and launch validation`
+- Parent: `Awesome GitHub Site - Phase 2 Full Website` (`#762`)
+- Child 1: `Add resource catalogue and category browsing` (`#763`)
+- Child 2: `Improve discovery, navigation, and search` (`#764`)
+- Child 3: `Document the full content model and governance` (`#765`)
+- Child 4: `Accessibility and launch validation for the full site` (`#766`)
 
 ## OpenSpec Notes
 
-- Use the phase split above when preparing `/opsx:propose` inputs.
+- Use the phase split above when preparing `/opsx:propose` inputs or issue bodies.
 - Keep proposal files phase-specific so phase 1 can ship without waiting for phase 2 detail.
-- Treat the normalised briefs in `briefs/` as the source of truth for the first planning pass.
+- Treat the normalised briefs in `briefs/` as the source of truth for the first planning pass, then add Pages/DNS details in the issue bodies.
 
 ## Acceptance Criteria
 
 - Phase 1 is bounded to 1-3 pages and can be launched independently.
 - Phase 2 expands the MVP without replacing the phase 1 structure.
 - The source briefs are aligned to repo documentation standards.
 - The active-project tracker reflects the new workstream.
+- The issue chain records the GitHub Pages setup steps, including custom domain, HTTPS, and `404` handling.
+- The issue register captures the created GitHub issue URLs.
@@ -0,0 +1,34 @@
+---
+file_type: documentation
+title: "Issue Register - Awesome GitHub Site"
+description: "Canonical register for the GitHub issues that drive the Awesome GitHub site launch and expansion."
+version: "1.0.1"
+created_date: "2026-06-03"
+last_updated: "2026-06-03"
+status: active
+stability: stable
+domain: website
+owners:
+  - Ash Shaw
+tags:
+  - issues
+  - website
+  - github-pages
+  - opsx
+---
+
+# Issue Register
+
+| Key | Template | GitHub Issue URL | Status | Evidence |
+| --- | --- | --- | --- | --- |
+| PHASE1-EPIC | `05-epic.md` | `https://github.com/lightspeedwp/.github/issues/756` | open | GitHub Pages launch and MVP scope |
+| PHASE1-RESEARCH | `21-research.md` | `https://github.com/lightspeedwp/.github/issues/757` | open | Domain, DNS, and HTTPS verification |
+| PHASE1-DOCS | `20-documentation.md` | `https://github.com/lightspeedwp/.github/issues/758` | open | Publishing source and runbook |
+| PHASE1-BUILD | `10-build-ci.md` | `https://github.com/lightspeedwp/.github/issues/759` | open | Astro publishing workflow |
+| PHASE1-TASK | `01-task.md` | `https://github.com/lightspeedwp/.github/issues/760` | open | Pages shell and custom `404` |
+| PHASE1-TEST | `12-testing-coverage.md` | `https://github.com/lightspeedwp/.github/issues/761` | open | Build, DNS, HTTPS, and routing validation |
+| PHASE2-EPIC | `05-epic.md` | `https://github.com/lightspeedwp/.github/issues/762` | open | Full website expansion |
+| PHASE2-FEATURE | `03-feature.md` | `https://github.com/lightspeedwp/.github/issues/763` | open | Resource catalogue and category browsing |
+| PHASE2-IMPROVEMENT | `07-improvement.md` | `https://github.com/lightspeedwp/.github/issues/764` | open | Discovery, navigation, and search refinement |
+| PHASE2-DOCS | `20-documentation.md` | `https://github.com/lightspeedwp/.github/issues/765` | open | Content model and governance |
+| PHASE2-A11Y | `14-a11y.md` | `https://github.com/lightspeedwp/.github/issues/766` | open | Accessibility and launch validation |
@@ -2,7 +2,7 @@
 file_type: documentation
 title: "Awesome GitHub Site"
 description: "Active project plan for the Awesome GitHub website, split into a launchable phase 1 MVP and a fuller phase 2 site."
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-06-03"
 last_updated: "2026-06-03"
 status: active
@@ -22,9 +22,9 @@ tags:
 
 ## 3-Bullet Summary
 
-- Value: turns the reference material into a small, shippable GitHub site first, then expands it into the fuller catalogue-style experience.
+- Value: turns the reference material into a small, shippable GitHub Pages site first, then expands it into the fuller catalogue-style experience.
 - Risks: phase creep, copy that stays too talk-specific, and a phase 2 structure that gets pulled into phase 1 too early.
-- Next step: run the phase 1 issue chain first, using the normalised briefs in `briefs/` as the source of truth.
+- Next step: run the phase 1 issue chain first, using the normalised briefs in `briefs/` and the Pages/DNS plan below as the source of truth.
 
 ## Overview
 
@@ -49,6 +49,16 @@ The delivery is intentionally split:
 - Phase 2 expansion planning and issue sequence
 - Normalised source briefs aligned to repo conventions
 - Execution tracker updates in `next-issues-execution-plan.md`
+- GitHub Pages hosting plan with DNS and HTTPS steps
+
+## Hosting Model
+
+- Canonical public URL: `github.lightspeedwp.agency`
+- GitHub Pages target domain underneath: `lightspeedwp.github.io`
+- Publishing source: GitHub Actions
+- Site generator: Astro
+- Required Pages features: custom domain, HTTPS, and a branded `404` page
+- Not in scope: Jekyll, submodules, or branch-based Pages publishing
 
 ## Phase Split
 
@@ -59,6 +69,9 @@ Build the smallest useful version of the site:
 - Home
 - Why this exists
 - References or Sources
+- GitHub Pages setup and DNS verification
+- HTTPS enablement after certificate issuance
+- Custom `404` page for missing routes
 
 ### Phase 2
 
@@ -68,12 +81,14 @@ Expand the site into the full experience:
 - category browsing
 - richer navigation
 - supporting guides and discovery flows
+- accessibility and launch polish for the full site
 
 ## References
 
 - [Phase 1 plan](phase-1/README.md)
 - [Phase 2 plan](phase-2/README.md)
 - [Issue execution plan](ISSUE_EXECUTION_PLAN.md)
+- [Issue register](ISSUE_REGISTER.md)
 - [Run log](RUN_LOG.md)
 - [OpenSpec guide](openspec/README.md)
 - [Mini site brief](briefs/mini-site-plan.md)

@@ -2,7 +2,7 @@
 file_type: documentation
 title: "Run Log - Awesome GitHub Site"
 description: "Execution log for planning and proposal runs related to the Awesome GitHub website."
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-06-03"
 last_updated: "2026-06-03"
 status: active
@@ -43,3 +43,12 @@ For each `/opsx:propose` run or planning pass, append a short entry using the pa
 - github-issue-url: `n/a`
 - labels-applied: `[]`
 - notes: `Project plan initialised. Phase 1 and phase 2 paths are now separated and ready for issue drafting.`
+
+### 2026-06-03 00:00 Europe/Warsaw - github-pages-issues-created
+
+- command: `gh issue create` x11
+- expected-template: `05-epic.md`, `21-research.md`, `20-documentation.md`, `10-build-ci.md`, `01-task.md`, `12-testing-coverage.md`, `05-epic.md`, `03-feature.md`, `07-improvement.md`, `20-documentation.md`, `14-a11y.md`
+- result: `success`
+- github-issue-url: `https://github.com/lightspeedwp/.github/issues/756` through `https://github.com/lightspeedwp/.github/issues/766`
+- labels-applied: `[]`
+- notes: `Created the phase 1 and phase 2 parent/child issue chain for Awesome GitHub, covering GitHub Pages setup, Astro publishing, custom domain DNS, 404 handling, and launch validation.`
@@ -2,7 +2,7 @@
 file_type: documentation
 title: "OpenSpec Proposal Guide - Awesome GitHub Site"
 description: "Guide for turning the Awesome GitHub phase plans into `/opsx:propose` inputs."
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-06-03"
 last_updated: "2026-06-03"
 status: active
@@ -25,34 +25,43 @@ This folder exists to support the issue proposal workflow for the Awesome GitHub
 
 Use it after the planning docs are approved and the phase split is locked.
 
+The issue chain should capture the GitHub Pages setup steps explicitly:
+
+1. Confirm custom subdomain and DNS target.
+2. Document repository settings and publishing source.
+3. Configure Astro publishing through GitHub Actions.
+4. Add the custom `404` page.
+5. Validate DNS, HTTPS, and routing.
+
 ## Expected Order
 
 ### Phase 1
 
-1. Source audit and scope lock
-2. Phase 1 information architecture and page map
-3. Phase 1 copy normalisation
-4. MVP site scaffold and page build
+1. GitHub Pages domain and DNS audit
+2. Hosting runbook and repository settings alignment
+3. Astro GitHub Actions publishing workflow
+4. MVP site scaffold, pages, and custom `404`
 5. Validation and launch readiness
 
 ### Phase 2
 
 1. Full information architecture and content model
-2. Layout and browsing system expansion
-3. Content migration and page population
-4. Search or discovery enhancements
-5. Visual polish, accessibility pass, and full launch validation
+2. Resource catalogue and category browsing
+3. Search, discovery, and navigation refinement
+4. Accessibility, content, and metadata expansion
+5. Visual polish and full launch validation
 
 ## Inputs
 
 - `../phase-1/README.md`
 - `../phase-2/README.md`
 - `../ISSUE_EXECUTION_PLAN.md`
+- `../ISSUE_REGISTER.md`
 - `../briefs/mini-site-plan.md`
 - `../briefs/page-copy-starter.md`
 
 ## Notes
 
 - Keep phase 1 and phase 2 proposal files separate.
-- Use the normalised briefs as the initial source for `/opsx:propose`.
+- Use the normalised briefs as the initial source for `/opsx:propose` or GitHub issue bodies.
 - Update `./RUN_LOG.md` after each proposal run.
@@ -2,7 +2,7 @@
 file_type: documentation
 title: "Awesome GitHub Site - Phase 1"
 description: "Phase 1 plan for the initial launchable version of the Awesome GitHub website."
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-06-03"
 last_updated: "2026-06-03"
 status: active
@@ -21,9 +21,9 @@ tags:
 
 ## 3-Bullet Summary
 
-- Value: ships a small but real site quickly so the project has a usable first outcome.
+- Value: ships a small but real site quickly so the project has a usable first outcome on GitHub Pages.
 - Risks: overbuilding the information architecture, adding catalogue behaviour too early, and letting the page count expand beyond the MVP.
-- Next step: define the 1-3 page shape and lock the copy before implementation starts.
+- Next step: define the 1-3 page shape, the Pages publishing path, and the custom domain before implementation starts.
 
 ## Scope
 
@@ -32,17 +32,24 @@ Phase 1 is intentionally narrow:
 - Home
 - Why this exists
 - References or Sources
+- GitHub Pages publishing setup
+- DNS and HTTPS verification
+- Custom `404` page
 
 ## Deliverables
 
 - A compact site shell with top navigation and footer
 - Clean, source-backed page copy
 - Basic visual treatment that can be extended later
 - A small validation checklist covering build and content consistency
+- GitHub Actions publishing workflow for Astro
+- Custom subdomain configuration for `github.lightspeedwp.agency`
 
 ## Acceptance Criteria
 
 - The site can be built and served without phase 2 features.
 - The core pages are complete and readable.
 - The copy is aligned to the normalised briefing docs.
 - The page structure is simple enough to extend in phase 2 without a rewrite.
+- GitHub Pages is configured with a custom domain and HTTPS.
+- A `404` page exists and is routed correctly on the published site.
@@ -2,7 +2,7 @@
 file_type: documentation
 title: "Awesome GitHub Site - Phase 2"
 description: "Phase 2 plan for expanding the Awesome GitHub website into the full resource-style site."
-version: "1.0.0"
+version: "1.0.1"
 created_date: "2026-06-03"
 last_updated: "2026-06-03"
 status: active
@@ -23,7 +23,7 @@ tags:
 
 - Value: expands the MVP into the fuller resource-style site inspired by the reference structure.
 - Risks: bolting on category pages without a clean content model, search or discovery added too early, and inconsistent metadata across pages.
-- Next step: keep phase 2 dependent on the phase 1 foundation rather than designing it in isolation.
+- Next step: keep phase 2 dependent on the phase 1 foundation and the live Pages deployment rather than designing it in isolation.
 
 ## Scope
 
@@ -34,6 +34,7 @@ Phase 2 adds the richer site structure:
 - supporting guides and discovery flows
 - stronger metadata and content organisation
 - fuller references and acknowledgements
+- expanded accessibility and performance polish
 
 ## Deliverables
 
@@ -42,10 +43,12 @@ Phase 2 adds the richer site structure:
 - Search or browse-first discovery support
 - More comprehensive content and source coverage
 - Accessibility and visual polish for launch readiness
+- Reuse the same GitHub Pages custom domain and Astro build pipeline from phase 1
 
 ## Acceptance Criteria
 
 - The phase 2 structure builds on the phase 1 MVP without replacing it.
 - Resource pages follow a consistent content model.
 - Navigation supports browsing by category and intent.
 - The site feels complete enough to stand beside the reference model without copying it directly.
+- Phase 2 ships on the same GitHub Pages host and HTTPS configuration already established in phase 1.
@@ -2,7 +2,7 @@
 title: Next Issues Execution Plan
 description: Comprehensive execution plan for all open issues, active projects, and
   strategic workflows.
-version: v2.2.4
+version: v2.2.5
 created_date: '2026-05-28'
 last_updated: '2026-06-03'
 file_type: documentation
@@ -29,7 +29,9 @@ status: active
 - Delivery is split into two phases:
   - Phase 1: 1-3 page launchable MVP
   - Phase 2: full resource-style site expansion
+- GitHub Pages target: custom subdomain `github.lightspeedwp.agency` with `lightspeedwp.github.io` as the Pages CNAME target.
 - Source briefs were normalised into the project folder so the phase split can be planned without leaking talk-specific copy into the site plan.
+- Created GitHub issues `#756` through `#766` for the phase 1 and phase 2 chains; next step is to keep the project register and launch docs aligned as implementation progresses.
 
 ## 2026-06-01 v0.5.0 Readiness Execution Update (Block 1)