Nairametrics Platform Evolution - Roadmap Proposal

Phase Highlights (Executive One-Pager)

This one-pager summarizes the three phases for quick executive review. For details, see the full roadmap and phase documents.

Overview

  • Strategy: Incremental evolution from a WordPress theme redesign → headless architecture → full Laravel platform.
  • Rationale: Deliver value early, de-risk architecture change, maintain editorial continuity.

Phase A — Theme Redesign (2–3 months, LOW risk)

  • Scope: New Sage 10 theme with Tailwind and Alpine; accessibility and performance uplift.
  • Outcomes: PageSpeed ≥ 90 (mobile), ≥ 95 (desktop); improved UX; no editorial change.
  • Cost: [Budget TBD] (one-time).
  • Go/No-Go Gates: Discovery complete (Wk 2) → Design approved (Wk 5) → QA & perf pass (Wk 12).
  • Link: Full Phase A

Phase B — Headless + Monorepo (6–9 months, MEDIUM risk)

  • Scope: Turborepo with Next.js (web) and Expo (mobile) sharing TS packages; Laravel API adapter; WordPress remains CMS.
  • Outcomes: ~70% code reuse; API p95 < 200ms; Web LCP < 2s; Mobile TTI < 3s; push notifications; analytics.
  • Cost: [Budget TBD] (one-time) + [Client-specific infrastructure cost]/mo infra.
  • Go/No-Go Gates: Architecture+API contracts frozen (M2) → API complete (M5) → E2E+SLO pass (M8).
  • Link: Full Phase B

Phase C — Full Laravel Migration (12–18 months, HIGH risk)

  • Scope: Migrate content and features to Laravel with Filament admin; staged cutover (parallel → dark launch → gradual).
  • Outcomes: Zero data loss; SEO preserved; API p95 < 150ms; 99.95% uptime; editorial satisfaction ≥ 80%.
  • Cost: [Budget TBD] (one-time) + [Client-specific infrastructure cost]/mo additional infra.
  • Go/No-Go Gates: Requirements freeze + mapping (Q1) → CMS core + rehearsal pass (Q3) → Dark launch SLOs (Q4).
  • Link: Full Phase C

Key KPIs by Phase

Phase KPI Targets
A PSI: 90+ mobile / 95+ desktop; LCP < 2.5s; INP < 200ms; CLS < 0.1
B API p95 < 200ms; Web LCP < 2s; Mobile TTI < 3s; Cache hit > 80%
C Uptime 99.95%; API p95 < 150ms; Zero migration data loss; SEO stability

Dependencies & Assumptions

  • A: No backend/data changes; same hosting/CDN; design approved by Week 5.
  • B: WordPress remains content source; API contract-first; team capacity (backend/web/mobile).
  • C: Phase B success ≥ 6 months; business approval; editorial training in place.

Risks & Mitigations (Summary)

  • A: Perf regression (mitigate via baseline + Lighthouse CI); design delays (timeboxed reviews).
  • B: API latency (use Redis + edge caching); SEO changes (SSR/ISR + pre-launch SEO checks); mobile scope creep (MVP-first).
  • C: Data loss (rehearsals + backups); SEO ranking shifts (redirects + gradual rollout); editorial adoption (training + champions).