89 lines
3.8 KiB
Markdown
89 lines
3.8 KiB
Markdown
# IGNY8 Phase 2 Roadmap & Implementation Plan
|
||
|
||
Consolidates `Igny8-part-2-plan.md` and `IGNY8-IMPLEMENTATION-PLAN.md` into a single execution roadmap.
|
||
|
||
---
|
||
|
||
## 1. Roadmap Overview
|
||
|
||
### Strategic Themes
|
||
1. **Planner Modernization** – richer clustering, taxonomy seeding, keyword governance.
|
||
2. **Site Builder Evolution** – guided wizard, taxonomy-aware sitemap generation, blueprint ↔ planner sync.
|
||
3. **Writer & Optimization Depth** – metadata propagation, product/service support, auto-linking improvements.
|
||
4. **Publishing & Sync** – IGNY8 deployments + full WordPress parity (taxonomies, products, attributes).
|
||
|
||
### Stage Rollout
|
||
| Stage | Focus | Target Outcome |
|
||
| --- | --- | --- |
|
||
| Stage 1 | Data & services foundation | New schema, clustering upgrades, workflow state APIs. |
|
||
| Stage 2 | Planner + Wizard UX | State-aware wizard, taxonomy builder, planner UI refresh. |
|
||
| Stage 3 | Writer / Linker / Optimizer | Metadata-aware tasks/content, improved linking & scoring. |
|
||
| Stage 4 | Publishing & Sync | WordPress taxonomy sync, deployment polish, QA. |
|
||
|
||
---
|
||
|
||
## 2. Detailed Workstream Breakdown
|
||
|
||
### Workstream A – Data & Services
|
||
- Apply migrations for blueprint clusters/taxonomies, writer mapping tables.
|
||
- Implement `WorkflowStateService`, validation endpoints, TaxonomyService.
|
||
- Upgrade clustering prompt/service for multi-dimensional outputs.
|
||
- Update API serializers to expose entity metadata.
|
||
|
||
### Workstream B – Planner & Wizard UX
|
||
- New planner views for clusters/taxonomies with matrix visualization.
|
||
- Wizard steps (business, clusters, taxonomy, sitemap, validation, hand-off) with gating logic.
|
||
- Toasts/tooltips/inline helpers to keep users oriented.
|
||
- Resume capability (persisted step state).
|
||
|
||
### Workstream C – Writer, Linker, Optimizer
|
||
- Extend ideas/tasks/content editors with cluster/taxonomy context panels.
|
||
- Enforce validation (no publish without assigned taxonomy/attributes).
|
||
- Linker suggestions grouped by cluster role; optimizer scoring for coverage.
|
||
- Progress dashboards per site/cluster.
|
||
|
||
### Workstream D – Publishing & Sync
|
||
- Finish WordPress taxonomy + product attribute sync (bi-directional).
|
||
- Update deployment adapters to honor new metadata; ensure renderer reads cluster/taxonomy info.
|
||
- Provide sync dashboards with health indicators, last sync timestamps.
|
||
- Final regression + staging sign-off.
|
||
|
||
---
|
||
|
||
## 3. Milestones & Deliverables
|
||
|
||
| Milestone | Key Deliverables | Dependencies |
|
||
| --- | --- | --- |
|
||
| M1 – Schema Ready | Migrations merged, services deployed, API docs updated. | None. |
|
||
| M2 – Guided Planner & Wizard | New UI flows live behind feature flag, analytics instrumented. | M1. |
|
||
| M3 – Metadata-Driven Writer | Writer/linker/optimizer using new relations, validation in place. | M2. |
|
||
| M4 – Publish & Sync Alpha | WordPress sync parity, deployment QA, release notes. | M3. |
|
||
|
||
Each milestone includes QA checklist, documentation update (master-docs + in-app help), and telemetry validation.
|
||
|
||
---
|
||
|
||
## 4. Dependencies & Risks
|
||
- **Redis/Celery availability** – AI flows block if infra not running; ensure monitoring.
|
||
- **Migration coordination** – new tables touched by multiple services; schedule maintenance window.
|
||
- **WordPress API variance** – taxonomy/product endpoints vary by site; need robust error handling + manual override UI.
|
||
- **User learning curve** – wizard adds structure; include onboarding tips and inline docs.
|
||
|
||
Mitigations described in `02-workflows.md` (UX guardrails) and `03-phase-reports.md` (lessons learned).
|
||
|
||
---
|
||
|
||
## 5. Communication & Tracking
|
||
- Maintain status in `part2-dev/README.md` with links to this roadmap.
|
||
- Sprint boards map tasks back to stage/milestone.
|
||
- Release notes reference doc IDs here for posterity.
|
||
|
||
---
|
||
|
||
## References
|
||
- Strategy context: `01-strategy.md`
|
||
- Detailed workflows: `02-workflows.md`
|
||
- Historical reports: `03-phase-reports.md`
|
||
|
||
|