Nairametrics Platform Evolution - Roadmap Proposal

Phase Documentation Overview

📍 Quick Links: ← Back to Roadmap Index | Simplified Roadmap | Master Roadmap

Three-Phase Evolution Strategy

The Nairametrics Website evolution follows a progressive, risk-managed approach divided into three distinct phases. Each phase builds on the previous one, minimizing disruption while delivering incremental value.

Phase Comparison

Aspect Phase A Phase B Phase C
Name Custom Theme Headless CMS Laravel Migration
Duration 2-3 months 4-6 months 6-9 months
Risk 🟢 Low 🟡 Medium 🔴 High
Budget [Budget TBD] [Budget TBD] [Budget TBD]
WordPress Full WordPress WordPress + API Phased out
Frontend Sage Theme Next.js + Expo Next.js + Expo
Editorial No change No change Filament admin
Mobile Responsive Native apps Native apps

📄 Phase Documents

Phase A: Custom WordPress Theme

Status: Ready to start
Timeline: 2-3 months (12-13 weeks)
Risk Level: 🟢 LOW

Modernize the user experience and performance without changing editorial workflows or backend architecture. Build a production-ready theme using Sage 10, Tailwind CSS, and Alpine.js.

Key Deliverables:

  • Modern, responsive WordPress theme
  • PageSpeed scores ≥ 90 (mobile), ≥ 95 (desktop)
  • Improved accessibility (WCAG 2.1 AA)
  • Foundation for Phase B decoupling

Phase B: Headless CMS + Unified Frontend

Status: Depends on Phase A completion
Timeline: 4-6 months
Risk Level: 🟡 MEDIUM

Decouple the frontend from WordPress while maintaining WordPress as the CMS. Introduce native mobile apps and a unified web experience using a Turborepo monorepo architecture.

Key Deliverables:

  • Laravel REST API layer
  • Next.js web application (SSR/SSG)
  • Expo mobile apps (iOS + Android)
  • Shared TypeScript packages (70-80% code reuse)
  • WordPress remains as CMS (editorial team unchanged)

Phase C: Complete Laravel Migration

Status: Depends on Phase B success
Timeline: 6-9 months
Risk Level: 🔴 HIGH

Replace WordPress entirely with Laravel + Filament admin. This phase is optional and should only proceed if Phase B proves successful.

Key Deliverables:

  • Full Laravel application with Filament admin panel
  • Complete data migration from WordPress
  • New editorial workflows and training
  • Mature Next.js + Expo applications
  • Zero dependency on WordPress

Transformation Guide: See Phase C Transformation Guide for detailed migration strategies and data mapping.

🎯 Quick Executive Summary

One-page overview of all phases for stakeholder presentations and quick reference.

Reading Order

For New Readers

  1. Start with Executive Summary
  2. Read Phase A Documentation in detail
  3. Review Phase B Documentation
  4. Consider Phase C Documentation as future state

For Technical Teams

  1. Review Master Roadmap for context
  2. Deep dive into relevant phase document
  3. Cross-reference with:

For Project Managers

  1. Review Phase Highlights
  2. Check Project Management Artifacts
  3. Study Migration Plan
  4. Review phase-specific timelines and budgets

Success Criteria

Phase A Gates

  • ✅ PageSpeed scores meet targets (≥ 90 mobile, ≥ 95 desktop)
  • ✅ No editorial workflow disruption
  • ✅ Accessibility compliance (WCAG 2.1 AA)
  • ✅ Zero critical bugs after 2 weeks in production

Phase B Gates

  • ✅ API performance meets SLA (< 200ms p95)
  • ✅ Mobile apps published to stores
  • ✅ User engagement metrics improve by 10%+
  • ✅ Editorial team comfortable with WordPress CMS

Phase C Gates

  • ✅ All content migrated with 100% fidelity
  • ✅ Editorial team trained and productive
  • ✅ Zero data loss or corruption
  • ✅ Performance equals or exceeds Phase B

Questions?

Last Updated: 2025-10-11

Contents