V2 planning approvedDev repo isolated from production
Editorial Platform Rebuild

Yorkshire BusinessWoman V2 starts as a safer product track, not a risky production rewrite.

This dev repo now carries the approved PRD, technical architecture, and wireframes. The first goal is to establish a clean V2 shell for public, member, corporate, and admin journeys.

Why V2

The existing product already proves demand. V2 proves resilience.

The rebuild focuses on trust, clarity, observability, and new revenue layers rather than cosmetic churn.

  • Keep production stable while V2 evolves in an isolated repo.
  • Replace duplicated integration logic with explicit domain services.
  • Launch team memberships, structured opportunities, and sponsor bundles as first-class products.
Security
API Hardening

Messaging, billing, uploads, and admin operations move to server-authenticated flows.

Performance
Cache First

Public pages use targeted revalidation instead of broad force-dynamic rendering.

Operations
Sync Health

Admins get one reconciliation centre across Clerk, Stripe, Ghost, Beehiiv, and email.

Homepage Wireframe

Public home becomes a conversion-focused editorial front door.

The new structure combines editorial hero, event rail, offers preview, featured member storytelling, and sponsor-safe modules.

Top Bar -> Editorial Hero -> News Rail + Membership CTA
Featured Events Rail -> Member Story -> Offers / Opportunities
Newsletter Signup -> Footer
Editorial Priorities

Keep the magazine voice, but reduce runtime fragility.

The live site proved the content model. V2 separates public storytelling from transactional member state more cleanly.

  • Premium editorial hub with sponsor-safe placements and member-only content gating
  • Homepage blending editorial highlights, event commerce, offers, and featured member storytelling
  • Migration path from Ghost-led publishing to clearer public and member content boundaries
Delivery Sequence

The V2 build begins with shell, routing, and system boundaries.

The next iterations can layer in real data once the visual and architectural foundations are stable.

Phase 1

Foundation shell, docs, routing, auth boundaries, design system primitives

Phase 2

Public home, membership, dashboard, admin overview, reconciliation surfaces

Phase 3

Corporate workspace, opportunities marketplace, networking overhaul

Phase 4

Real read models, analytics, sync diagnostics, sponsor inventory tooling