BMJ Master Plan v2

assetactive

BMJ Master Plan v2 (summary)

This canonical record summarizes BMJ_MASTER_PLAN_v2.md (~50KB). The full specification lives in the Identity_Design source tree on the authoring machine.

What the document is

A single-file master build plan for shipping the BMJ web platform: brand identity, legal prerequisites, dev environment setup, architecture, database SQL, design tokens, Tailwind integration, feature build order, subscriptions, hosting, analytics, SEO, and post-launch iterations—plus Claude Code workflows and copy-paste command blocks.

Phase map (high level)

  1. Brand identity — Palette, typography, visual language, logo checklist.
  2. Phase 0 — Legal and infrastructure before code.
  3. Phase 1 — Windows + Node/Git/VS Code + Claude Code + Next.js scaffold + dependencies.
  4. Phase 2 — CLAUDE.md project memory (full template in source).
  5. Phase 3 — Custom slash commands for editorial and ops tasks.
  6. Phase 4 — App structure, Supabase schema, RLS policies, indexes, auth trigger.
  7. Phase 5brand.css, globals, Tailwind extension, example components.
  8. Phase 6 — Fourteen Claude Code sessions from shell layout through deploy.
  9. Phase 7 — Stripe products, tier features, webhook events, payment routing.
  10. Phase 8 — Environment variables, Vercel, GitHub, DNS on Squarespace.
  11. Phase 9 — Plausible and SEO checklist.
  12. Phase 10 — Post-launch roadmap (immediate through long-term).
  13. Daily workflow — Core and project-specific Claude commands, pre-commit routine.
  14. Outstanding — Blockers and decisions required from leadership before build/launch.

Tech stack (from source)

Next.js 14 (App Router), TypeScript, Tailwind + CSS variables, Supabase (Postgres + Auth), Stripe, Resend, Vercel, MDX content, Plausible analytics, Claude Code CLI.

Source

Original file: Identity_Design/BMJ_MASTER_PLAN_v2.md.