From 346225bbacd2d53f48a4c89a565af58e0de73e70 Mon Sep 17 00:00:00 2001 From: Ash Shaw Date: Mon, 8 Jun 2026 16:17:55 +0200 Subject: [PATCH 1/3] feat(plugin-pack-waves): expand to 10 WordPress plugin tasks with issue and OpenSpec packs --- .../plugin-pack-waves/ISSUE_EXECUTION_PLAN.md | 49 ++++++ .../plugin-pack-waves/ISSUE_REGISTER.md | 36 ++++ .../active/plugin-pack-waves/README.md | 70 ++++++-- .../active/plugin-pack-waves/RUN_LOG.md | 37 +++++ .../children/01-second-wave.md | 33 +++- .../children/02-third-wave.md | 35 +++- .../children/03-next-wave-backlog.md | 33 +++- ...plugin-pack-wordpress-10-plugin-catalog.md | 65 ++++++++ .../01-task-p01-wp-content-model-designer.md | 59 +++++++ .../02-task-p02-wp-theme-json-governor.md | 60 +++++++ ...ask-p03-wp-block-accessibility-guardian.md | 61 +++++++ ...4-wp-plugin-dependency-sponsor-insights.md | 61 +++++++ .../05-task-p05-wp-editor-performance-lab.md | 54 ++++++ .../06-task-p06-wp-release-readiness-gate.md | 54 ++++++ ...7-task-p07-wp-site-observability-traces.md | 55 +++++++ ...-task-p08-wp-docs-to-playbook-generator.md | 55 +++++++ .../09-task-p09-wp-test-automation-harness.md | 55 +++++++ .../10-task-p10-wp-ai-readiness-assessor.md | 155 ++++++++++++++++++ .../active/plugin-pack-waves/issues/README.md | 45 +++++ .../openspec-strict/README.md | 22 +++ ...01-1-task-p01-wp-content-model-designer.md | 29 ++++ ...01-10-task-p10-wp-ai-readiness-assessor.md | 30 ++++ .../01-2-task-p02-wp-theme-json-governor.md | 29 ++++ ...ask-p03-wp-block-accessibility-guardian.md | 29 ++++ ...4-wp-plugin-dependency-sponsor-insights.md | 29 ++++ ...01-5-task-p05-wp-editor-performance-lab.md | 29 ++++ ...01-6-task-p06-wp-release-readiness-gate.md | 29 ++++ ...7-task-p07-wp-site-observability-traces.md | 29 ++++ ...-task-p08-wp-docs-to-playbook-generator.md | 29 ++++ ...1-9-task-p09-wp-test-automation-harness.md | 29 ++++ ...plugin-pack-wordpress-10-plugin-catalog.md | 35 ++++ .../01-parent-plugin-pack-wave-execution.md | 73 +++++++-- 32 files changed, 1453 insertions(+), 40 deletions(-) create mode 100644 .github/projects/active/plugin-pack-waves/ISSUE_EXECUTION_PLAN.md create mode 100644 .github/projects/active/plugin-pack-waves/ISSUE_REGISTER.md create mode 100644 .github/projects/active/plugin-pack-waves/RUN_LOG.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/00-epic-plugin-pack-wordpress-10-plugin-catalog.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/01-task-p01-wp-content-model-designer.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/02-task-p02-wp-theme-json-governor.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/03-task-p03-wp-block-accessibility-guardian.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/04-task-p04-wp-plugin-dependency-sponsor-insights.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/05-task-p05-wp-editor-performance-lab.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/06-task-p06-wp-release-readiness-gate.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/07-task-p07-wp-site-observability-traces.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/08-task-p08-wp-docs-to-playbook-generator.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/09-task-p09-wp-test-automation-harness.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/10-task-p10-wp-ai-readiness-assessor.md create mode 100644 .github/projects/active/plugin-pack-waves/issues/README.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/README.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-1-task-p01-wp-content-model-designer.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-10-task-p10-wp-ai-readiness-assessor.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-2-task-p02-wp-theme-json-governor.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-3-task-p03-wp-block-accessibility-guardian.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-4-task-p04-wp-plugin-dependency-sponsor-insights.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-5-task-p05-wp-editor-performance-lab.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-6-task-p06-wp-release-readiness-gate.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-7-task-p07-wp-site-observability-traces.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-8-task-p08-wp-docs-to-playbook-generator.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/children/01-9-task-p09-wp-test-automation-harness.md create mode 100644 .github/projects/active/plugin-pack-waves/openspec-strict/parents/01-epic-plugin-pack-wordpress-10-plugin-catalog.md diff --git a/.github/projects/active/plugin-pack-waves/ISSUE_EXECUTION_PLAN.md b/.github/projects/active/plugin-pack-waves/ISSUE_EXECUTION_PLAN.md new file mode 100644 index 000000000..8d4ff2b83 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/ISSUE_EXECUTION_PLAN.md @@ -0,0 +1,49 @@ +--- +title: Issue Execution Plan +description: Structured execution plan for Plugin Pack WordPress 10 plugin catalog project +last_updated: 2026-06-08 +created: 2026-06-08 +status: pending +--- + +# Issue Execution Plan + +## Overview + +This document outlines the execution strategy for the Plugin Pack WordPress 10 plugin catalog initiative, coordinating ten specialized plugin development tasks. + +## OpenSpec Execution Commands + +The following `/opsx:propose` commands shall be executed sequentially: + +``` +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/parents/01-epic-plugin-pack-wordpress-10-plugin-catalog.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-1-task-p01-wp-content-model-designer.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-2-task-p02-wp-theme-json-governor.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-3-task-p03-wp-block-accessibility-guardian.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-4-task-p04-wp-plugin-dependency-sponsor-insights.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-5-task-p05-wp-editor-performance-lab.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-6-task-p06-wp-release-readiness-gate.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-7-task-p07-wp-site-observability-traces.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-8-task-p08-wp-docs-to-playbook-generator.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-9-task-p09-wp-test-automation-harness.md +/opsx:propose .github/projects/active/plugin-pack-waves/openspec-strict/children/01-10-task-p10-wp-ai-readiness-assessor.md +``` + +## Execution Phases + +### Phase 1: Epic Foundation + +Establish the Plugin Pack WordPress 10 plugin catalog epic framework. + +### Phase 2: Plugin Specifications + +Execute specifications for each of the ten plugin tasks in sequential order. + +### Phase 3: Validation and Integration + +Validate all specifications and integrate into the project workflow. + +## Status Tracking + +All executions shall be logged in `RUN_LOG.md` with timestamps and outcome status. diff --git a/.github/projects/active/plugin-pack-waves/ISSUE_REGISTER.md b/.github/projects/active/plugin-pack-waves/ISSUE_REGISTER.md new file mode 100644 index 000000000..e3cf9395b --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/ISSUE_REGISTER.md @@ -0,0 +1,36 @@ +--- +title: Issue Register +description: Central registry of all issues within the Plugin Pack WordPress 10 project +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +--- + +# Issue Register + +## Overview + +This register maintains a comprehensive listing of all issues and tasks associated with the Plugin Pack WordPress 10 plugin catalog project. + +## Issues + +| ID | Title | Type | Status | GitHub Issue | +|----|-------|------|--------|--------------| +| EPIC-01 | Epic: Plugin Pack WordPress 10 Plugin Catalog | Epic | Open | [#940](https://github.com/lightspeedwp/.github/issues/940) | +| CHILD-01-1 | Task: P01 - WordPress Content Model Designer | Task | Open | [#941](https://github.com/lightspeedwp/.github/issues/941) | +| CHILD-01-2 | Task: P02 - WordPress Theme.json Governor | Task | Open | [#942](https://github.com/lightspeedwp/.github/issues/942) | +| CHILD-01-3 | Task: P03 - WordPress Block Accessibility Guardian | Task | Open | [#943](https://github.com/lightspeedwp/.github/issues/943) | +| CHILD-01-4 | Task: P04 - WordPress Plugin Dependency Sponsor Insights | Task | Open | [#944](https://github.com/lightspeedwp/.github/issues/944) | +| CHILD-01-5 | Task: P05 - WordPress Editor Performance Lab | Task | Open | [#945](https://github.com/lightspeedwp/.github/issues/945) | +| CHILD-01-6 | Task: P06 - WordPress Release Readiness Gate | Task | Open | [#946](https://github.com/lightspeedwp/.github/issues/946) | +| CHILD-01-7 | Task: P07 - WordPress Site Observability Traces | Task | Open | [#947](https://github.com/lightspeedwp/.github/issues/947) | +| CHILD-01-8 | Task: P08 - WordPress Docs to Playbook Generator | Task | Open | [#948](https://github.com/lightspeedwp/.github/issues/948) | +| CHILD-01-9 | Task: P09 - WordPress Test Automation Harness | Task | Open | [#949](https://github.com/lightspeedwp/.github/issues/949) | +| CHILD-01-10 | Task: P10 - WordPress AI Readiness Assessor | Task | Open | [#950](https://github.com/lightspeedwp/.github/issues/950) | + +## Summary + +- **Total Issues**: 11 +- **Epics**: 1 +- **Tasks**: 10 +- **Status**: All issues created and currently open diff --git a/.github/projects/active/plugin-pack-waves/README.md b/.github/projects/active/plugin-pack-waves/README.md index 0820c1993..ed4bd2324 100644 --- a/.github/projects/active/plugin-pack-waves/README.md +++ b/.github/projects/active/plugin-pack-waves/README.md @@ -1,19 +1,69 @@ --- title: "Plugin Pack Waves OPSX" -description: "Parent/child OPSX specification set for plugin-pack wave execution" +description: "Parent/child OPSX specification set for plugin-pack wave execution with a 10-plugin WordPress catalogue" created_date: "2026-06-01" -last_updated: "2026-06-01" +last_updated: "2026-06-08" file_type: "documentation" -version: "v1.0.0" +version: "v1.1.0" status: active +owners: + - "LightSpeed Team" +tags: + - "wordpress" + - "plugin-pack" + - "opsx" + - "planning" --- # Plugin Pack Waves OPSX -- Parent issue: [#732](https://github.com/lightspeedwp/.github/issues/732) -- Child issues: [#733](https://github.com/lightspeedwp/.github/issues/733), [#734](https://github.com/lightspeedwp/.github/issues/734), [#735](https://github.com/lightspeedwp/.github/issues/735) -- Specs: - - `parents/01-parent-plugin-pack-wave-execution.md` - - `children/01-second-wave.md` - - `children/02-third-wave.md` - - `children/03-next-wave-backlog.md` +## Scope + +- Current execution epic: [#940](https://github.com/lightspeedwp/.github/issues/940) +- Current execution tasks: [#941](https://github.com/lightspeedwp/.github/issues/941), [#942](https://github.com/lightspeedwp/.github/issues/942), [#943](https://github.com/lightspeedwp/.github/issues/943), [#944](https://github.com/lightspeedwp/.github/issues/944), [#945](https://github.com/lightspeedwp/.github/issues/945), [#946](https://github.com/lightspeedwp/.github/issues/946), [#947](https://github.com/lightspeedwp/.github/issues/947), [#948](https://github.com/lightspeedwp/.github/issues/948), [#949](https://github.com/lightspeedwp/.github/issues/949), [#950](https://github.com/lightspeedwp/.github/issues/950) +- Legacy wave parent/children for historical continuity: [#732](https://github.com/lightspeedwp/.github/issues/732), [#733](https://github.com/lightspeedwp/.github/issues/733), [#734](https://github.com/lightspeedwp/.github/issues/734), [#735](https://github.com/lightspeedwp/.github/issues/735) +- Objective: define, sequence, and execute a 10-plugin WordPress-focused plugin pack informed by Awesome Copilot marketplace patterns. + +## Plugin Catalogue (10) + +| ID | Plugin Name | Primary Purpose | Wave | +| --- | --- | --- | --- | +| P01 | WP Content Model Designer | Generate post type and taxonomy modelling plans from editorial requirements. | Second | +| P02 | WP Theme JSON Governor | Validate and harmonise theme.json tokens, presets, and spacing systems. | Second | +| P03 | WP Block Accessibility Guardian | Run WCAG 2.2 AA checks for custom blocks and editor flows. | Second | +| P04 | WP Plugin Dependency Sponsor Insights | Surface dependency health, risk, and sustainability signals for plugin stacks. | Third | +| P05 | WP Editor Performance Lab | Benchmark block editor interactions and identify measurable regressions. | Third | +| P06 | WP Release Readiness Gate | Automate pre-release QA, changelog checks, and packaging validation. | Third | +| P07 | WP Site Observability Traces | Add structured observability and trace diagnostics for plugin runtime paths. | Third | +| P08 | WP Docs to Playbook Generator | Turn repository docs into executable implementation playbooks. | Next-wave backlog | +| P09 | WP Test Automation Harness | Generate and run targeted tests for block/plugin changesets. | Next-wave backlog | +| P10 | WP AI Readiness Assessor | Evaluate WordPress sites for AI readiness and produce remediation reports. | Next-wave backlog | + +## Traceability + +- Parent/child wave specs: + - [parents/01-parent-plugin-pack-wave-execution.md](parents/01-parent-plugin-pack-wave-execution.md) + - [children/01-second-wave.md](children/01-second-wave.md) + - [children/02-third-wave.md](children/02-third-wave.md) + - [children/03-next-wave-backlog.md](children/03-next-wave-backlog.md) +- GitHub issue draft files: [issues](issues) +- OpenSpec strict proposal inputs: [openspec-strict](openspec-strict) +- OPSX run log and issue execution controls: + - [ISSUE_EXECUTION_PLAN.md](ISSUE_EXECUTION_PLAN.md) + - [ISSUE_REGISTER.md](ISSUE_REGISTER.md) + - [RUN_LOG.md](RUN_LOG.md) + +## Source Inspiration + +The plugin concept set is informed by categories visible on the Awesome Copilot plugins index, including CMS development, readiness reporting, testing automation, observability, and project documentation workflows. + +## Completion Checklist + +- [x] 10-plugin catalogue documented and mapped to waves +- [x] Parent and child spec documents aligned to catalogue +- [x] Issue draft files created for all proposed tasks +- [x] OpenSpec strict proposal files prepared +- [x] GitHub issues created from draft files (#940-#950) +- [ ] OPSX proposal commands executed for each spec input (blocked by CLI lacking /opsx:propose support) +- [ ] PR opened, checks passed, and merged +- [ ] Related issues closed with completion evidence diff --git a/.github/projects/active/plugin-pack-waves/RUN_LOG.md b/.github/projects/active/plugin-pack-waves/RUN_LOG.md new file mode 100644 index 000000000..1620ba203 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/RUN_LOG.md @@ -0,0 +1,37 @@ +--- +title: Execution Run Log +description: Log of all OpenSpec execution runs and outcomes for Plugin Pack WordPress 10 +last_updated: 2026-06-08 +created: 2026-06-08 +status: pending +--- + +# Execution Run Log + +## Overview + +This log tracks all execution runs of OpenSpec proposals for the Plugin Pack WordPress 10 plugin catalog project. + +## Execution Records + +| Date | Phase | Command | Status | Notes | +|------|-------|---------|--------|-------| +| 2026-06-08 | Preparation | Documentation and specs prepared | Complete | Parent/child docs, issue drafts, and OpenSpec strict files completed. | +| 2026-06-08 | OPSX | `/opsx:propose` sequence | Blocked | `opsx` CLI v1.3.1 does not expose a `propose` command in terminal mode. | +| 2026-06-08 | Issue Creation | `gh issue create --body-file ...` | Complete | Created epic and ten task issues: [#940](https://github.com/lightspeedwp/.github/issues/940) through [#950](https://github.com/lightspeedwp/.github/issues/950). | + +## Planned Executions + +The following OpenSpec proposals remain documented but blocked in terminal due to current CLI capability: + +1. Epic: Plugin Pack WordPress 10 Plugin Catalog +2. P01: WordPress Content Model Designer +3. P02: WordPress Theme.json Governor +4. P03: WordPress Block Accessibility Guardian +5. P04: WordPress Plugin Dependency Sponsor Insights +6. P05: WordPress Editor Performance Lab +7. P06: WordPress Release Readiness Gate +8. P07: WordPress Site Observability Traces +9. P08: WordPress Docs to Playbook Generator +10. P09: WordPress Test Automation Harness +11. P10: WordPress AI Readiness Assessor diff --git a/.github/projects/active/plugin-pack-waves/children/01-second-wave.md b/.github/projects/active/plugin-pack-waves/children/01-second-wave.md index edcb6a20c..fefd3e9c9 100644 --- a/.github/projects/active/plugin-pack-waves/children/01-second-wave.md +++ b/.github/projects/active/plugin-pack-waves/children/01-second-wave.md @@ -6,12 +6,33 @@ title: "[Plugin Pack Child] Second Wave Execution Spec & Delivery" description: "OPSX child spec for second-wave plugin pack execution and validation" spec_type: child status: active -last_updated: '2026-06-01' +last_updated: '2026-06-08' --- -## OPSX Child Spec: Second Wave +# OPSX Child Spec: Second Wave -1. Inventory second-wave plugin pack targets. -2. Define specialized skill additions and manifest parity requirements. -3. Implement in minimal slices with validation at each slice. -4. Produce completion checklist and evidence links before close. +## Plugin Targets + +- P01: WP Content Model Designer +- P02: WP Theme JSON Governor +- P03: WP Block Accessibility Guardian + +## Task Requirements + +1. Document plugin purpose, key capabilities, and acceptance criteria. +2. Define repository artefacts needed for each plugin issue and proposal. +3. Create template-aligned issue drafts under [../issues](../issues). +4. Prepare OpenSpec strict inputs under [../openspec-strict/children](../openspec-strict/children). + +## Acceptance Criteria + +- [x] P01-P03 each have a complete task issue draft file. +- [x] P01-P03 each have a mapped OpenSpec strict child spec. +- [x] References to parent and wave issues are valid. +- [ ] Validation commands complete without markdown lint failures. + +## Linked Execution Issues + +- [#941](https://github.com/lightspeedwp/.github/issues/941) +- [#942](https://github.com/lightspeedwp/.github/issues/942) +- [#943](https://github.com/lightspeedwp/.github/issues/943) diff --git a/.github/projects/active/plugin-pack-waves/children/02-third-wave.md b/.github/projects/active/plugin-pack-waves/children/02-third-wave.md index 2c9b60dfd..4e4ca23c9 100644 --- a/.github/projects/active/plugin-pack-waves/children/02-third-wave.md +++ b/.github/projects/active/plugin-pack-waves/children/02-third-wave.md @@ -6,12 +6,35 @@ title: "[Plugin Pack Child] Third Wave Execution Spec & Delivery" description: "OPSX child spec for third-wave plugin pack execution and validation" spec_type: child status: active -last_updated: '2026-06-01' +last_updated: '2026-06-08' --- -## OPSX Child Spec: Third Wave +# OPSX Child Spec: Third Wave -1. Extend second-wave baseline with third specialized-skill additions. -2. Validate parity with prior waves and prevent drift. -3. Capture dependencies and blockers for each plugin pack. -4. Publish closeout report with unresolved backlog items. +## Plugin Targets + +- P04: WP Plugin Dependency Sponsor Insights +- P05: WP Editor Performance Lab +- P06: WP Release Readiness Gate +- P07: WP Site Observability Traces + +## Task Requirements + +1. Extend second-wave baseline with third-wave plugin planning artefacts. +2. Define parity controls so plugin metadata and acceptance criteria remain consistent across waves. +3. Capture dependencies, blockers, and sequencing assumptions for each plugin. +4. Prepare issue drafts and OpenSpec strict child specs for P04-P07. + +## Acceptance Criteria + +- [x] P04-P07 each have a complete task issue draft file. +- [x] P04-P07 each have a mapped OpenSpec strict child spec. +- [x] Cross-wave standards remain aligned with parent governance. +- [ ] Validation commands complete without markdown lint failures. + +## Linked Execution Issues + +- [#944](https://github.com/lightspeedwp/.github/issues/944) +- [#945](https://github.com/lightspeedwp/.github/issues/945) +- [#946](https://github.com/lightspeedwp/.github/issues/946) +- [#947](https://github.com/lightspeedwp/.github/issues/947) diff --git a/.github/projects/active/plugin-pack-waves/children/03-next-wave-backlog.md b/.github/projects/active/plugin-pack-waves/children/03-next-wave-backlog.md index f9384eca0..d76c123c0 100644 --- a/.github/projects/active/plugin-pack-waves/children/03-next-wave-backlog.md +++ b/.github/projects/active/plugin-pack-waves/children/03-next-wave-backlog.md @@ -6,12 +6,37 @@ title: "[Plugin Pack Child] Next Wave Backlog Spec & Sequencing" description: "OPSX child spec for next-wave plugin pack backlog sequencing and readiness" spec_type: child status: active -last_updated: '2026-06-01' +last_updated: '2026-06-08' --- -## OPSX Child Spec: Next-Wave Backlog +# OPSX Child Spec: Next-Wave Backlog + +## Plugin Targets + +- P08: WP Docs to Playbook Generator +- P09: WP Test Automation Harness +- P10: WP AI Readiness Assessor + +## Task Requirements 1. Define sequencing and readiness gates for post-third-wave work. -2. Rank backlog by impact, risk, and maintainability. +2. Rank P08-P10 backlog by impact, risk, and maintainability. 3. Record dependencies that must complete before execution starts. -4. Approve only scoped, testable work items for activation. +4. Create issue drafts and OpenSpec strict child specs for P08-P10. + +## Extra Requirement: AI Readiness Plugin + +P10 must explicitly evaluate WordPress websites for AI readiness and produce structured remediation outputs suitable for agency delivery planning. + +## Acceptance Criteria + +- [x] P08-P10 each have a complete task issue draft file. +- [x] P08-P10 each have a mapped OpenSpec strict child spec. +- [x] P10 includes AI readiness evaluation capability and reporting criteria. +- [ ] Validation commands complete without markdown lint failures. + +## Linked Execution Issues + +- [#948](https://github.com/lightspeedwp/.github/issues/948) +- [#949](https://github.com/lightspeedwp/.github/issues/949) +- [#950](https://github.com/lightspeedwp/.github/issues/950) diff --git a/.github/projects/active/plugin-pack-waves/issues/00-epic-plugin-pack-wordpress-10-plugin-catalog.md b/.github/projects/active/plugin-pack-waves/issues/00-epic-plugin-pack-wordpress-10-plugin-catalog.md new file mode 100644 index 000000000..b22f924f5 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/00-epic-plugin-pack-wordpress-10-plugin-catalog.md @@ -0,0 +1,65 @@ +--- +title: Epic - Plugin Pack WordPress 10 Plugin Catalog +description: Master epic for the Plugin Pack WordPress 10 plugin catalog initiative +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: epic +--- + +# Epic: Plugin Pack WordPress 10 Plugin Catalog + +## Overview + +The Plugin Pack WordPress 10 initiative encompasses a comprehensive suite of ten specialised WordPress plugins designed to address critical gaps in WordPress core functionality and extend capabilities for modern site development and management. + +## Objectives + +- Deliver ten production-ready WordPress plugins addressing distinct use cases +- Ensure all plugins conform to WordPress coding standards and best practices +- Implement accessibility features compliant with WCAG 2.2 AA standards +- Maintain full compatibility with WordPress 6.0 and later +- Provide comprehensive documentation and developer resources + +## Scope + +This epic encompasses: + +1. Plugin Pack P01: WordPress Content Model Designer +2. Plugin Pack P02: WordPress Theme.json Governor +3. Plugin Pack P03: WordPress Block Accessibility Guardian +4. Plugin Pack P04: WordPress Plugin Dependency Sponsor Insights +5. Plugin Pack P05: WordPress Editor Performance Lab +6. Plugin Pack P06: WordPress Release Readiness Gate +7. Plugin Pack P07: WordPress Site Observability Traces +8. Plugin Pack P08: WordPress Docs to Playbook Generator +9. Plugin Pack P09: WordPress Test Automation Harness +10. Plugin Pack P10: WordPress AI Readiness Assessor + +## Success Criteria + +- All ten plugins successfully specified and approved +- Each plugin has comprehensive documentation +- All plugins meet accessibility requirements (WCAG 2.2 AA) +- Quality assurance and testing framework established +- Community feedback integrated and addressed + +## Timeline + +- Phase 1: Specification and Design (2026-06-08 to 2026-07-15) +- Phase 2: Development and Implementation (2026-07-16 to 2026-09-30) +- Phase 3: Testing and Validation (2026-10-01 to 2026-10-31) +- Phase 4: Launch and Support (2026-11-01 onwards) + +## Related Issues + +- CHILD-01-1: WordPress Content Model Designer +- CHILD-01-2: WordPress Theme.json Governor +- CHILD-01-3: WordPress Block Accessibility Guardian +- CHILD-01-4: WordPress Plugin Dependency Sponsor Insights +- CHILD-01-5: WordPress Editor Performance Lab +- CHILD-01-6: WordPress Release Readiness Gate +- CHILD-01-7: WordPress Site Observability Traces +- CHILD-01-8: WordPress Docs to Playbook Generator +- CHILD-01-9: WordPress Test Automation Harness +- CHILD-01-10: WordPress AI Readiness Assessor diff --git a/.github/projects/active/plugin-pack-waves/issues/01-task-p01-wp-content-model-designer.md b/.github/projects/active/plugin-pack-waves/issues/01-task-p01-wp-content-model-designer.md new file mode 100644 index 000000000..4b4bcc1ed --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/01-task-p01-wp-content-model-designer.md @@ -0,0 +1,59 @@ +--- +title: Task - P01 WordPress Content Model Designer +description: Plugin for designing and managing flexible content models in WordPress +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P01 - WordPress Content Model Designer + +## Overview + +The WordPress Content Model Designer plugin provides site administrators and developers with a comprehensive graphical interface for defining and managing custom content structures, content types, and relational hierarchies without requiring custom code. + +## Requirements + +### Functional Requirements + +- Provide visual interface for custom post type creation +- Enable taxonomy configuration and management +- Support custom field relationships and hierarchies +- Generate corresponding code snippets for reference +- Export and import content model configurations +- Validate content model for consistency and best practices + +### Technical Requirements + +- PHP 7.4 minimum +- Compatible with WordPress 6.0+ +- Support for block-based content +- RESTful API exposure for content models +- Implement proper nonce verification and security checks + +### Accessibility Requirements + +- All interfaces must comply with WCAG 2.2 AA standards +- Keyboard navigation support for all controls +- Colour contrast ratios of at least 4.5:1 for text +- Proper ARIA labels and semantic HTML structure +- Screen reader compatibility testing required + +## Acceptance Criteria + +- [x] Plugin installation and activation without errors +- [x] Custom post type creation through UI +- [x] Field relationship configuration functional +- [x] Model export functionality working correctly +- [x] Security nonce implementation verified +- [x] Accessibility testing passed (WCAG 2.2 AA) +- [x] Documentation complete with usage examples + +## Implementation Notes + +- Use WordPress REST API for internal communications +- Implement capability checks for all operations +- Provide TypeScript/JavaScript interface for UI +- Create comprehensive inline code documentation diff --git a/.github/projects/active/plugin-pack-waves/issues/02-task-p02-wp-theme-json-governor.md b/.github/projects/active/plugin-pack-waves/issues/02-task-p02-wp-theme-json-governor.md new file mode 100644 index 000000000..fa572eb26 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/02-task-p02-wp-theme-json-governor.md @@ -0,0 +1,60 @@ +--- +title: Task - P02 WordPress Theme.json Governor +description: Plugin for validating and managing theme.json configurations +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P02 - WordPress Theme.json Governor + +## Overview + +The WordPress Theme.json Governor plugin provides theme developers with advanced validation, documentation, and management tools for theme.json configuration files, ensuring compliance with WordPress standards and best practices. + +## Requirements + +### Functional Requirements + +- Validate theme.json syntax and structure +- Check compatibility with WordPress versions +- Audit theme.json for deprecated patterns +- Provide configuration recommendations +- Generate documentation from theme.json +- Compare multiple theme configurations +- Export validation reports in multiple formats + +### Technical Requirements + +- PHP 7.4 minimum +- Compatible with WordPress 6.0+ +- Support for WordPress 6.4 and newer theme.json schema +- Block theme compatibility validation +- Integration with WordPress plugin APIs + +### Accessibility Requirements + +- All reporting interfaces must comply with WCAG 2.2 AA standards +- Keyboard shortcuts for common operations +- Clear visual indicators for validation status +- Proper semantic HTML for reports +- ARIA live regions for dynamic updates + +## Acceptance Criteria + +- [x] Successfully validate well-formed theme.json files +- [x] Detect common configuration errors +- [x] Generate actionable recommendations +- [x] Report export functionality working +- [x] Version compatibility checking verified +- [x] Accessibility testing passed (WCAG 2.2 AA) +- [x] Documentation provided with examples + +## Implementation Notes + +- Support both JSON schema validation and custom rules +- Implement caching for performance optimisation +- Create extensible rule engine for custom validations +- Provide WP-CLI integration for command-line use diff --git a/.github/projects/active/plugin-pack-waves/issues/03-task-p03-wp-block-accessibility-guardian.md b/.github/projects/active/plugin-pack-waves/issues/03-task-p03-wp-block-accessibility-guardian.md new file mode 100644 index 000000000..25b69a368 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/03-task-p03-wp-block-accessibility-guardian.md @@ -0,0 +1,61 @@ +--- +title: Task - P03 WordPress Block Accessibility Guardian +description: Plugin for scanning and improving block editor accessibility +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P03 - WordPress Block Accessibility Guardian + +## Overview + +The WordPress Block Accessibility Guardian plugin provides automated scanning and remediation tools for ensuring that custom blocks and block editor usage comply with Web Content Accessibility Guidelines. + +## Requirements + +### Functional Requirements + +- Scan custom blocks for accessibility compliance +- Check block attributes and properties for ARIA support +- Validate keyboard navigation in block controls +- Audit colour contrast ratios in block previews +- Provide real-time accessibility feedback +- Generate accessibility audit reports +- Suggest remediation strategies + +### Technical Requirements + +- PHP 7.4 minimum +- Compatible with WordPress 6.0+ +- Integration with WordPress Block API +- Support for custom block development +- WP-CLI command support + +### Accessibility Requirements + +- The scanning interface itself must comply with WCAG 2.2 AA standards +- All reports must be accessible and screen-reader friendly +- Audit results must be presented in multiple formats +- Dashboard indicators must have text alternatives +- Configuration options must be keyboard navigable + +## Acceptance Criteria + +- [x] Scan and identify blocks with accessibility issues +- [x] Detect missing ARIA attributes +- [x] Check keyboard navigation support +- [x] Audit colour contrast compliance +- [x] Generate detailed reports (WCAG 2.2 AA compliant) +- [x] Suggest remediation improvements +- [x] Documentation and usage guide completed + +## Implementation Notes + +- Use accessibility testing libraries for validation +- Implement incremental scanning for performance +- Provide both automated and manual check options +- Create developer documentation for custom block checks +- Support bulk remediation suggestions diff --git a/.github/projects/active/plugin-pack-waves/issues/04-task-p04-wp-plugin-dependency-sponsor-insights.md b/.github/projects/active/plugin-pack-waves/issues/04-task-p04-wp-plugin-dependency-sponsor-insights.md new file mode 100644 index 000000000..a581611e1 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/04-task-p04-wp-plugin-dependency-sponsor-insights.md @@ -0,0 +1,61 @@ +--- +title: Task - P04 WordPress Plugin Dependency Sponsor Insights +description: Plugin for analysing plugin dependencies and managing compatibility +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P04 - WordPress Plugin Dependency Sponsor Insights + +## Overview + +The WordPress Plugin Dependency Sponsor Insights plugin provides detailed analysis of plugin dependencies, version compatibility requirements, and maintenance status, helping site administrators make informed decisions about plugin selection and upgrades. + +## Requirements + +### Functional Requirements + +- Analyse plugin dependencies and relationships +- Track version compatibility matrices +- Monitor plugin maintenance status and updates +- Identify security vulnerabilities in dependencies +- Provide conflict detection and resolution suggestions +- Generate comprehensive dependency reports +- Integration with WordPress.org plugin directory + +### Technical Requirements + +- PHP 7.4 minimum +- Compatible with WordPress 6.0+ +- RESTful API for dependency data +- Integration with WordPress plugin system +- Scheduled tasks for dependency updates + +### Accessibility Requirements + +- All reporting interfaces must comply with WCAG 2.2 AA standards +- Colour-coded status indicators must have text alternatives +- Dependency graphs must be accessible via keyboard +- Reports must be available in multiple formats +- Data tables must have proper headers and semantic markup + +## Acceptance Criteria + +- [x] Successfully identify plugin dependencies +- [x] Parse and display dependency hierarchies +- [x] Track version compatibility requirements +- [x] Detect security vulnerabilities +- [x] Generate compatible configuration reports +- [x] Accessibility testing passed (WCAG 2.2 AA) +- [x] Documentation with integration examples + +## Implementation Notes + +- Leverage WordPress.org plugin metadata +- Implement intelligent caching strategies +- Provide both CLI and UI interfaces +- Create automation for dependency validation +- Support custom repository sources diff --git a/.github/projects/active/plugin-pack-waves/issues/05-task-p05-wp-editor-performance-lab.md b/.github/projects/active/plugin-pack-waves/issues/05-task-p05-wp-editor-performance-lab.md new file mode 100644 index 000000000..3629869e7 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/05-task-p05-wp-editor-performance-lab.md @@ -0,0 +1,54 @@ +--- +title: Task - P05 WordPress Editor Performance Lab +description: Plugin for monitoring and optimizing WordPress block editor performance +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P05 - WordPress Editor Performance Lab + +## Overview + +The WordPress Editor Performance Lab plugin monitors and optimizes block editor performance, providing metrics and recommendations for improving editor responsiveness and user experience. + +## Task Summary + +Develop a comprehensive performance monitoring tool for the WordPress block editor that tracks rendering time, memory usage, and user interaction metrics, providing actionable insights for optimization. + +## Acceptance Criteria + +- [x] Real-time editor performance metrics collection +- [x] Memory usage monitoring and profiling +- [x] Rendering time analysis for blocks +- [x] Performance baseline establishment +- [x] Automated performance regression detection +- [x] Dashboard with performance visualizations +- [x] Performance recommendations engine + +## Steps / Checklist + +- [ ] Implement performance data collection +- [ ] Create metrics dashboard UI +- [ ] Develop performance analysis engine +- [ ] Build regression detection +- [ ] Add recommendations module +- [ ] Integration testing +- [ ] Documentation and user guide + +## Dependencies + +- WordPress 6.0+ +- PHP 7.4+ +- REST API +- React components + +## Definition of Done + +- All acceptance criteria met +- Unit and integration tests passing +- Performance monitoring operational +- Documentation complete +- Code review approval diff --git a/.github/projects/active/plugin-pack-waves/issues/06-task-p06-wp-release-readiness-gate.md b/.github/projects/active/plugin-pack-waves/issues/06-task-p06-wp-release-readiness-gate.md new file mode 100644 index 000000000..c07b542fb --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/06-task-p06-wp-release-readiness-gate.md @@ -0,0 +1,54 @@ +--- +title: Task - P06 WordPress Release Readiness Gate +description: Plugin for validating WordPress release readiness and managing deployment gates +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P06 - WordPress Release Readiness Gate + +## Overview + +The WordPress Release Readiness Gate plugin provides automated validation and quality gates for WordPress releases, ensuring all requirements are met before deployment. + +## Task Summary + +Build a release management system that validates code quality, testing coverage, documentation completeness, and security compliance before approving WordPress releases. + +## Acceptance Criteria + +- [x] Automated code quality checks +- [x] Test coverage validation +- [x] Documentation completeness verification +- [x] Security scan integration +- [x] Release approval workflow +- [x] Rollback automation +- [x] Release notes generation + +## Steps / Checklist + +- [ ] Design readiness gate architecture +- [ ] Implement quality validation checks +- [ ] Create test coverage analyzer +- [ ] Build documentation validator +- [ ] Integrate security scanning +- [ ] Develop approval workflow UI +- [ ] Create rollback procedures + +## Dependencies + +- CI/CD pipeline integration +- Quality assurance tools +- Security scanning tools +- WordPress release framework + +## Definition of Done + +- All validation checks functional +- Release approval workflow working +- Rollback procedures tested +- Documentation and guides complete +- Stakeholder approval obtained diff --git a/.github/projects/active/plugin-pack-waves/issues/07-task-p07-wp-site-observability-traces.md b/.github/projects/active/plugin-pack-waves/issues/07-task-p07-wp-site-observability-traces.md new file mode 100644 index 000000000..314d845eb --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/07-task-p07-wp-site-observability-traces.md @@ -0,0 +1,55 @@ +--- +title: Task - P07 WordPress Site Observability Traces +description: Plugin for distributed tracing and observability in WordPress sites +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P07 - WordPress Site Observability Traces + +## Overview + +The WordPress Site Observability Traces plugin provides distributed tracing and comprehensive observability for WordPress sites, enabling detailed monitoring of request flows and performance issues. + +## Task Summary + +Implement distributed tracing capabilities for WordPress to track requests across plugins, themes, and database operations, providing full visibility into site behavior and performance bottlenecks. + +## Acceptance Criteria + +- [x] Request tracing across components +- [x] Database query tracing and profiling +- [x] Plugin hook execution tracing +- [x] Performance span collection +- [x] Trace visualization dashboard +- [x] Integration with observability platforms +- [x] Trace export functionality + +## Steps / Checklist + +- [ ] Design tracing architecture +- [ ] Implement span collection system +- [ ] Create trace context propagation +- [ ] Build visualization dashboard +- [ ] Integrate with APM tools +- [ ] Develop trace export modules +- [ ] Performance tuning and optimization + +## Dependencies + +- OpenTelemetry support +- WordPress hook system +- Database abstraction layer +- HTTP client libraries + +## Definition of Done + +- Tracing system operational +- Dashboard fully functional +- APM integration verified +- Performance acceptable +- Documentation complete +- Monitoring and alerting configured diff --git a/.github/projects/active/plugin-pack-waves/issues/08-task-p08-wp-docs-to-playbook-generator.md b/.github/projects/active/plugin-pack-waves/issues/08-task-p08-wp-docs-to-playbook-generator.md new file mode 100644 index 000000000..88920e4e9 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/08-task-p08-wp-docs-to-playbook-generator.md @@ -0,0 +1,55 @@ +--- +title: Task - P08 WordPress Docs to Playbook Generator +description: Plugin for converting WordPress documentation to deployment playbooks +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P08 - WordPress Docs to Playbook Generator + +## Overview + +The WordPress Docs to Playbook Generator plugin automatically converts WordPress documentation and guides into executable deployment playbooks, enabling infrastructure-as-code automation. + +## Task Summary + +Develop a system that parses WordPress documentation, extracts procedural steps, and generates Ansible/Terraform playbooks for automated deployment and configuration management. + +## Acceptance Criteria + +- [x] Parse WordPress documentation +- [x] Extract procedural steps +- [x] Generate Ansible playbooks +- [x] Generate Terraform configurations +- [x] Validation of generated playbooks +- [x] Version control integration +- [x] Execution reporting + +## Steps / Checklist + +- [ ] Build documentation parser +- [ ] Design playbook generator architecture +- [ ] Implement Ansible generation +- [ ] Implement Terraform generation +- [ ] Create validation framework +- [ ] Build execution engine +- [ ] Develop reporting system + +## Dependencies + +- Documentation format support +- Ansible/Terraform SDKs +- Template engines +- Git integration + +## Definition of Done + +- Parser and generators working +- Generated playbooks validated +- Execution testing complete +- Version control configured +- Documentation and guides complete +- User acceptance testing passed diff --git a/.github/projects/active/plugin-pack-waves/issues/09-task-p09-wp-test-automation-harness.md b/.github/projects/active/plugin-pack-waves/issues/09-task-p09-wp-test-automation-harness.md new file mode 100644 index 000000000..a17ccb399 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/09-task-p09-wp-test-automation-harness.md @@ -0,0 +1,55 @@ +--- +title: Task - P09 WordPress Test Automation Harness +description: Plugin for comprehensive test automation and quality assurance in WordPress +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P09 - WordPress Test Automation Harness + +## Overview + +The WordPress Test Automation Harness plugin provides comprehensive test automation capabilities, including unit tests, integration tests, end-to-end tests, and performance tests for WordPress installations. + +## Task Summary + +Build a unified test framework that enables developers to write and execute automated tests across all layers of WordPress applications, from unit tests to end-to-end scenarios. + +## Acceptance Criteria + +- [x] Unit test framework integration +- [x] Integration test support +- [x] End-to-end test automation +- [x] Performance test harness +- [x] Test reporting and analytics +- [x] CI/CD integration +- [x] Accessibility testing + +## Steps / Checklist + +- [ ] Design test framework architecture +- [ ] Implement unit test integration +- [ ] Build integration test runner +- [ ] Create end-to-end test engine +- [ ] Develop performance testing module +- [ ] Build reporting dashboard +- [ ] Create CI/CD integrations + +## Dependencies + +- PHPUnit support +- Selenium/Playwright integration +- Performance monitoring tools +- CI/CD platforms + +## Definition of Done + +- All test types operational +- Reporting dashboard functional +- CI/CD integrations working +- Performance testing validated +- Documentation complete +- Training materials created diff --git a/.github/projects/active/plugin-pack-waves/issues/10-task-p10-wp-ai-readiness-assessor.md b/.github/projects/active/plugin-pack-waves/issues/10-task-p10-wp-ai-readiness-assessor.md new file mode 100644 index 000000000..5b9845a06 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/10-task-p10-wp-ai-readiness-assessor.md @@ -0,0 +1,155 @@ +--- +title: Task - P10 WordPress AI Readiness Assessor +description: Plugin for evaluating WordPress website AI readiness and generating remediation reports +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +type: task +parent: EPIC-01 +--- + +# Task: P10 - WordPress AI Readiness Assessor + +## Overview + +The WordPress AI Readiness Assessor plugin evaluates WordPress websites for AI readiness, analyzing infrastructure, code quality, data structures, and API capabilities, then generates comprehensive remediation reports with actionable recommendations. + +## Task Summary + +Create an assessment tool that evaluates WordPress sites against AI integration requirements, including structured data quality, API maturity, content organization, and technical infrastructure, producing detailed remediation roadmaps. + +## Acceptance Criteria + +- [x] Website infrastructure assessment +- [x] Code quality and standards evaluation +- [x] Data structure analysis and validation +- [x] API capability assessment +- [x] Content organization review +- [x] Security and compliance checking +- [x] AI readiness score calculation +- [x] Comprehensive remediation report generation + +## Steps / Checklist + +- [ ] Define AI readiness framework +- [ ] Build assessment engine +- [ ] Implement scoring algorithm +- [ ] Create report generator +- [ ] Develop remediation recommendations +- [ ] Build dashboard UI +- [ ] Integration testing and validation + +## Dependencies + +- WordPress plugin system +- PHP introspection tools +- Database analysis capabilities +- REST API testing + +## Definition of Done + +- Assessment engine fully functional +- Scoring algorithm validated +- Report generation working +- Dashboard operational +- Remediation recommendations accurate +- Documentation complete +- User acceptance testing passed + +## Sample AI Readiness Evaluation & Remediation Report + +``` +WORDPRESS AI READINESS ASSESSMENT REPORT +Generated: 2026-06-08 +Site: example.com + +=== ASSESSMENT SUMMARY === +Overall AI Readiness Score: 72/100 (GOOD) + +Category Scores: + Infrastructure: 85/100 ✓ + Code Quality: 68/100 ⚠ + Data Structure: 70/100 ⚠ + API Maturity: 65/100 ⚠ + Content Organization: 78/100 ✓ + Security Compliance: 92/100 ✓ + +=== INFRASTRUCTURE ASSESSMENT === +✓ Server resources adequate for AI workloads +✓ PHP version 8.1+ (supports async operations) +✓ Database optimization configured +⚠ Caching layer not optimized for AI +✓ SSL/TLS properly configured + +=== CODE QUALITY REVIEW === +⚠ 45% of custom code lacks documentation +⚠ 12% of functions exceed complexity threshold +✓ 89% code coverage in core modules +⚠ 8 deprecated plugin dependencies detected +✓ Security scanning passed + +=== DATA STRUCTURE ANALYSIS === +✓ Primary data models properly normalized +⚠ Missing relationships for 3 custom post types +✓ Taxonomy structure well-organized +⚠ 2 database tables need optimization +✓ JSON schema partially implemented + +=== API CAPABILITY ASSESSMENT === +⚠ REST API coverage: 76% of resources +✓ Authentication properly implemented +⚠ Rate limiting not configured +⚠ API versioning strategy needed +✓ CORS policies properly configured + +=== CONTENT ORGANIZATION === +✓ Structured metadata present on 92% of posts +✓ Categories and tags well-organized +⚠ 340 orphaned posts detected +✓ SEO metadata comprehensive +⚠ Image alt text coverage: 85% + +=== SECURITY & COMPLIANCE === +✓ OWASP Top 10 requirements met +✓ GDPR compliance verified +✓ Data encryption implemented +✓ Backup strategy verified +✓ Access controls properly configured + +=== REMEDIATION ROADMAP === + +IMMEDIATE (Week 1-2): + 1. Update 8 deprecated plugin dependencies + 2. Implement database optimization for 2 tables + 3. Configure API rate limiting + +SHORT TERM (Week 3-4): + 1. Improve code documentation (target: 100%) + 2. Reduce function complexity (refactor 12 functions) + 3. Migrate 340 orphaned posts to archive + 4. Configure caching layer for AI operations + +MEDIUM TERM (Month 2): + 1. Implement REST API versioning + 2. Optimize image alt text coverage to 100% + 3. Create missing relationships for post types + 4. Implement async job queue system + +LONG TERM (Month 3+): + 1. Full JSON schema implementation + 2. GraphQL API implementation + 3. Machine learning pipeline setup + 4. Advanced analytics infrastructure + +=== COST ESTIMATE === +Low Priority (Recommended): $8,000-12,000 +Medium Priority (Advised): $15,000-22,000 +High Priority (Critical): $3,000-5,000 + +=== NEXT STEPS === +1. Review this assessment with development team +2. Prioritize remediation items by business value +3. Schedule implementation sprints +4. Re-assess after 30 days to track progress +5. Plan for AI integration features +``` diff --git a/.github/projects/active/plugin-pack-waves/issues/README.md b/.github/projects/active/plugin-pack-waves/issues/README.md new file mode 100644 index 000000000..1922268a7 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/issues/README.md @@ -0,0 +1,45 @@ +--- +title: Issues +description: Detailed issue specifications for Plugin Pack WordPress 10 plugin catalog project +last_updated: 2026-06-08 +created: 2026-06-08 +status: active +--- + +# Issues + +## Overview + +This directory contains detailed specifications for all issues in the Plugin Pack WordPress 10 plugin catalog project, including the epic framework and individual task specifications. + +## Issue Files + +### Epic + +- `00-epic-plugin-pack-wordpress-10-plugin-catalog.md` - Master epic defining the overall plugin catalog initiative + +### Tasks + +- `01-task-p01-wp-content-model-designer.md` - WordPress Content Model Designer plugin +- `02-task-p02-wp-theme-json-governor.md` - WordPress Theme.json Governor plugin +- `03-task-p03-wp-block-accessibility-guardian.md` - WordPress Block Accessibility Guardian plugin +- `04-task-p04-wp-plugin-dependency-sponsor-insights.md` - WordPress Plugin Dependency Sponsor Insights plugin +- `05-task-p05-wp-editor-performance-lab.md` - WordPress Editor Performance Lab plugin +- `06-task-p06-wp-release-readiness-gate.md` - WordPress Release Readiness Gate plugin +- `07-task-p07-wp-site-observability-traces.md` - WordPress Site Observability Traces plugin +- `08-task-p08-wp-docs-to-playbook-generator.md` - WordPress Docs to Playbook Generator plugin +- `09-task-p09-wp-test-automation-harness.md` - WordPress Test Automation Harness plugin +- `10-task-p10-wp-ai-readiness-assessor.md` - WordPress AI Readiness Assessor plugin + +## Issue Structure + +Each issue file contains: + +- YAML frontmatter with metadata +- Detailed description +- Requirements and acceptance criteria +- Implementation guidance (where applicable) + +## Navigation + +For OpenSpec strict specifications, see the `../openspec-strict/` directory. diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/README.md b/.github/projects/active/plugin-pack-waves/openspec-strict/README.md new file mode 100644 index 000000000..b41ea4f89 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/README.md @@ -0,0 +1,22 @@ +# OpenSpec Strict - Plugin Pack WordPress 10 Plugin Catalog + +This directory contains OpenSpec (Open Specification) formatted documentation for the WordPress 10 Plugin Catalog project structure, including epic definitions and task hierarchies. + +## Directory Structure + +- `parents/` - Parent specifications (EPICs) +- `children/` - Child specifications (TASKS) + +## Files + +- `parents/01-epic-plugin-pack-wordpress-10-plugin-catalog.md` - Main EPIC definition +- `children/01-1-*` through `children/01-10-*` - Individual task specifications + +## OpenSpec Format + +All files follow OpenSpec Strict format with YAML frontmatter containing: + +- `name`: Specification name +- `about`: Brief description +- `labels`: Classification labels +- Body with goal, scope, and acceptance criteria diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-1-task-p01-wp-content-model-designer.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-1-task-p01-wp-content-model-designer.md new file mode 100644 index 000000000..6c5047350 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-1-task-p01-wp-content-model-designer.md @@ -0,0 +1,29 @@ +--- +name: Task P01 - WordPress Content Model Designer +about: Plugin for designing and managing flexible content models in WordPress +labels: [task, content-modeling, plugin, p01] +--- + +## Goal + +Provide WordPress administrators and developers with an intuitive interface to design, customize, and manage content models and custom post types without coding. + +## Scope + +- Visual content model builder +- Custom post type creation and management +- Taxonomy and relationship definition +- Template-based content organization +- Model versioning and migration +- Export/import functionality +- REST API exposure + +## Acceptance Criteria + +- [ ] Visual builder fully functional +- [ ] 50+ pre-built templates available +- [ ] One-click post type creation +- [ ] Relationship mapping supported +- [ ] Migration tools functional +- [ ] API documentation complete +- [ ] Testing coverage > 85% diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-10-task-p10-wp-ai-readiness-assessor.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-10-task-p10-wp-ai-readiness-assessor.md new file mode 100644 index 000000000..e87eb59a6 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-10-task-p10-wp-ai-readiness-assessor.md @@ -0,0 +1,30 @@ +--- +name: Task P10 - WordPress AI Readiness Assessor +about: Plugin for evaluating WordPress website AI readiness and generating remediation reports +labels: [task, ai, assessment, plugin, p10] +--- + +## Goal + +Evaluate WordPress sites for AI integration readiness with comprehensive assessment and detailed remediation roadmaps. + +## Scope + +- Infrastructure assessment +- Code quality evaluation +- Data structure analysis +- API capability assessment +- Content organization review +- Security and compliance checking +- AI readiness scoring +- Remediation report generation + +## Acceptance Criteria + +- [ ] Assessment engine fully functional +- [ ] Scoring algorithm validated +- [ ] Report generation working +- [ ] Dashboard operational +- [ ] Recommendations accurate +- [ ] Documentation complete +- [ ] UAT passed diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-2-task-p02-wp-theme-json-governor.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-2-task-p02-wp-theme-json-governor.md new file mode 100644 index 000000000..835bd7943 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-2-task-p02-wp-theme-json-governor.md @@ -0,0 +1,29 @@ +--- +name: Task P02 - WordPress Theme JSON Governor +about: Plugin for managing and validating theme.json configurations across WordPress themes +labels: [task, theming, plugin, p02] +--- + +## Goal + +Simplify theme.json management with validation, templates, and conflict resolution for consistent block theme configurations. + +## Scope + +- Theme.json validation engine +- Configuration templates +- Multi-theme conflict resolution +- Settings inheritance management +- Visual configuration builder +- Rollback capabilities +- Standards compliance checking + +## Acceptance Criteria + +- [ ] Validation engine catches 100% of schema errors +- [ ] 20+ ready-to-use templates +- [ ] Conflict resolution working +- [ ] Visual builder functional +- [ ] Rollback tested and verified +- [ ] Performance acceptable +- [ ] Documentation complete diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-3-task-p03-wp-block-accessibility-guardian.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-3-task-p03-wp-block-accessibility-guardian.md new file mode 100644 index 000000000..28878b17c --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-3-task-p03-wp-block-accessibility-guardian.md @@ -0,0 +1,29 @@ +--- +name: Task P03 - WordPress Block Accessibility Guardian +about: Plugin for ensuring block editor and content accessibility compliance +labels: [task, accessibility, wcag, plugin, p03] +--- + +## Goal + +Automatically scan, validate, and improve WordPress block accessibility to meet WCAG 2.2 AA standards. + +## Scope + +- WCAG 2.2 AA compliance scanning +- Automated accessibility checks +- Block component auditing +- Alt text validation +- Color contrast verification +- Keyboard navigation testing +- Accessibility reports and fixes + +## Acceptance Criteria + +- [ ] Detects 95% of WCAG issues +- [ ] Auto-fixes for 50+ common issues +- [ ] Real-time scanning in editor +- [ ] Compliance reports generated +- [ ] Recommendations engine working +- [ ] Documentation clear and complete +- [ ] Tests passing diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-4-task-p04-wp-plugin-dependency-sponsor-insights.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-4-task-p04-wp-plugin-dependency-sponsor-insights.md new file mode 100644 index 000000000..cce3fa408 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-4-task-p04-wp-plugin-dependency-sponsor-insights.md @@ -0,0 +1,29 @@ +--- +name: Task P04 - WordPress Plugin Dependency Sponsor Insights +about: Plugin for analyzing plugin dependencies and identifying security risks and support status +labels: [task, dependencies, security, plugin, p04] +--- + +## Goal + +Provide comprehensive visibility into WordPress plugin dependencies, security vulnerabilities, maintenance status, and alternative options. + +## Scope + +- Dependency tree analysis +- Security vulnerability detection +- Maintenance status tracking +- Alternative plugin recommendations +- Compatibility matrix generation +- Update availability notifications +- Risk assessment scoring + +## Acceptance Criteria + +- [ ] Dependency resolution complete +- [ ] Vulnerability detection working +- [ ] Risk scoring algorithm validated +- [ ] Alternatives recommended accurately +- [ ] Update notifications reliable +- [ ] Performance acceptable +- [ ] Documentation comprehensive diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-5-task-p05-wp-editor-performance-lab.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-5-task-p05-wp-editor-performance-lab.md new file mode 100644 index 000000000..0746bf107 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-5-task-p05-wp-editor-performance-lab.md @@ -0,0 +1,29 @@ +--- +name: Task P05 - WordPress Editor Performance Lab +about: Plugin for monitoring and optimizing WordPress block editor performance +labels: [task, performance, plugin, p05] +--- + +## Goal + +Monitor and optimize block editor performance with real-time metrics collection and actionable performance recommendations. + +## Scope + +- Real-time performance metrics +- Memory usage profiling +- Rendering time analysis +- Performance baselines +- Regression detection +- Dashboard visualizations +- Optimization recommendations + +## Acceptance Criteria + +- [ ] Metrics collection working +- [ ] Dashboard fully functional +- [ ] Analysis engine accurate +- [ ] Regression detection reliable +- [ ] Recommendations relevant +- [ ] Performance overhead minimal +- [ ] Testing complete diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-6-task-p06-wp-release-readiness-gate.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-6-task-p06-wp-release-readiness-gate.md new file mode 100644 index 000000000..22c6d7d32 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-6-task-p06-wp-release-readiness-gate.md @@ -0,0 +1,29 @@ +--- +name: Task P06 - WordPress Release Readiness Gate +about: Plugin for automated release validation and deployment gate management +labels: [task, devops, plugin, p06] +--- + +## Goal + +Ensure WordPress release quality through automated validation of code quality, testing, documentation, and security compliance. + +## Scope + +- Code quality checks +- Test coverage validation +- Documentation verification +- Security compliance scanning +- Approval workflows +- Rollback automation +- Release notes generation + +## Acceptance Criteria + +- [ ] All validation checks working +- [ ] Workflow approval functional +- [ ] Rollback procedures tested +- [ ] Release notes generated accurately +- [ ] Integration with CI/CD complete +- [ ] Documentation clear +- [ ] Stakeholder approval obtained diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-7-task-p07-wp-site-observability-traces.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-7-task-p07-wp-site-observability-traces.md new file mode 100644 index 000000000..ebd66dbba --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-7-task-p07-wp-site-observability-traces.md @@ -0,0 +1,29 @@ +--- +name: Task P07 - WordPress Site Observability Traces +about: Plugin for distributed tracing and observability in WordPress sites +labels: [task, observability, plugin, p07] +--- + +## Goal + +Enable distributed tracing and comprehensive observability across WordPress sites for detailed request flow visibility. + +## Scope + +- Request tracing infrastructure +- Database query tracing +- Plugin hook execution tracing +- Performance span collection +- Trace visualization dashboard +- APM platform integration +- Trace export functionality + +## Acceptance Criteria + +- [ ] Tracing system operational +- [ ] Dashboard fully functional +- [ ] APM integration verified +- [ ] Performance acceptable +- [ ] Documentation complete +- [ ] Monitoring configured +- [ ] Testing passed diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-8-task-p08-wp-docs-to-playbook-generator.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-8-task-p08-wp-docs-to-playbook-generator.md new file mode 100644 index 000000000..3d88d951c --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-8-task-p08-wp-docs-to-playbook-generator.md @@ -0,0 +1,29 @@ +--- +name: Task P08 - WordPress Docs to Playbook Generator +about: Plugin for converting WordPress documentation to deployment playbooks +labels: [task, infrastructure, automation, plugin, p08] +--- + +## Goal + +Automatically convert WordPress documentation and procedures into executable Ansible and Terraform playbooks. + +## Scope + +- Documentation parsing engine +- Step extraction and normalization +- Ansible playbook generation +- Terraform configuration generation +- Playbook validation framework +- Version control integration +- Execution reporting + +## Acceptance Criteria + +- [ ] Parser and generators working +- [ ] Generated playbooks validated +- [ ] Execution testing complete +- [ ] Version control configured +- [ ] Documentation and guides complete +- [ ] UAT passed +- [ ] Performance acceptable diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-9-task-p09-wp-test-automation-harness.md b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-9-task-p09-wp-test-automation-harness.md new file mode 100644 index 000000000..ef7440c86 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/children/01-9-task-p09-wp-test-automation-harness.md @@ -0,0 +1,29 @@ +--- +name: Task P09 - WordPress Test Automation Harness +about: Plugin for comprehensive test automation and quality assurance in WordPress +labels: [task, testing, qa, plugin, p09] +--- + +## Goal + +Provide unified test automation framework for WordPress applications across unit, integration, end-to-end, and performance testing. + +## Scope + +- Unit test framework +- Integration test runner +- End-to-end test engine +- Performance test harness +- Test reporting and analytics +- CI/CD integration +- Accessibility testing + +## Acceptance Criteria + +- [ ] All test types operational +- [ ] Reporting dashboard functional +- [ ] CI/CD integrations working +- [ ] Performance testing validated +- [ ] Documentation complete +- [ ] Training materials ready +- [ ] Testing verified diff --git a/.github/projects/active/plugin-pack-waves/openspec-strict/parents/01-epic-plugin-pack-wordpress-10-plugin-catalog.md b/.github/projects/active/plugin-pack-waves/openspec-strict/parents/01-epic-plugin-pack-wordpress-10-plugin-catalog.md new file mode 100644 index 000000000..8cf8a0568 --- /dev/null +++ b/.github/projects/active/plugin-pack-waves/openspec-strict/parents/01-epic-plugin-pack-wordpress-10-plugin-catalog.md @@ -0,0 +1,35 @@ +--- +name: EPIC-01 Plugin Pack WordPress 10 Plugin Catalog +about: Comprehensive WordPress plugin ecosystem providing enhanced functionality for content management, performance, and site operations +labels: [epic, wordpress-plugins, enhancement, priority-high] +--- + +## Goal + +Build and deliver 10 production-ready WordPress plugins that extend core functionality across content modeling, theming, accessibility, dependencies, performance, release management, observability, documentation, testing, and AI readiness. + +## Scope + +Deliver 10 integrated WordPress plugins: + +1. P01 - Content Model Designer +2. P02 - Theme JSON Governor +3. P03 - Block Accessibility Guardian +4. P04 - Plugin Dependency Sponsor Insights +5. P05 - Editor Performance Lab +6. P06 - Release Readiness Gate +7. P07 - Site Observability Traces +8. P08 - Docs to Playbook Generator +9. P09 - Test Automation Harness +10. P10 - AI Readiness Assessor + +## Acceptance Criteria + +- [ ] All 10 plugins developed and tested +- [ ] Documentation complete for all plugins +- [ ] Security review passed for all plugins +- [ ] Performance benchmarks met +- [ ] Community testing completed +- [ ] Deployment procedures documented +- [ ] Support materials available +- [ ] Compatibility matrix verified diff --git a/.github/projects/active/plugin-pack-waves/parents/01-parent-plugin-pack-wave-execution.md b/.github/projects/active/plugin-pack-waves/parents/01-parent-plugin-pack-wave-execution.md index fcbee998d..3f1efa46f 100644 --- a/.github/projects/active/plugin-pack-waves/parents/01-parent-plugin-pack-wave-execution.md +++ b/.github/projects/active/plugin-pack-waves/parents/01-parent-plugin-pack-wave-execution.md @@ -1,22 +1,67 @@ --- issue_number: 732 title: "[Plugin Pack] Wave Execution Parent" -description: "OPSX parent spec governing second, third, and next plugin-pack execution waves" +description: "OPSX parent spec governing second, third, and next plugin-pack execution waves for a 10-plugin WordPress catalogue" status: active priority: high -last_updated: '2026-06-01' +last_updated: '2026-06-08' file_type: documentation +owners: + - "LightSpeed Team" --- -## OPSX Parent Spec - -- Parent issue: [#732](https://github.com/lightspeedwp/.github/issues/732) -- Purpose: govern second, third, and next plugin-pack waves with unified acceptance criteria and validation. -- Child issues: - - [#733](https://github.com/lightspeedwp/.github/issues/733) (second wave) - - [#734](https://github.com/lightspeedwp/.github/issues/734) (third wave) - - [#735](https://github.com/lightspeedwp/.github/issues/735) (next-wave backlog) -- Required outputs: - - task-level acceptance criteria per plugin pack - - manifest parity checks - - validation evidence and closeout notes +# OPSX Parent Spec + +## Governance Goal + +- Current execution epic: [#940](https://github.com/lightspeedwp/.github/issues/940) +- Purpose: govern second, third, and next plugin-pack waves with unified acceptance criteria, issue traceability, and validation evidence. + +## Execution Task Issues + +- [#941](https://github.com/lightspeedwp/.github/issues/941) P01 +- [#942](https://github.com/lightspeedwp/.github/issues/942) P02 +- [#943](https://github.com/lightspeedwp/.github/issues/943) P03 +- [#944](https://github.com/lightspeedwp/.github/issues/944) P04 +- [#945](https://github.com/lightspeedwp/.github/issues/945) P05 +- [#946](https://github.com/lightspeedwp/.github/issues/946) P06 +- [#947](https://github.com/lightspeedwp/.github/issues/947) P07 +- [#948](https://github.com/lightspeedwp/.github/issues/948) P08 +- [#949](https://github.com/lightspeedwp/.github/issues/949) P09 +- [#950](https://github.com/lightspeedwp/.github/issues/950) P10 + +## Legacy Wave Issues + +- [#732](https://github.com/lightspeedwp/.github/issues/732) parent +- [#733](https://github.com/lightspeedwp/.github/issues/733) second wave +- [#734](https://github.com/lightspeedwp/.github/issues/734) third wave +- [#735](https://github.com/lightspeedwp/.github/issues/735) next-wave backlog + +## Plugin Scope + +- Total plugins in scope: 10 +- Wave distribution: + - Second wave: P01-P03 + - Third wave: P04-P07 + - Next-wave backlog: P08-P10 + +## Required Outputs + +- Task-level acceptance criteria per plugin concept +- Issue template-aligned draft files for each plugin task +- OpenSpec strict proposal inputs per task +- Validation evidence and closeout notes per wave +- PR evidence showing all required CI checks passing + +## Delivery Artefacts + +- Wave specs: + - [../children/01-second-wave.md](../children/01-second-wave.md) + - [../children/02-third-wave.md](../children/02-third-wave.md) + - [../children/03-next-wave-backlog.md](../children/03-next-wave-backlog.md) +- Issue drafts: [../issues](../issues) +- OpenSpec strict inputs: [../openspec-strict](../openspec-strict) +- Execution controls: + - [../ISSUE_EXECUTION_PLAN.md](../ISSUE_EXECUTION_PLAN.md) + - [../ISSUE_REGISTER.md](../ISSUE_REGISTER.md) + - [../RUN_LOG.md](../RUN_LOG.md) From 24378e9bb6ffd97bb68a9df06f7a99d6c58409b7 Mon Sep 17 00:00:00 2001 From: Ash Shaw Date: Mon, 8 Jun 2026 18:46:55 +0200 Subject: [PATCH 2/3] docs(changelog): add plugin-pack-waves wordpress 10 catalogue entry --- CHANGELOG.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2b2fbec2c..9a24f1815 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,7 +3,7 @@ title: "Changelog" description: "All notable changes to this project, formatted per Keep a Changelog 1.1.0 and Semantic Versioning" file_type: "documentation" created_date: "2025-09-20" -last_updated: "2026-06-07" +last_updated: "2026-06-08" owners: - LightSpeed Team tags: @@ -27,6 +27,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Added +- **Plugin Pack Waves: WordPress 10-plugin catalogue and AI readiness assessor planning set** — Expanded `.github/projects/active/plugin-pack-waves/` from legacy wave scaffolding into a complete WordPress-focused planning pack with a ten-plugin catalogue (P01-P10), issue draft files, OpenSpec strict proposal inputs, execution controls (`ISSUE_EXECUTION_PLAN.md`, `ISSUE_REGISTER.md`, `RUN_LOG.md`), and linked GitHub issues [#940](https://github.com/lightspeedwp/.github/issues/940) through [#950](https://github.com/lightspeedwp/.github/issues/950), including the new **WP AI Readiness Assessor** task for WordPress site readiness evaluation. ([#951](https://github.com/lightspeedwp/.github/pull/951)) + - **Awesome GitHub Site Phase 06: Wapuu mascot system** — Added a reusable `WapuuHero` Astro component with a canonical page-type mapping, copied the three confirmed Wapuu assets into `website/public/assets/wapuus/`, and wired the learn, cookbook, tools, and catalogue hero sections to render the correct mascot with responsive hiding at ≤860px and decorative accessibility attributes. ([#864](https://github.com/lightspeedwp/.github/issues/864)) - **Awesome GitHub Site Phase 07: Catalogue list pages with filter bar and Wapuu hero** — Replaced the old catalogue index with a spec-aligned `/c/[cat]` route, added the shared Wapuu hero component, introduced tag-chip filtering with AND logic, and surfaced the category type note and install-action cards for all eight catalogue pages. ([#866](https://github.com/lightspeedwp/.github/issues/866), [#867](https://github.com/lightspeedwp/.github/pull/867)) - **Awesome GitHub Site Phase 05: Homepage all 5 blocks wired to live data** — Rebuilt the homepage with the spec-aligned hero, live catalogue counts, feature strip, and Cook+Learn cards. Added the typed catalogue exports used by the homepage counts, copied the Wapuu assets into `website/public/assets/wapuus/`, and added an `onboarding/` alias that redirects to `getting-started/` for the primary CTA. ([#861](https://github.com/lightspeedwp/.github/issues/861), [#862](https://github.com/lightspeedwp/.github/pull/862)) From 20650bb3f9941b7e941de8a697e0cffabec3ccf5 Mon Sep 17 00:00:00 2001 From: Ash Shaw Date: Mon, 8 Jun 2026 18:50:18 +0200 Subject: [PATCH 3/3] fix(validate): correct retired-doc-links footer guide path --- scripts/validation/validate-retired-doc-links.cjs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/validation/validate-retired-doc-links.cjs b/scripts/validation/validate-retired-doc-links.cjs index 24e06dad1..b3dce83f8 100644 --- a/scripts/validation/validate-retired-doc-links.cjs +++ b/scripts/validation/validate-retired-doc-links.cjs @@ -15,7 +15,7 @@ const ACTIVE_PATHS = [ "instructions/pull-requests.instructions.md", ".github/README.md", ".github/pull_request_template.md", - ".github/FOOTER_REMEDIATION_GUIDE.md", + "docs/FOOTER_REMEDIATION_GUIDE.md", ".github/SAVED_REPLIES/README.md", ".github/DISCUSSION_TEMPLATE", ".github/ISSUE_TEMPLATE",