A dormant legacy platform rebuilt and cut over without abandoning its production data.
A dormant WordPress platform was revived and rebuilt for production. The rebuild preserved the legacy data contract, replaced the presentation and application layer, and kept every production change behind explicit review, remediation, and deployment gates. The public result is a search-led directory with filterable data visualisations.
- Problem
- Revive a dormant platform while preserving legacy production content and the relationships between its records.
- Role
- Managing Editor, full platform and product owner, sole human rebuild lead, and final technical approver.
- Constraint
- Preserve read-only legacy fields, prevent data loss, and keep production deployment human-gated throughout.
- Decision
- Replace the presentation and application layer while retaining the production data contract intact.
How the rebuild ran.
The legacy data contract stayed fixed while project-specific agents did scoped work. Every step that touched production waited behind a human gate.
- 01Legacy platform and preserved data contract
- 0213 project-specific agent roles
- 03Human review, remediation, and re-verification
- 04Successful production cutover
The data visualisations.
The rebuild turned current organisation records into filterable analytical views rather than a static presentation layer. Step through the working surfaces below.
The SDG index.
A separate set of views makes the content model inspectable across the 17 Sustainable Development Goals: connection paths, ranked shares, a relationship network, and an overlap matrix.
Measured, not asserted.
Comparable PageSpeed categories improved on both mobile and desktop. Step between the two views below.
What changed.
- Production migration and cutover completed successfully.
- The opening AI-assisted security review logged 11 critical vulnerabilities and 85+ additional findings; all 11 critical findings were fixed and re-verified.
- Editorial publishing and maintenance were simplified while operational and security risk was reduced.
- Mobile and desktop Lighthouse categories all improved; desktop now scores in the green across every category, with mobile performance work continuing.
WordPress · GitHub Actions · specialised design, implementation, review, testing, security, migration, and deployment agents