v2 is not an edit of v1 — it's roughly twice the program. It keeps every existing page and adds two entirely new role tracks (a full Patient certification layer and a complete Care Partner track), an outcomes-measurement engine (PHIT), a provider ROI tool, and a real marketing/onboarding funnel. Recommendation: do not overwrite v1. Stage v2 side-by-side at a subpath, review for 1–2 weeks, then promote.
Every v1 page family is preserved. v2 layers a far larger program on top — organized around three trained roles (Patient · Care Partner · Provider), each built out across all 62 conditions.
| Capability | v1 (Live today) | v2 (New) |
|---|---|---|
| Patient condition courses | 29 | 118 |
| Patient Certification Exams | None | 62 NEW |
| Patient Pathways | None | 62 NEW |
| Patient Tools Kits | None | 63 NEW |
| Care Partner role (full track) | Partial (3 pages) | Hub + 62 Exams + 64 Pathways + 62 Kits |
| Provider layer | Hub + dashboard | + Care Transitions, Orientation, Incentive Map, Enrollment Script |
| PHIT outcomes dashboard | None | Knowledge · Actions · Confidence deltas + rollups |
| Provider Data Upload / ROI | None | Encrypted intake + dose-response analysis |
| Onboarding funnel | None | Per-role (Patient / Care Partner / Provider) |
| Marketing & sales assets | Welcome page only | + Showcase, Microshowcase, Problem·Solution·Benefits |
| Conversation Simulator / Visit Tool | None | Both new |
| Advocate Bingo | 61 | 65 (re-themed per condition) |
| Fact Sheets / Passports / Screeners / 360 | Present | Unchanged (parity) |
| Total files / size | 492 files · 31 MB | 993 files · 74 MB |
Yes, there's a standing landing page — but the front door changes between versions, and that needs a deliberate decision before we promote.
A first-time visitor lands on a true sales front door (hero, "pick your condition," "what you'll earn").
A 3-role directory. The welcome/marketing content lives in separate files: FFH-Prepared-Patient-Home, FFH-Program-Showcase, Microshowcase, Problem·Solution·Benefits.
Rob's packaged guidance is directionally right — stage side-by-side, then promote; never hard-overwrite. We agree on the safety logic; we just translate the mechanics into the FFH single-repo workflow rather than spinning up a second Vercel project.
Not recommended. Risks 404s on externally-linked v1 filenames, changes the public front door with no review window, and pushes a 62-condition change live untested.
Right instinct, wrong mechanics for us. A separate Vercel project + DNS swap doesn't match our single-repo GitHub Desktop workflow.
Deploy v2 to /prepared-patient-v2/ in the same repo. v1 stays untouched at /prepared-patient/. Zero link rot, no DNS work, full review window, then swap to promote.
Deploy v2 to /prepared-patient-v2/ in the same repo. v1 stays live and untouched at /prepared-patient/.
Use the Microshowcase as the 10-minute walk-through; verify the PHIT dashboard and the Provider Upload encrypt→decrypt→ROI cycle; have one real SCD patient complete a pre→post exam and confirm the dashboard counts it.
Swap v2 into /prepared-patient/, keep a Welcome page as the root front door, and retain a v1 archive for 30 days as fallback.
Update inbound links (Academy, Foundation, partner pages, Coach Lucy referrals) to the promoted hub.
/brand-assets/ paths + Sign-In/Sign-Up/Jump-To/Clipboard on public pages) before it becomes the production front door.Stage at /prepared-patient-v2/, review for 1–2 weeks, then promote. On approval, Lucy's team will package the standard FFH deploy script for the v2 subpath and schedule the review window.