Skip to content

Marketing Site ​

Feature Overview ​

The public marketing site (instances/marketing) at professionalperformanceportfolio.com presents PPP to prospective doctors and institutions: home, plans & pricing, CPD activities, FAQs, contact, and legal pages. It also owns the site's search-engine metadata and the social link-preview card (Open Graph / Twitter) that renders when the URL is shared in WhatsApp, LinkedIn, Slack, or X.

Sources & Recordings ​
TypeDocumentSession DateLast Audited
GitHub Issue#7379 — strapline choice (Matt option 3)—2026-05-27
Brand Guidelinesdocs/site/brand/logo-assets.md, docs/site/brand/colour.md—2026-05-27

Open Questions ​

#QuestionProposed answer / statusRef
7671bRetire the "Think: Whoop for the Workplace" framing on all surfaces, or keep it as marketing voice?Removed from the share card; awaiting Matt on wider use.#7671
10122aMatt floated a "pop out screen that comes out and then just says join the waitlist" as the CTA target. Should the waitlist CTA open a pop-out/modal form instead of scrolling to the in-page waitlist form?Engineering default: scroll to the in-page waitlist form (already wired for header/hero); pop-out modal awaiting Matt.#10122
Closed Questions (1) — click to expand
#QuestionResolutionRef
7671aKeep "The Athlete Doctor™" branding on the card / brand pages?Retired per Matt (27 May 2026) — the athlete framing puts off non-athletic doctors. Removed everywhere.#7671

Acceptance Criteria ​

Strapline & SEO metadata ​

  • ✅ Browser tab title reads "PPP – The Professional Infrastructure for Doctors" (#7671)
  • ✅ SPA document.title matches the static <title> on route change (#7537)
  • ✅ The current strapline reads "AMC-Accredited CPD Home. Performance & Wellbeing. Build a living, lifelong CV — every case, course and reflection, captured as you work." across the home hero, the <meta name="description"> SEO/Google-search tag, the social-card og:description / twitter:description tags, and the OG-image generator (scripts/generate-og-image.mjs) (#8423)
  • ✅ Non-home routes (/faqs, /contact, /for-consultants, etc.) serve their own <title>/<meta name="description">/<link rel="canonical">/OG/Twitter tags in the raw, pre-JS-execution HTML — not the homepage's static defaults — via a Cloudflare Pages Function (functions/[[path]].ts) that rewrites index.html per-route ahead of useSeoMeta's client-side correction (#11690)

Social share card (Open Graph / Twitter) ​

  • ✅ og:description and twitter:description use the current strapline (#7671)
  • ✅ Retired "Whoop for the Workplace" copy removed from the card (#7671)
  • ✅ og-image.png uses the approved emblem-only mark, not the "PPP" circle (#7671)
  • ✅ OG image regenerated deterministically by a committed generator script (#7671)
  • ✅ "The Athlete Doctor™" branding retired across card + brand pages (#7671)

Responsive header / desktop nav ​

  • ✅ Desktop nav (incl. Login button) visible at viewports ≥ 1024 px (#7813)
  • ✅ Hamburger menu still collapses below the desktop-nav threshold (#7813)

Search indexing & AI-crawler policy ​

  • ✅ Only the production marketing host is indexable; UAT / preview hosts are kept out of search and AI answer-engine indexes (#7859)
  • ✅ Host-aware robots.txt Pages Function: production host serves Allow: / + Sitemap; any other host serves Disallow: / (replaces the static public/robots.txt, which could not differ per environment from a single build artifact)
  • ✅ Belt-and-braces on non-prod: a Cloudflare X-Robots-Tag: noindex response header plus a WAF block for known AI/answer-engine crawler user-agents (api/infra-cloudflare/src/{security-headers,bot-blocking}.ts)
  • ✅ ppp-dev is intentionally public (dev-tunnel access without OTP) and is therefore explicitly included in the non-prod noindex + crawler-block rules so the live dev app stays out of indexes (#7859)

CPD information pages ​

  • ✅ marketing.information.matches-source-documents-verbatim — the published /information policy pages and the /cpd-activities tables reproduce Kristin's July-2026 source documents verbatim, including the college references those documents name directly (RACS, ANZASM, ASERNIP-S, MALT, capitalised "College"). This AC previously asserted the opposite and is corrected rather than deleted, because the reversal is the governance record: it required those terms to be genericised (ANZASM surgical case form → Surgical mortality audit case form, and so on) on the reading that Matt's 29 April RACS/CAPE ruling covered them. Matt narrowed that ruling on the 2026-07-29 Dev Session call (#11025): it governs what PPP calls its own products and features — CAPE is the proprietary term he flagged — and college references in CPD activity materials are correct to carry ("they're references… we're happy to reference"). Because these are the pages AMC reads and the controlled source documents were never altered, genericising only the website had left the published page and the source PDF listing different claimable activities — the exact failure #11025 flagged as the reason not to fix this on the website alone. verify-policy-fidelity.mjs therefore carries no substitution map: it compares against the unmodified sources and all 13 policies score 100.0%, so the gate now proves the pages match the source rather than matching a tolerated divergence from it. The removed map's own comment anticipated exactly this state. Still true and still enforced: the scope is the whole of instances/marketing/src, not one directory (an earlier pass marked itself ✅ while MALT and capitalised "College" survived on the same pages — an AC falsifiable by grep), Info4.tsx and the other 8 unreferenced Info*.tsx files were deleted as part of #11058 (they were verifiably unimported — superseded by the July 2026 policy set, #11022), and proprietary product/feature naming such as CAPE stays out of PPP's own naming everywhere.†‡ (#11025)

  • ⚠️ KNOWN DIVERGENCE — decided (publish verbatim), not yet corrected at source. The /information policy pages do not list the four Program-Level Requirements in the canonical wording (Culturally Safe Practice / Addressing Health Inequities / Professionalism / Ethics, corrected by #12150 2026-09-01 — see cpd-home.md cpd.home.plr.canonical-label-consistency) consistently. The policy components are verbatim transcriptions of Kristin's July-2026 source PDFs, and those PDFs still use non-canonical wording — and disagree with each other: the PLR policy heads its sections "Culturally Safe Practice" (this one now happens to match the corrected canonical wording) and "Maintaining and Developing Ethical Practice", its own tables read "Maintaining Professionalism" and "Addressing Health inequities" (lower-case i) and a table cell "Ethical Practice", the auditing policy matches the tables, and the guidance policy uses the bare "Health Inequities" Matt rejected on #7525 plus "Ethics" in one place and "Culturally Safe Practice" in another. Rob decided this on #11024 (2026-07-27): publish verbatim. Rewording a controlled regulatory document that AMC was about to read — under deadline, without Kristin — was the larger risk. Engineering therefore does not reword these components; the fix belongs in the source PDFs. Still outstanding, re-tracked by #12150 (2026-09-01): #12150's own Google Drive check (2026-09-01) confirmed both copies of the July-2026 PDF are still uncorrected — no hidden already-fixed version exists — so the divergence remains live on the site (30 occurrences across four policy components), now measured against the corrected canonical wording rather than the previous one. What #12150 changed: the canonical constant (PLR_CANONICAL_NAMES) and every in-app consumer were corrected to AMC's actual published wording per Matt's 2026-09-01 direction, which reversed the earlier "Cultural Safety" / "Ethical Practice" wording (itself sourced from #7525/#6369). The marketing pages were deliberately left untouched by #12150, both because Rob's verbatim-publish decision still stands and because rewording them would fail scripts/verify-policy-fidelity.mjs, which checks components against the source PDF text, not against PLR_CANONICAL_NAMES — a mismatch there is a real regression, not a false positive. Harmonising stays cheap by design — the components are transcriptions verified by that script, so a corrected PDF means a re-transcribe and a gate re-run, not a rewrite. This criterion returns to ✅ when corrected PDFs arrive and are re-transcribed. † † † ‡

  • ✅ marketing.information.no-stale-policy-content — the retired pre-July-2026 Review and Appeal policy component Info2.tsx is deleted rather than left unimported: it carried the superseded $165 (incl. GST) appeal fee, and stale-but-present policy content is a drift hazard for exactly the figure class the July-2026 policy set (and verify-policy-fidelity.mjs) governs. The live /information Review and Appeal page renders the July-2026 policy with the $600 AUD (ex GST) appeal fee. (#11034) ‡

Home page — two-product distinction ​

  • ✅ The home hero presents the two offerings as two distinct products in side-by-side cards, each with a large product heading ("CPD Home" / "PPP Full Platform") rendered as an <h2> so they read as separate products, not one blurred offer (#7904). † ‡
  • ✅ As of #9892, each card's image is a genuine screenshot of the real app, replacing the blurred placeholders (home-app-preview-4/5-blurred.png). Both cards reuse the same real screenshots as the "See it in action" section (preview-cpd-home.png — CPD Home dashboard; preview-ppp-full.png — Surgical Logbook) rather than sourcing distinct images — an initial attempt at distinct screens picked the wrong content (a CPD Plan sub-page instead of CPD Home; an onboarding checklist instead of real platform content), so Rob asked to just reuse the already-vetted preview images. † ‡
  • ✅ Each product card is a semantic, keyboard-operable button with a visible focus ring; clicking it scrolls to that product's pricing tile (CPD → cpd-pricing, PPP → ppp-pricing-tile) (#7904).
  • ✅ The CPD Home card's one-line description reads "Providing you with support and guidance to achieve your yearly CPD requirements." and the PPP Full Platform card's reads "Providing you with a collegiate performance platform to drive performance, coach well-being, and seamlessly fulfil regulatory requirements." (#7904).

Home page — product terminology alignment ​

  • ✅ The full product is named "PPP Full Platform" on every customer-facing surface of the landing page — the hero product card heading, the plans & pricing tile, and the login-gated sign-up CTA ("Sign up for the PPP Full Platform") — matching the in-app canonical name; the bare "PPP Platform" wording no longer appears anywhere on the page (#7903). † ‡
  • ✅ The PPP Full Platform inclusion list surfaces the Passport feature by its user-facing description ("Recruitment Compliance Passport"), not the internal "PPP Passport" name (#7903). † ‡

Home page — pricing inclusion ordering ​

  • ✅ Each pricing card's feature/inclusion list (CPD_HOME_INCLUSIONS, PPP_FULL_PLATFORM_INCLUSIONS) renders in a deliberate order: items universally relevant to all doctors (e.g. live tracking, deadline reminders, GeoSmart timesheets) appear high, and person-specific or niche items (e.g. specialist high-level requirements, supported feedback models) appear lower. This is a copy-only sequence change — no inclusion text, pricing, plan structure, or CTA is altered. The final rank is editorial and may be re-ranked by Matt as a non-blocking fast-follow (#7906). † ‡
  • ✅ The PPP Full Platform inclusion list always keeps "All CPD Home features included" as its first item (#7906).
  • ✅ The "Recruitment Compliance Passport" bullet sits immediately after "All CPD Home features included" in the PPP Full Platform list, ahead of GeoSmart timesheets. This is the order shipped since Matt's website-review copy rewrite (#10154); the #7906 regression test asserted a pre-#10154 sequence that omitted the Passport bullet entirely and had been failing silently ever since, because no CI job ran the suite until #11310. The expectation was aligned to the shipped page rather than the page reordered to the stale expectation — the rank is editorial and Matt's to set. † ‡

Home page — per-feature plain-English explanations ​

  • ✅ Jargon-heavy and named features in both pricing inclusion lists carry a concise plain-English description rendered as secondary text beneath each item. The items with descriptions include: "GeoSmart timesheets" (location-aware auto-detection), "Two-step verification" (internal provider-confirmation process), "Increased awareness. Superior performance." (wellness + workplace analytics combined), "Audit ready" (AHPRA audit readiness), "CPD plan proformas" (ready-to-use templates matched to career stage/speciality), "Supports specialist high-level requirements" (AMC/AHPRA/specialist college coverage), "Recruitment Compliance Passport" (shareable credentials document), "Real-time CV", "PPP Pulse wellness tracker", "CPD scoring for in-platform interactions", "Digitally interactive with colleagues", "FHIR-enabled logbook", and "Psychologically proven supported feedback models" (#7905). As of #10135, "Live tracking", "Deadline reminders", "Exportable reports", "3-year information storage", "Support and guidance", and "All CPD Home features included" also carry short descriptions from Matt's website copy review. Engineering drafts the copy from the specs — Matt approves wording before go-live. † † ‡

Home page — career-long value proposition ​

  • ✅ The home hero foregrounds the career-long value proposition with the lead-in copy "One platform that can carry you along your entire medical career", rendered as small text above the "Professional Performance Portfolio" <h1> and kept within the navy hero band (#7907). As of the #9892 redesign this lives in ImmersiveHero's kicker rather than the old HeroSection — placement and wording unchanged. † ‡

Home page — doctor-value-first copy refresh (#8307) ​

Copy below is engineering's faithful rendering of Matt's Google Doc (retrieved 24 Jun 2026). Matt approves the final wording before go-live — the rendered copy may be re-worded without changing the structure.

  • ✅ The white banner carries a doctor-value headline "Take Control of your professional existence" beneath the existing banner sub-text, plus two audience CTA buttons "For Consultants" / "For Non Consultants" that reveal the matching USP content inline beneath them (#8307; the original scroll-to-section mechanism was replaced by an inline roll-out as part of #9892 — see "navigation flow" below). † ‡
  • ⚠️ The navy hero tagline block previously reframed around doctor value — "Life-Long CV Builder", "Real. In-Time. Accurate.", "The Digital Infrastructure Doctors Deserve.", the existing strapline, the italic "We collect your day-to-day..." paragraph, and "Giving power back to doctors..." (#8307). As of the #9892 redesign this stack is condensed into ImmersiveHero's single subtext line ("By Doctors, For Doctors — CPD, Logbook and Wellness, together with feedback, appraisals and more, all captured as you work.") as a deliberate part of the wow-factor rework — see the marketing Change Log. The social-card strapline remains verbatim in index.html meta tags (#7671/#7379); it is no longer duplicated in the visible hero body. † † ‡
  • ✅ A "For Consultants" USP section ("You're busy. Let us take away your painstaking admin.") lists the consultant benefits: living REAL CV, CPD scoring for supervision/education, lifelong log at a click, decreased duplication via junior auto-logging, portfolio transfer between jobs (local + international), and CPD/Appraisals/Logbook together; it links to the Features section (#8307). † ‡
  • ✅ A "For Non-Consultants" USP section ("Making professionalism easy.") lists: independent digital infrastructure for logging qualifications/experience, Timesheet/AVAC automation with smart Geotag + audit, digital Workplace Assessment approval, PGY1/PGY2 AMC National Provocation Pathway, local Training Pathway upload, digital consultant feedback, keyless logbook entry, and overseas/sabbatical portability; it links to the Features section (#8307). † ‡
  • ✅ A "Features" section lists the platform capabilities from the Doc: PPP Dashboard, Roadmap, CPD Home (AMC accredited), PPP Pulse (Wellness — proprietary doctor-specific algorithm, wearable-connected), Logbook (photo-upload, FHIR + SNOMED CT, multi-account linking), PPP Passport, Feedback (two-way, psychologically safe), Reflection, Audit Log (GIRFT-aligned), Work Based Assessments, Appraisals, Timesheets (Smart GeoTag auto-timesheet with paid-correctly audit), and Attendance (verified CPD recognition for workplace meetings) (#8307; Timesheets and Attendance restored by #11308). † ‡
  • ✅ Net-new user-specific USP screens/routes ship as dedicated, indexable marketing pages — /for-consultants and /for-non-consultants — reusing the exact benefit copy the home-page banner buttons reveal inline (single source in data/usp.ts) and the shared #9892 glass primitives (GlassSection/SectionHeading/GlassCard/PillButton, no new brand primitive), with per-route SEO metadata via useSeoMeta and both routes registered in the sitemap. The home-page buttons keep the inline Collapse roll-out AND now carry a prominent "See the full page" deep-link to the matching standalone route (a hybrid that preserves the #9892 inline-engagement work); the authenticated app is untouched (#8307, #10436; direction ratified by Matt — "dedicated page for USPs" — and Rob 2026-07-17 — "dedicated, indexable routes… authed app untouched"). † ‡

Home page — iOS-glass immersive hero redesign (#9892) ​

  • ✅ The home hero (ImmersiveHero) uses a bold Nunito <h1> (the site's brand typeface — see "Fraunces reverted" below), an asymmetric two-tone atmosphere with a film-grain texture, a staged word-by-word load-in reveal, and scroll-linked parallax/exit motion (panels translate and fade out as the section scrolls past) via framer-motion (#9892). † ‡
  • ⚠️ Reversed by #11806: product-screen artwork in the hero previously used an abstracted, Gemini-generated glass-dashboard fragment (gemini-2.5-flash-image, called directly via the Generative Language API) rather than a literal app screenshot, balancing "prove the product is real" against the product owner's competitor-cloning concern (#9892). Matt and Brooke's direct feedback on the live site was that this artwork read as "AI" rather than as the actual platform. The hero now shows real captured CPD Home screenshots (/cpd-dashboard) inside literal iPad + phone device chrome — the same real-screenshot-in-DeviceFrame-chrome pattern already established for the "Works everywhere you do" section below (#9892) — via a new DeviceFrame 'tablet' variant. The screenshots were polished (scrollbar/edge cleanup only, no invented UI content) but are otherwise faithful captures, not generated imagery. † † ‡
  • ✅ Every product screenshot on the site is captured from an account whose entitlement matches the copy beside it, and is regenerated by a script rather than by hand (#12035). The three CPD Home assets (devices/ipad-cpd-home.png, devices/mobile-cpd-home.png, preview-cpd-home.png) are captured as the seeded CPD-only member (test-cpd@ppp-test.com) and therefore show the CPD-only sidebar — no Logbook / Wellness / PPP Passport — and a first-name-only greeting per #11992; preview-ppp-full.png is captured as the full-PPP member (test-full@ppp-test.com), where the full sidebar is correct because that asset is sold as the full platform. The prior artwork was captured from a full-platform account and shipped "Welcome Back, Priya Patel" with the whole platform menu beneath CPD-Home-only copy. scripts/capture-product-screenshots.mjs asserts both properties at capture time (it refuses to write a CPD Home asset showing PPP-only nav, or a full-name greeting), and an @regression spec asserts the deployed bytes match the committed capture so a stale asset cannot silently ship. † ‡
  • ✅ Shared glass primitives (GlassPanel, GlassCard, useScrollReveal) and design tokens (themes/glass.ts) back the hero so the same visual language can extend to other marketing pages without re-deriving rgba()/backdropFilter values per component. † ‡
  • ✅ A small overlapping avatar cluster of 4 AI-generated (gemini-2.5-flash-image) doctor portraits — spanning a diverse range of race/ethnicity, not real people, in navy scrubs (Australian clinical style, not white coats) — sits below the hero CTA with the copy "Designed with doctors across every specialty" as a social-proof signal, restyled from BdHealth's light-teal "available doctors" pattern into the site's dark navy palette. Copy is an engineering placeholder pending Matt's sign-off, per the site's established review pattern; no unverified statistics are claimed. † † ‡
  • ✅ The hero subtext names CPD, Logbook, and Wellness explicitly ("CPD, Logbook and Wellness, together with feedback, appraisals and more, all captured as you work"), so the platform's breadth reads clearly rather than foregrounding any single feature (e.g. CV-building) as the headline message (#9892). † ‡

Home page — functionality preview (#7908) ​

  • ✅ A "See it in action" section appears on the home page (between the Features and Problem sections) with a tabbed screenshot preview, so prospective users can visualise the product before full walkthrough videos exist (#7908). † ‡
  • ✅ The preview section has two tabs: "CPD Home" and "PPP Full Platform", each with three feature highlight bullets (#7908). As of #9892, both tabs show genuine screenshots of the real running app (preview-cpd-home.png — CPD Home dashboard; preview-ppp-full.png — Surgical Logbook) — the originals (home-app-preview-cpd.webp/-ppp.webp) were discovered to be mislabeled generic UI-kit template mockups, not actual PPP screens. † † ‡
  • ✅ Each screenshot is presented inside GlassScreenFrame — a dark glass panel with scroll-linked 3D perspective tilt (rotateX from 10° to 0° to -10° as the section scrolls through the viewport) and an ambient brand-blue glow — replacing the previous flat white card on a plain shadow (#9892). † ‡
  • ✅ A subtitle reads "A first look at the platform — full walkthrough videos are on the way." to set expectations while videos are pending (#7908).

Home page — "Works everywhere you do" cross-platform section (#9892) ​

  • ✅ A new section (between "See it in action" and the Problem section) makes the desktop/mobile/wearable cross-platform message explicit — previously missing from the redesigned page. Three columns, static (not a carousel — only 3 device categories, so all stay visible without requiring interaction): Desktop browser and Mobile app each show a real screenshot inside a literal DeviceFrame (browser window chrome / phone notch+bezel). † ‡
  • ✅ As of #10119, Wearables shows a single CSS/SVG smartwatch mockup (DeviceFrame's watch variant — case, strap lugs, and crown, built entirely from existing GLASS/COLORS design tokens, no new image asset) with a mocked-up push notification ("You're checked in — PPP Pulse"), replacing the earlier abstract Gemini-generated wristband+ring visual — Matt felt the device-array illustration read as "too futuristic/corporate" and asked for a single watch showing a simulated check-in notification instead. Whoop/Oura remain data sources that sync into PPP Pulse rather than platforms PPP renders a native screen on, so the copy still says "sync automatically into PPP Pulse." † ‡
  • ✅ As of #11810, the watch mockup's simulated notification also shows the PPP emblem (reuses the existing ppp-emblem-v1.svg brand mark already used for the pricing card icons on this page, at 20×20 — no new brand asset introduced) alongside the check-in confirmation icon — supersedes the "no new image asset" framing of the #10119 AC above for this one element; the watch case/strap/crown remain pure CSS/SVG tokens as before. † ‡

Home page — motion polish and site-wide font baseline (#9892) ​

  • ✅ CssBaseline is rendered inside the marketing ThemeProvider, so <body> (and any element not wrapped in a MUI Typography, e.g. the nav bar) defaults to the brand's Nunito instead of the browser's serif fallback. Discovered auditing font usage for the #9892 redesign: the nav bar was rendering in Times New Roman. † ‡
  • ✅ The 4 stats in "Bridging the unmet need in medical training" (52.3%, 1 in 4, 78.82%, >50%) roll up from 0 to their real value on scroll-into-view via CountUpNumber, rather than rendering statically (#9892). † ‡
  • ✅ As of #11832, the same panel gained 2 more CountUpNumber stat boxes on genuinely-measured training-outcome figures: 89% ("Rate the quality of their clinical supervision highly") and 83% ("Would recommend their current training program"), both cited to the Medical Board of Australia's 2025 Medical Training Survey via the same visible-caption source-attribution pattern as the existing Beyond Blue/MJA and QLD PHO boxes — panel is now 6 stats total. The original ask was for "competence and confidence" figures; the Medical Training Survey doesn't survey those two words directly, so Rob approved substituting the closest genuinely-measured, honestly-citable figures from the 2025 National Report (quality of clinical supervision; recommend current training) rather than stretching the source's actual findings to fit the literal ask. † ‡
  • ✅ The Features section (13 items) is a dual-row infinite glass marquee (FeatureMarquee) — each row auto-scrolls, opposite directions, pausing on hover — on a dark navy background matching the hero/preview sections, replacing the previous static white grid (#9892). Originally 11 items; Timesheets (Smart GeoTag builds the timesheet, user adjusts/submits, paid-correctly audit trail) and Attendance (log in to workplace meetings such as M&Ms/MDTs for verified CPD recognition) were restored from Matt's Website-updates brief, whose Features list has 13 entries (#11308). Rows split evenly from the array length, each feature rendered exactly once across the two rows. † † ‡
  • ✅ The "For Consultants" and "For Non-Consultants" USP content expands via an MUI Collapse transition when its trigger button is selected, replacing the previous always-visible sections. Copy and layout unchanged (#9892; superseded by the inline roll-out mechanism documented under "navigation flow" below — the benefit lists themselves are not individually staggered). † ‡

Home page — flow and brand-consistency pass (#9892) ​

Rob requested a critical review of the redesign's flow and brand consistency; every finding was fixed in the same pass.

  • ✅ "From controlled chaos to clarity" restyled from the pre-redesign light-purple gradient cards to dark glass (GlassCard + scroll stagger) — it had been the one section left visually inconsistent with the rest of the redesign. "Our values" (kept light/white, appropriate for the cultural-acknowledgement content) and "Guiding principles" (upgraded to GlassCard) gained scroll motion; Plans & Pricing gained a light-touch scroll reveal + bold heading without touching PlanCard's pricing/Stripe logic. † ‡
  • ✅ A shared PillButton component (primary/solid/outline tones) replaces every bespoke or plain-MUI CTA on the page ("Explore the features", "View all news", "Sign up", "Get started") with one consistent button language, instead of the hero's bespoke pill button plus assorted MUI defaults elsewhere. † ‡
  • ⚠️ Reverted: an earlier pass in this redesign introduced the Fraunces serif display font across every major section headline as "a coherent typographic system". Fraunces was never an approved brand asset — docs/features/design-system.md names Nunito as the sole brand typeface (design-system.brand.no-urbanist-override) with no exception for marketing. Rob flagged it wasn't brand-kit-approved; on review the decision was to revert entirely rather than seek retroactive sign-off. Every heading (ImmersiveHero <h1>, SectionHeading, CommonSectionHeading, and all inline section headings in Home.tsx) is back to Nunito at a bolder weight (600–800) to keep the visual weight the redesign relied on. The Google Fonts <link> for Fraunces was removed from index.html. † ‡
  • ✅ "Take Control of your professional existence" (#8307) is demoted from a competing h3/h4 headline to a supporting h5/h6 statement, so it reads as a continuation of the ImmersiveHero above rather than a second hero. Wording unchanged. † ‡
  • ✅ The hero CTA is now always visible: falls back to "Join the Waitlist" (wording unified by #10122; the same scrollToSection(SECTIONS.contact) action the header uses) when ppp-login-enabled is off, instead of rendering no call-to-action at all. † ‡
  • ✅ Page resequenced to a problem-first narrative arc: the Problem section and the "From Burnout to Breakthrough" solution bridge now sit immediately after the hero, before the product/feature tour — previously the crisis case arrived after a full feature pitch and the "solution" was presented twice. † ‡

Home page — navigation flow, hover interaction, SEO/AEO, and responsive fixes (#9892) ​

  • ✅ "For Consultants"/"For Non Consultants" no longer scroll-jump past the "Two products" pricing cards to a distant section — they roll out inline (MUI Collapse) directly beneath the buttons, swapping between panels, via a shared UspPanel body. † ‡
  • ✅ "Two products, one mission" is extracted into its own ProductCardsSection and moved to sit after Features — it was sandwiched inside HeroSection, exactly what the accordion buttons were jumping past. Rebuilt on the new GlassSection organism for correct dark-glass contrast. † ‡
  • ✅ First use of shared atomic-design primitives — GlassSection (dark-bg + glow + Container wrapper), SectionHeading (kicker + heading + subtext + reveal motion), GlassIconCard (icon + title + description card) — reducing the ~5x duplicated section-wrapper pattern to one definition, per Rob's ask for easier re-skinning. † ‡
  • ✅ In "Works everywhere you do", the desktop browser frame tilts in 3D on hover as if glanced at on a desk (top edge receding left); the phone frame turns in 3D as if being rotated in someone's hand. Both use a perspective wrapper so the 3D effect reads rather than a flat skew. † ‡
  • ✅ SEO/AEO pass: fixed a real semantic issue (the 4 crisis-stat numbers were wrapped in actual <h2> tags for visual size only, outranking the section's own <h3> in the document outline — now component="p"); added a canonical link; added static JSON-LD (Organization + SoftwareApplication × 2 with AUD pricing) for search crawlers and AI answer engines; added public/llms.txt, the emerging AEO convention providing a plain-markdown site summary for LLM crawlers. † ‡
  • ✅ Responsive audit across 5 breakpoints (375/390/768/1024/1440px) found and fixed a genuine horizontal-overflow bug present at every width: a stale margin: '0 -8px' on the root Box was compensating for the browser's default body { margin: 8px }, which the earlier CssBaseline fix (#9892) already resets to 0 — the negative margin was left over and became actively harmful. Zero overflow issues confirmed post-fix at all 5 breakpoints. † ‡

Home page — persistent waitlist CTA + waitlist-clear contact form (#10122) ​

  • ✅ A floating CTA "rolls with the user": once the hero (which carries its own always-visible CTA) scrolls out of view, a fixed pill CTA (FloatingCta, reusing PillButton) appears bottom-of-viewport and stays on screen as the user scrolls, so the primary action is never a full page-scroll away. It hides again while the waitlist/contact section is on screen. Pre-launch it reads "Join the Waitlist" and scrolls to the waitlist form; with ppp-login-enabled on it becomes the signup CTA, mirroring the header/hero gating. † ‡
  • ✅ Pre-launch (ppp-login-enabled off) the contact surface is unambiguous that submitting means joining the waitlist: the home contact-section heading reads "Join the Waitlist" (not the generic "Contact") with a clarifying line beneath; the form itself carries a waitlist notice, the submit button reads "Join the Waitlist" (not "Send"), and the home and /waitlist intro blurb reads "Leave your details and we'll be in touch on our pathway to launch!" and the green success banner reads "You've joined the wait list and locked in your launch day discount. We'll be in touch soon!" (both from waitlistCopy.ts, #12624). The /contact page hosts the same form, so it inherits the waitlist signal. With the flag on, all copy reverts to the plain contact form. † ‡
  • ✅ Waitlist CTA copy is unified to "Join the Waitlist" across the header, the hero CTA (previously "Join the waiting list"), and the floating CTA, matching Matt's wording. In the header that wording appears exactly once per viewport (#12036): pre-launch the header renders only the styled waitlist CTA (the desktop button / the drawer entry below the divider), and the Contact nav item — which #11962 had also relabelled "Join the Waitlist", because pre-launch /contact IS the waitlist form — is not rendered at all. It returns as "Contact Us" once ppp-login-enabled is on, the only state in which it is not a duplicate of the adjacent CTA. Matt's "pop out screen" idea is an Open Question (10122a) — the shipped default scrolls to the in-page form. † ‡
  • ✅ The header "Join the Waitlist" CTA reaches the waitlist form from every route, not just Home — on a non-Home page it navigates to Home and then scrolls to the contact/waitlist section once it has mounted; on Home it scrolls in place without navigating. This holds for both the desktop button and the mobile drawer entry. The shared useScrollToSection hook owns that guard, so scrollToSection — a deliberate silent no-op when its [data-section] target is absent — is no longer called directly by any component that can render outside Home. Previously the header CTA did nothing at all on /faqs, /information and every other non-Home page: no navigation, no error, no feedback. #11812 had fixed the identical defect in FloatingCta with an inline isHome guard but left the shared helper dangerous, so the header reinherited it; that inline guard is now folded into the hook rather than copied a third time (#12074). † ‡
  • ✅ Waitlist submissions are durably persisted, not email-only (#10588). Every validated "Join the Waitlist" signup is written to Cloudflare KV (PPP_WAITLIST) alongside the email notification (Azure Communication Services until #12154, Brevo since), so a missed/filtered email can no longer mean the signup is unrecoverable. The write is fail-open: a missing binding or KV error never blocks the email send or the form's 200 response. This tick described the code, not the deployed system, from #10613 until #11117 — the PPP_WAITLIST namespace was recorded as "a manual Cloudflare step post-merge" and never created, so persistWaitlistSignup took its if (!kv) return branch on every signup and nothing was ever persisted in any environment. It is true from the first marketing deploy carrying #11117, which creates and binds the namespace in CD; signups taken before that deploy exist only as sent emails and are not recoverable from KV. A gated admin endpoint (GET /api/waitlist/admin/list, bearer-token-protected via the same NEWS_ADMIN_TOKEN the news review gate uses) returns the signup count, unique-email count, and full list, or a ?format=csv export — the durable source of truth the original #10122 CTA/form work did not include. † ‡
  • ✅ The PPP_WAITLIST KV namespace is created and bound by CD on every marketing deploy, and the binding is verified by re-reading the Pages project rather than trusted from the PATCH's 2xx — it is no longer a manual dashboard step that can be forgotten. The same parameterised script (scripts/cf-ensure-pages-kv.sh) asserts PPP_NEWS, so a new binding is an argument list rather than a forked copy, and each invocation asserts that the sibling bindings it does not name survived its own write. † ‡
  • ✅ A waitlist write that does not happen now says so. The fail-open behaviour is deliberately unchanged — it protects the notification email, which is the primary path (ACS until #12154, Brevo since) — but both failure branches (PPP_WAITLIST absent, and a KV write that throws) emit a console.warn naming the binding, reachable via wrangler pages deployment tail. Signup PII is redacted from the logged error first, because this feature's KV key embeds the signup's email address and Cloudflare KV errors quote the key — and that redaction scrubs by construction (the exact key and serialised value this code handed to KV) rather than by substring-replacing field values in the rendered message, which a one-character name or the literal unknown sourcePage would otherwise shred into unreadability, destroying the very diagnostic this criterion exists to provide. The admin endpoint reports persistenceBound, so "we are storing nothing" is no longer byte-identical to "nobody has signed up", and a bearer-gated ?format=status projection returns that health signal plus the counts without the signup array, so an automated caller never pulls PII it has no use for. That projection derives its counts from key names only and never fetches a value, because the deploy-time smoke test calls it on every marketing deploy in both environments: a kv.get-per-record implementation would have made deploy success a function of waitlist size, failing the deploy of unrelated changes once the store outgrew the Workers subrequest cap. † ‡

CPD Activities page — brought on-brand (#9892) ​

  • ✅ /cpd-activities (CPD Activity and Specialist High-Level Requirements) is the first page outside Home brought onto the #9892 glass language: a GlassSection + SectionHeading hero (was a plain white h1 on the navy background with no motion) and PillButton for the Activities/Requirements toggle (was plain MUI contained/text buttons). The two reference tables (CPDActivitiesTable, RequirementsTable) sit in a rounded glass-tinted card wrapper. † ‡
  • ✅ CPDActivitiesTable (the "CPD Activities" tab) redesigned on brand tokens — Rob: "is that the best we can do?" after the initial pass left it untouched. Navy (COLORS.gray[800]) header ties into the hero instead of sitting under it as a plain white/gray legacy table; category tints now derive from COLORS.ppp.warning/primary/success (the brand palette) instead of raw #fcdec0/#e6f3ff/#e6fbe6 hex pastels; soft COLORS.gray[100] dividers and light zebra striping replace the black 1px-solid-everywhere grid; raw "x" marks became CheckCircleOutlineIcon in the matching category color, matching the checkmark language already used in UspPanel's benefit lists. Data values and the rowSpan/colSpan header structure are unchanged. RequirementsTable/CPDSpecialistAreas.tsx (the "Specialist High-Level Requirements" tab) was deliberately left out of scope — it's shared with the live logged-in app (instances/ppp/src/modules/cpd/specialist-areas/), which carries its own stricter design-system governance; restyling it belongs to that surface, not a marketing-only pass. † ‡
  • ✅ The CPD Activities table header (both header rows) freezes just below the fixed page nav as the page scrolls, and the page owns a single scroll bar — no nested/second scroll region. The header sticks against the page at top: HEADER_OFFSET_PX (the fixed nav height, 90px, plus the 36px UAT/staging banner when it is shown — composed once in constants.ts and shared with the page's own main-content offset; the second header row stacks at HEADER_OFFSET_PX + HEADER_ROW1_HEIGHT) rather than scrolling past the nav or tucking under the staging banner (#10144). For page-level sticky to engage, no ancestor between the header and the page may be a scroll container: the card wrapping the table must NOT establish its own scroll region (no bounded maxHeight/overflow), and CPDActivitiesTable's TableContainer forces overflow:'visible' at all widths. A per-breakpoint overflowX:'auto' at xs (tried first for the 650px-min-width table's mobile horizontal scroll) is itself a scroll container below md — the CSS overflow spec coerces the other axis away from 'visible' — so it re-trapped the sticky header on phones, scrolling it off the top (the #10120 bug back on mobile, #10144). With overflow:'visible' no ancestor scrolls, the header freezes against the page at every width, and on narrow viewports the 650px table falls back to the page's own horizontal scroll. This supersedes the earlier #9892 "docking panel" approach — a position:sticky Box with a bounded maxHeight+overflow:hidden wrapping a flex:1/minHeight:0 TableContainer scroll panel — which produced two scroll bars and stuck the header to the inner scrollport instead of the page (the overflowX:'auto' the panel needed for narrow viewports forced overflowY to a non-'visible' value per the CSS overflow spec, making the panel the sticky containing block). The hero is never sticky — it scrolls away in normal flow. The Specialist Requirements tab (shared, out-of-scope component) keeps its original non-constrained layout. † † † ‡
  • ✅ marketing.ac.cpd-activities-tables-match-published — Both reference tables on the public /cpd-activities page reproduce their published July-2026 policy documents rather than a paraphrase of them, because this page is what a prospective member (and AMC) reads to learn what PPP will let them claim. The CPD Activities tab carries the published 101 activities with their published category marks and hours (see cpd-home.md § cpd.home.activity-master-list-matches-published). The Specialist High-Level Requirements tab reproduces the published specialist table: each specialty named as published (Pain Specialist, not "Pain Medicine Specialist"), each requirement label verbatim including its mandatory frequency qualifier (e.g. "Emergency Response Activity (at least 1 per year)") since the frequency is the requirement, and the published two hours columns — "Per Hour of Activity" and "Per Activity" — kept separate rather than collapsed into one, so a value's meaning does not change row to row. Where the published table leaves a cell blank the page leaves it blank; no hours figure is supplied for the Emergency Medicine leadership requirement, the one row published with both hours cells empty, and its category mark stays under Performance Review (of self) because moving it changes which AHPRA category the requirement satisfies. The table renders exactly as many columns as its header declares. The in-app copy of this table (instances/ppp/src/modules/cpd/specialist-areas/) is held identical to the marketing copy by test, since a divergence between them is itself the defect. (#11057) † † † ‡
  • ✅ GlassSection gains a dense prop (half the vertical padding) for secondary-page title heroes, distinct from the full-size home-page section variant. CPD Activities' hero uses it — halving its height gets the user to the table faster. Information, News, and FAQs — previously three different treatments (Information: plain white h1 on footer-bg.svg, desktop-only, no hero at all on mobile; News/FAQs: plain centered heading on the light background, no dark hero) — are now on the exact same GlassSection(dense) + SectionHeading hero as CPD Activities, on every viewport, for a consistent look across all four secondary pages. † ‡

FAQs page — accordion header glass fade (#10121) ​

  • ✅ FAQ accordion question headers (AccordionSummary) pick up the same navy-tinted glass fade as the GlassSection(dense) hero above them — GLASS.surface.dark/border.dark at rest, GLASS.surface.darkHover when expanded — instead of flat white MUI-default blocks, the one remaining solid-color element on the page after the #9892 hero migration. Reuses the existing #9892 glass tokens; no new gradient/primitive introduced. † ‡

News admin review route (#10123) ​

  • The marketing router registers a token-gated /news-admin review-queue route alongside the public /news pages. The route's behaviour (AI-curated candidate approval before publish, pinning) is specified separately in marketing-news-automation.md; marketing.md owns only the shared route registration (landing/constants.ts, landing/index.tsx). †

Acknowledgement of Country (#11229) ​

Kristin (Cultural Advisor liaison) relayed Jesse at Cultural Wayfinder Pty Ltd's (PPP's Cultural Advisor) finalised website Acknowledgement of Country wording and a companion internal guide book. Placement: "a pop up when the user visits the first time, rather than every time, but should still be a visible navigation from the homepage if it sits elsewhere." Only the finalised wording (Sample A in the guide book) is public; the guide book's fuller content (five-step drafting approach, other sample wordings, do/don't guidance) is PPP's internal reference only and is never published to the docs site.

  • ✅ marketing.acknowledgement-of-country.text-matches-source-verbatim — the acknowledgement text rendered by the first-visit pop-up and the /acknowledgement-of-country page is byte-identical to Cultural Wayfinder Pty Ltd's finalised wording (Professional.Performance.Portfolio.Website.Acknowledgement.docx), held as a single exported constant so the two surfaces cannot drift apart. † ‡
  • ✅ marketing.acknowledgement-of-country.first-visit-popup — a dialog carrying the acknowledgement text opens once per visitor (gated by a ppp-acknowledgement-seen localStorage flag set on dismissal, not a per-session flag), mounted globally so it fires regardless of which page a visitor lands on first, and is dismissible via an explicit "Acknowledge" button (relabelled from "Got it" per Matt's website feedback, 2026-08-25 — #11805 item 2), a close icon, or the backdrop/Escape (all three set the flag). † † ‡
  • ✅ marketing.acknowledgement-of-country.permanent-footer-link — a permanent "Acknowledgement of Country" link renders in the site-wide Footer on every route (not homepage-only), pointing at the dedicated /acknowledgement-of-country page. The Home "Our values" tile (previously an unreviewed placeholder paraphrase — "We acknowledge the Traditional Custodians of the land and celebrate diversity across all communities we serve.", never checked by the Cultural Advisor) now links to the same page instead of restating a second, shorter paraphrase of approved wording. † ‡
  • ✅ marketing.acknowledgement-of-country.dedicated-page — /acknowledgement-of-country is a permanent, indexable route (registered in sitemap.xml) on the same GlassSection(dense) + SectionHeading secondary-page hero as CPD Activities/Information/News/FAQs, reusing the existing Aboriginal Australians and Torres Strait Islander flag assets already used on the Home "Our values" section (no new artwork — Kristin: Aboriginal artwork accompanying the text is "not a current priority"). † ‡
  • ✅ marketing.acknowledgement-of-country.guide-book-internal-only — Cultural Wayfinder Pty Ltd's companion guide book (five-step drafting approach, Samples B–E, do/don't guidance, tokenism guidance) is reproduced faithfully as PPP's internal reference, and lives entirely outside docs/site/ (the VitePress build's source root — .github/workflows/pages.yml runs vitepress build with working-directory: docs/site), so it is never served by the public docs site. The guide book's own Revision History restricts distribution: "Internal use: this guide is intended for PPP staff, the CPD Advisor and the Cultural Advisor. Distribution outside PPP requires the Cultural Advisor's agreement." † ‡

packages-shared/ppp/src/constants/pricing.ts (PLAN_PRICES) is the single source of truth for CPD Home / PPP Full Platform subscription pricing, already correctly consumed by the Home pricing cards, signup/payment flow, and backend Stripe checkout. #8069 identified that the EULA, Terms of Service, and Refund Policy pages still hardcoded the price/GST literal as prose and never shipped the fix (its Phase 2).

  • ✅ marketing.ac.legal-pages-pricing-single-source — the EULA (/eula), Terms of Service (/terms-of-service), and Subscription Refund Policy (/subscription-refund-policy) pages render subscription pricing via the shared <PlanPrice>/<PriceLabel> components (landing/components/pricing/), which read formatPrice()/getPriceLabel() from pricing.ts — no literal $299/$1,199 string remains in any of the three pages' source. A CI guard (.github/scripts/check-price-literals.mjs, wired into ci.yml's lint job) fails the build if a future edit reintroduces one. † ‡
  • ✅ marketing.ac.faqs-pricing-single-source — the FAQs page's "How much does it cost" answer composes its price figure from getPriceLabel(PLAN_PRICES.cpd[DEFAULT_CURRENCY].annual, DEFAULT_CURRENCY) rather than a literal string; since the answer text is plain JS (not JSX, feeding both the rendered accordion and the FAQPage JSON-LD), the price is computed once as a module constant and interpolated. † ‡

Markdown-only surfaces (the in-app Guide's .md content, other docs/features/*.md prose) are deliberately out of scope for #11801 — the issue targets .tsx render surfaces only, where a literal silently diverges from pricing.ts with no build-time signal. The in-app CPD Support "User Guide" modal (.tsx) is covered under cpd-support.md, which already documents its REVIEW_APPEAL_FEES single-source pattern; #11801 extended the same pattern to its CPD Home subscription-fee bullets.

Routed-content error resilience (#11959, defensive hardening) ​

/plans-and-pricing was reported rendering completely blank on UAT — 35/35 network requests 200, zero console output. Root cause could not be reproduced against HEAD (router config, PlansRedirect, and the pricing section all checked out clean; best evidence points at transient 2026-08-28 Cloudflare Pages deploy flakiness — #11959 stays open pending recurrence or confirmation). Independent of root cause, the investigation surfaced a real gap the issue's own "Ask" called out directly: a render error thrown by any routed page was previously swallowed with zero diagnostic trail, because nothing caught it before React's default uncaught-error unmount.

  • ✅ marketing.ac.routed-content-error-boundary — the marketing SPA's routed <Switch> content (not Header/Footer/StagingBanner, which stay outside it so site chrome still renders) is wrapped in a RouteErrorBoundary that catches a thrown render error via componentDidCatch, logs it (no longer silent), and renders a minimal on-brand fallback ("Something went wrong" + reload action, reusing COLORS + PillButton — no new brand primitives) instead of a blank page. The boundary resets on client-side navigation (keyed off the route pathname) so an error on one route does not permanently break navigation to a healthy route afterward. † ‡

Interactive-control destination audit (#11177) ​

Matt asked for a review of "the website elements and all buttons to confirm all working". Two prior passes reported no regressions having verified only content, SEO titles and copy — never clicking anything. A dead header CTA (#12074) was then found by hand on live UAT. The shared trap is scrollToSection (landing/constants.ts), a deliberate silent no-op when its [data-section] target is absent: every anchor but the hero exists only on Home, so any caller that runs off-Home — or before Home has mounted — does nothing at all, with no navigation, no error and no feedback.

  • ✅ marketing.ac.plans-route-reaches-pricing — /plans-and-pricing reliably lands with the pricing section parked below the fixed header. PlansRedirect previously fired one scrollToSection behind a fixed 100ms setTimeout, which raced <Home /> mounting: measured against the pre-fix build under 6x CPU throttling the scroll was lost on 2 of 3 runs (scrollY stayed 0 with the section present in the DOM), while a fast machine always passed — which is why it shipped. A fixed delay is wrong in both directions here, because Home's layout keeps settling afterwards (the News section above pricing renders, then collapses to null once its async fetch resolves with no articles, removing several thousand px), so a one-shot scroll lands short. The route now re-aims on each animation frame until the section's offset holds still, then stops. † ‡
  • ✅ marketing.ac.cta-destination-coverage — the primary marketing controls are covered by assertions on the DESTINATION each one reaches, never on mere visibility: the hero waitlist CTA reaches the contact form, both product cards reach their matching pricing tile, "Explore the features" navigates to /features (it scrolled the home page until #12137), and every footer nav/legal link resolves to its own route rather than falling through the router's catch-all <Redirect to="/">. "It's visible" is precisely the assertion that let a dead conversion button ship, so it is deliberately not used as a proxy for "it works". † ‡

Website walkthrough fixes — Matt's 2026-09-01 call (#12136, #12137, #12138, #12139, #12142, #12143, #12145) ​

Matt walked the live site top-to-bottom with Rob screen-sharing. These are the discrete content, layout and asset fixes he called out, plus the two pages he asked for.

  • ✅ marketing.ac.hero-real-device-hardware — the hero shows a laptop and a phone, both photorealistic, each displaying the real captured CPD Home dashboard with the whole screen visible. The previous iPad mockup cropped the dashboard (objectFit: 'cover' at 3/4), which is what Matt objected to. The device shells are AI-generated (gemini-2.5-flash-image, the same tool as the doctor portraits) and composited with the real Playwright capture by scripts/composite-device-shells.mjs — the shell is generated, the screen content never is, because an AI-invented dashboard would be a fabricated product screenshot. The #10118 regression guarding this surface asserted height > width as a proxy for "device-shaped"; a laptop is landscape by definition, so that proxy is replaced by assertions on the actual requirement (two devices present, phone portrait, laptop landscape but bounded below card-flatness, both decoding real pixels). † ‡
  • ✅ marketing.ac.surgeon-no-stethoscope — the third "designed with doctors" avatar shows a surgeon in scrubs and cap without a stethoscope. Same person, scrubs, cap, pose and lighting otherwise. † ‡
  • ✅ marketing.ac.hero-amc-accreditation-linked — the hero social-proof cluster leads with the AMC credential above the "Designed with doctors across every specialty" strapline, showing the AMC mark alongside the wording, and the whole credential is one link to PPP's row on the AMC CPD Home register. The mark sits on a white chip because the asset's ink (#2D3E50) against the hero background (#151D28) is ~1.5:1 — unreadable placed bare, and the DOM reports it as loaded, so only a rendered screenshot catches it. Wording is "AMC-accredited CPD Home", matching every other surface making that claim rather than introducing a per-component variant of a regulatory statement; PPP appears on the register with status "Initial accreditation" (verified live, 2026-09-01). † ‡
  • ✅ marketing.ac.amc-link-deep-links-to-ppp-row — every AMC link deep-links to PPP's own row on the register, centred in the viewport, rather than landing at the top of the page. The register's table row carries no id or named anchor, so there is nothing on AMC's side to target; a URL text fragment (#:~:text=) resolves against the rendered text instead. Verified live at 1440px and 375px against a negative control: without the fragment the row sits ~5400px below the fold at scrollY 0; with it the browser scrolls and centres it. Degrades to today's behaviour — landing at the top of the register — if unsupported or if AMC edits the wording, never a broken link. A previous "done" claim on this was never verified and did not work. † ‡
  • ✅ marketing.ac.audience-toggle-defaults-non-consultant — the "Protecting and elevating doctors" audience toggle opens on For Non Consultants, and PGY1/PGY2 AMC National Provocation Pathway is the first item in that panel's benefit list. The default reverses Matt's earlier 2026-08-25 direction ("Default to Consultant button open"); both are deliberate product decisions, recorded at the useState so the reversal reads as intentional rather than drift. † ‡
  • ✅ marketing.ac.watch-face-check-in-only — the watch mockup shows the geotag check-in confirmation only; "PPP Pulse" is removed from the watch face, while the surrounding body copy referencing Pulse is retained. The two are different things and showing both on one face read as confused. † ‡
  • ✅ marketing.ac.contact-page-reads-as-contact — /contact is framed as the contact page rather than "Join the Waitlist". #11962 had relabelled the whole page because the form beneath it was the waitlist signup and the heading promised support the site could not yet deliver; that issue offered two fixes and this takes the other one. Only the page framing changes: ContactForm's waitlistMode gate is untouched, so pre-launch the notice, submit label and analytics form_name still say submitting joins the waitlist. The honesty requirement #11962 protected now rides on the form rather than the heading. † ‡
  • ✅ marketing.ac.features-page — "Explore the features" navigates to a dedicated /features page, and clicking any feature card in the home-page Features marquee lands on it with that feature selected (/features#<slug>) instead of opening a popup. The page is one screen: all 13 features listed at once (a vertical list beside the explanation on desktop) and the selected feature's explanation — title, one-line summary and full long-form detail copy — shown in place. Choosing another feature swaps the explanation without scrolling the page or leaving it; the URL hash follows the selection, so back/forward and shared links work. Rendered from src/data/features.ts, the same source the marquee cards read, so a card and its explanation cannot disagree. On phones the list becomes a horizontally scrolling strip below the explanation, sticky to the bottom of the screen (clear of the floating waitlist pill) where the thumb is, and centres the selected feature. Reworked 2026-09-23 (#12418): #12137 first shipped this page as the two pricing-tier inclusion lists (CPD_HOME_INCLUSIONS / PPP_FULL_PLATFORM_INCLUSIONS), which Matt rejected on seeing it live as "more selling points"; those tier lists remain on the home page's pricing cards only. A first rework stacked 13 panels down one long page — rejected by Rob as not user friendly, and not what Matt described. † † † ‡
  • ✅ marketing.ac.admin-separate-from-app-admin (#12424) — the marketing site's admin (news review at /news-admin, the waitlist list) is a separate, self-contained surface from the PPP app's admin console: no shared runtime, no imports from instances/ppp/ or api/backend-*, its own Cloudflare Access + token gate, and data in Cloudflare KV. The boundary is written down in docs/site/architecture/bounded-contexts.md ("The marketing site — and its admin — sit outside the context model") with the canonical terms Marketing admin and PPP admin console. Rob raised it as a worry that the admin had been built in the wrong place; the conclusion was that it is right, because the PPP app is not in production and the marketing site must be fully autonomous of it. Whether the two ever converge after the app launches is not decided. No automated guard enforces the no-import rule yet — checked by grep on 2026-09-23. † ‡
  • ✅ marketing.ac.secondary-pages-one-h1 (#11177) — every secondary page has exactly one <h1>, and it is the page's title: Features, CPD Activities, Information, FAQs, News, For Consultants, For Non-Consultants and Acknowledgement of Country. Found by the #11177 click-through audit (a 22-route crawl at 1440px and 375px): those pages opened with an <h3> and had no h1, because SectionHeading always rendered an h3 — correct for the repeated section headings on the home page, wrong for a page title. SectionHeading gains an optional as prop (default unchanged, h3); page titles pass as="h1". Visual size is unaffected (the typography variant is separate from the element). The same crawl found no console errors, failed requests, broken images or dead internal links; two 17–18px overflows on /acceptable-use-policy and /accessibility at 375px did not reproduce on inspection and are not recorded as defects. The /cpd-activities horizontal scroll at 375px is by design (the page owns the single scroll bar for its wide table). † ‡
  • ✅ marketing.ac.features-in-nav (#12418) — Features is a link in the site header (desktop nav and mobile menu, straight after About Us) and in the footer nav, each reaching /features. The homepage's "Explore the features" CTA and the marquee cards were the only routes to the page before, so it was undiscoverable from any other page. Verified the desktop nav still fits at 1080px and 1024px alongside the extra item. Source is Rob's recollection, not a cited Matt quote: Rob, 2026-09-23: "I think Matt asked for the Nav at the top to include Features and the Nav in the footer". A search of the 2026-09-22 call notes/transcript extract and Matt's WhatsApp thread found no such request, so this is recorded as Rob's direction pending Matt's confirmation, not as a transcript-backed requirement. † ‡
  • ✅ marketing.ac.features-page-tier-screenshots — /features carries a small "See it in action" strip with one screenshot per tier, taken from the audited pair in capture-product-screenshots.mjs' ACCOUNT/ASSET CONTRACT table: CPD Home shows preview-cpd-home.png (captured from a CPD-only account, guarded by assertCpdOnlyNav), Full Platform shows preview-ppp-full.png. Matt's explicit nice-to-have ("maybe a screenshot of each if that's easy enough") is satisfied at tier granularity rather than per feature — no per-feature asset set exists, and inventing one would mean shipping unaudited captures, the exact harm #12138 exists to prevent. Retained through the #12418 rework (the page is now feature explanations rather than tier lists; the strip is illustration only). The presentation reuses the existing GlassScreenFrame primitive, so no new visual primitive is introduced (brand guardrail). The e2e assertion is on the src each data-tier-screenshot wrapper renders, not on "the page contains two images" — the latter is equally true of a page with the pair swapped, so it cannot tell the bug from the fix — and additionally on naturalWidth > 0, since a mistyped path still yields a present <img>. † † ‡
  • ✅ marketing.ac.features-page-in-sitemap — /features appears in the generated sitemap.xml. The page shipped with a canonical URL via useSeoMeta, i.e. built to be indexed, but was never added to generate-sitemap.mjs' route list, so the one page that answers "what do I get?" per tier was undiscoverable to crawlers except by following a home-page CTA. Listed at 0.8, the same priority as the /for-consultants and /for-non-consultants tier-explainer pages it sits alongside. † ‡
  • ✅ marketing.ac.standalone-waitlist-page — /waitlist renders the waitlist form directly, for use as a single Instagram/LinkedIn bio link with no homepage scroll. It renders the same <ContactForm /> as the home page's waitlist section and /contact — not a copy — so identical fields (#11996) and a single submission destination (#12144) are structural rather than a convention someone must remember to keep in step. The home page's scroll-through journey is deliberately unchanged for visitors already on the site. Matt raised this three times on WhatsApp before a ticket existed. † ‡
  • ✅ marketing.ac.screenshots-captured-from-uat — every product screenshot is captured from UAT, not a local dev server, so no dev-server indicator badge, debug affordance or localhost-only data reaches the public site. The capture script's own prerequisites previously instructed the next person to run a local standup — which is how the badge shipped — and now document the UAT invocation. The script also clears the first-run furniture (the "Getting Started" checklist and the profile-completion banner) that otherwise buries the dashboard the screenshot exists to show: the checklist is dismissed through its own labelled control, and the profile-completion banner — which lost its dismiss control entirely in #12667 (onboarding-checklist.profile-banner-no-dismiss) — is kept off the capture by the two capture accounts (test-cpd, test-full) having genuinely complete profiles, seeded via jobContractStartDate in seedTestAccounts.ts. † ‡
  • ✅ marketing.ac.screenshot-tier-inventory — the asset→tier→account mapping is recorded in capture-product-screenshots.mjs as a table (asset, tier claimed, account captured from, route, surface), covering the derived composited assets as well as the raw captures, so the check is repeatable rather than a one-off audit. Enforcement is in-script: assertCpdOnlyNav throws if full-platform nav leaks into an asset sold as CPD Home, and pairs that absence check with a positive "CPD Home is present" assertion so it cannot pass vacuously against a nav that failed to render. † ‡
  • ✅ marketing.ac.pricing-cards-read-as-a-pair — the two plan cards on the home page read as a pair to compare, not two panels at opposite edges of the screen. The page gutters were never the problem (24px); the channel between the cards was — at maxWidth="xl" two 480px cards sat ~230px apart, spanning 97% of a 1440px viewport and 78% at 1920px. The Container is constrained to 1200px and the card widened to 560px together: this deliberately reverses design review #11811, which rejected 560px because a wider card made the pre-existing feature-count mismatch (CPD Home lists 10, Full Platform 12 longer ones) more visible as dead space. That finding held while the Container stayed xl — widening only the card left the same short list in a taller void. Changing both inverts it, because a wider card wraps each description in fewer lines and so shortens the LONGER card toward the shorter one. Measured at 1440px: dead gap 291px → 208px, section height 1437px → 1291px, inter-card gap 230px → 28px, and the pair holds its shape at 1920px (60% of viewport) rather than sprawling. Neither value works without the other. † ‡
  • ✅ marketing.ac.amc-accredited-leads-cpd-home-tile — "AMC-accredited CPD Home facility" is the first inclusion listed in the CPD Home tile, so the accreditation is the first thing a prospective member reads about that plan rather than being buried mid-list. It renders from CPD_HOME_INCLUSIONS[0] in src/data/planTiers.ts, the single source for the home page's pricing cards. (It was previously shared with /features, which stopped rendering the tier lists in #12418 — the AMC-first ordering now applies to the pricing tile only.) The Full Platform tile carries the same claim as a description on its "All CPD Home features included" row, so neither tier's accreditation status is ambiguous. † ‡
  • ✅ marketing.ac.hero-shows-real-product — the homepage hero shows real captured product screens, not a generic placeholder graphic. The previous hero-dashboard-fragment.png was an abstract "glass card" mockup — skeleton bars and a signal icon, no readable text, nothing tying it to CPD tracking, logbook or wellness — and it was the first visual a prospective member saw. It is replaced by the laptop and phone devices, whose screen content is a genuine Playwright capture of the CPD Home dashboard from UAT; only the device shell is generated. The orphaned placeholder asset is deleted rather than left in public/, so it cannot be silently reintroduced. † ‡
  • ✅ marketing.ac.news-rss-discovery — news discovery runs from RSS feeds via src/data/rssDiscovery.ts, implementing the DiscoverySource interface in src/data/newsAutomation.ts. Governed in detail by marketing-news-automation.md (marketing.news-automation.rss-discovery-adapter) — recorded here because the module lives under instances/marketing/src/data/. Discovery produces pending candidates only; nothing reaches the public News page without an explicit approval. † ‡
  • ✅ marketing.ac.waitlist-brevo-subscription — a validated waitlist signup is added to Brevo as a marketing contact, so Matt can design mailings and funnels against a live list. Brevo was chosen (Rob + Matt, 2026-09-01) because it is the only platform meeting all four requirements: a genuinely free tier (300 emails/day, up to 100k stored contacts), automation/funnels included on that free tier (capped at 2,000 contacts), an official first-party MCP (mcp.brevo.com, GA) so Matt can read and write it from Claude, and full read/write API coverage. Mailchimp was rejected on evidence, not preference: its free tier fell 2,000 → 500 → 250 contacts and all automation was removed, so it cannot do what was asked. The call fails OPEN and runs LAST — after the notification email has sent and the KV record is written — so a marketing-platform outage can never cost a signup; the worst case is a contact added by hand. It fails LOUDLY, per #11117: that incident's defect was not the fail-open choice but the silence, so the throw, non-2xx and misconfigured-list branches each announce themselves. Not-configured is deliberately silent — until the keys are set the integration is simply off, and warning on every submission would train the reader to ignore the log that matters. updateEnabled: true so a returning visitor updates rather than 400s as a duplicate, and the API key is redacted by value from any diagnostic, since providers sometimes echo the credential back in an error. Bot (honeypot) submissions are never subscribed. Verified by mutation: removing fail-open, removing the failure warning, removing updateEnabled, or removing key redaction each fails its own test (7/7 green when restored). Configuration: BREVO_API_KEY and BREVO_LIST_ID as Pages environment variables; absent in both environments today, so this is inert until Matt provisions them. † ‡
  • ✅ marketing.ac.waitlist-notification-via-brevo — the waitlist notification email is sent through Brevo’s transactional API, not Azure Communication Services, and the form therefore requires no Azure configuration at all. This closes a five-month outage (#12154): AZURE_COMMUNICATION_CONNECTION_STRING was dropped from both Pages projects during the #4445 migration, so /contact-form fail-fast 500’d on prod and uat from 2026-04-01 and every waitlist signup was rejected at the door. Provisioning a production ACS resource was rejected as the fix: no ppp-uk-prod-acs exists, the ppp-uk-prod Pulumi stack is explicitly marked not deployable (#11392, ≈18 unset production secrets and a placeholder imageTag), and pulumi up against it would stand up the entire production Azure estate to obtain one connection string. Brevo was already approved (Rob + Matt, 2026-09-01) and already wired for contact subscription, so routing the notification through it removes the Azure dependency rather than adding a second provider. The send fails CLOSED — unlike the KV write and the list subscription that follow it — because a visitor told their signup succeeded when nobody was notified is precisely the harm #12154 caused; ordering is what makes the 200 mean “somebody was told”. replyTo is the signup, so replying answers the doctor rather than PPP’s own mailbox, and the sender is admin@professionalperformanceportfolio.com because that is the only verified sender on the Brevo account (no authenticated domain yet — authenticating one would allow a noreply@ sender). Provider error bodies are never logged, only status codes, since a Brevo error can echo the request payload and that payload carries the signup’s name and email. Verified by mutation, each failing its own assertion: restoring the fail-fast (7 red), an unverified noreply@ sender, making the send fail open, dropping replyTo, and leaking a honeypot submission — 105/105 green when restored. Additionally verified against the live Brevo API, which the mocked tests cannot prove: the exact payload the code builds returned HTTP 201 with a real messageId. Configuration: BREVO_API_KEY is now required for the form to function in any environment. † ‡
  • ✅ marketing.ac.waitlist-doctor-confirmation-via-brevo-template — a doctor-facing waitlist confirmation email is sent via Brevo's Template API (templateId, not a hardcoded textContent/htmlContent payload), so Matt can edit the subject/body/branding directly in Brevo's dashboard template editor with no code deploy. Before this, only the internal notification existed (plain text, to admin@, hardcoded) — there was no doctor-facing confirmation at all, and because that internal send already used Brevo's raw smtp/email API rather than a dashboard template, there was nothing in Brevo's UI for Matt to find when he went looking for "the email sent in reply". Sent to the signup's own email with their name as a template param, after waitlist-notification-via-brevo has already succeeded. Fails differently from the internal notification on purpose: BREVO_WAITLIST_CONFIRMATION_TEMPLATE_ID is optional, and not-configured is silent — the template genuinely does not exist yet in Brevo (every environment's state at the time this shipped), not a misconfiguration, matching waitlist-brevo-subscription's own not-configured convention rather than crying wolf on every submission. Once configured, a send failure is loud (logged, same visibility as the internal notification) but does not fail the request — by the time it runs the internal notification has already succeeded, so "somebody was told" is already true, and rejecting the visitor's signup over a secondary confirmation email would recreate #12154's harm one layer up. Verified red-then-green: the templateId-payload assertion and the non-blocking-failure assertion both fail against the pre-fix code (no confirmation call exists at all) and pass with the fix. Configuration: BREVO_WAITLIST_CONFIRMATION_TEMPLATE_ID as a Pages environment variable, pointing at a Brevo dashboard template Matt or Rob authors; absent in both environments today, so this is inert until provisioned — same posture as waitlist-brevo-subscription's BREVO_LIST_ID. † ‡
  • ✅ marketing.ac.hero-laptop-shows-full-platform — the hero laptop shows the full PPP platform, while the phone beside it stays on CPD Home (Matt, 2026-09-01: “laptop-device.png to be changed to show PPP home not CPD home”, then “the mobile can stay on CPD home”). The laptop is captured as test-full@ppp-test.com, so its sidebar shows PPP Dashboard, PPP Pulse, PPP Passport and Appraisals — the nav a CPD-only account can never see. The route stays /cpd-dashboard, chosen against live UAT data rather than from the route name: no seeded account has a populated /ppp-dashboard (flat-zero Pulse chart, empty Logbook/WBA donuts, an “Outstanding Onboarding 8/11” checklist over the top), so capturing it would put an empty product on the front page — the exact harm #12138 exists to prevent. assertFullPlatformNav is the mirror of assertCpdOnlyNav: it refuses to write an asset sold as the full platform whose nav is CPD-only, so the account/asset contract now holds in both directions rather than only catching over-entitled captures. This does not relax #12138 — preview-cpd-home.png and mobile-cpd-home.png are still sold as CPD Home and still must show CPD-only nav; that rule is about an asset’s nav matching the tier its surrounding copy claims, and the hero laptop is not captioned as CPD Home. † ‡
  • ✅ marketing.ac.device-corners-follow-the-bezel — the composited devices keep their rounded corners; the screenshot is pasted only where the shell was chroma-keyed, never across the screen’s whole bounding box. A device screen is a rounded rectangle, so its bounding box also contains bezel pixels at each corner — 4,428 px on the phone (1.54% of the rect), 440 px on the laptop. The paste loop wrote that rectangle unconditionally while the black-fill pass immediately above it was already correctly gated on the key, so a white page corner replaced the rounded bezel and the phone rendered with square corners against the dark hero (Rob spotted it on the live mockup, 2026-09-01). The gate is the key mask itself, recorded before the black fill overwrites the key colour — sampling it afterwards would read the fill, not the shell. Measured red-then-green on the committed artwork: 4,338 of the phone’s 4,428 bezel pixels were painted opaque white before the fix, 0 after. The laptop’s 440 corner pixels measured 0 both ways, because that screenshot’s own corners are not white — which is why only the phone looked square, and why the assertion is on the bezel pixels rather than on a visual proxy. † ‡
  • ✅ marketing.ac.pricing-tile-shows-amc-accredited-label — the CPD Home pricing tile shows a visible "AMC-accredited" label directly under the tile title, on both the home page's pricing cards and /plans-and-pricing (both render the shared PlanCard). This is additive to marketing.ac.amc-accredited-leads-cpd-home-tile above, not a replacement: that AC governs the claim's position within the scrollable feature list; Matt's 2026-09-16 feedback was that the tile itself, before any scrolling, did not visibly say "AMC accredited" at all. The Full Platform tile carries no such label, matching its existing "AMC-accredited CPD Home" description line rather than duplicating a badge. † ‡
  • ✅ marketing.ac.high-performance-approach-softened — the "From Burnout to Breakthrough" hero pillar reads "The High-Performance Approach" / "Without the Effort" on two lines, softening the framing toward easing effort rather than only high performance. Matt's original #12261 ask ("in the same font") was implemented literally as one comma-joined sentence in a single Typography; Matt then asked (2026-09-20, on the live video review) for the second clause on its own line — still the same Typography element and styling (weight/size/color all identical), just an explicit <br /> between the two, not a separate visually-emphasised element. † † ‡
  • ✅ marketing.ac.waitlist-signup-city-country — every persisted WaitlistRecord carries city-level location, derived from Cloudflare's own request.cf.city/request.cf.country (present natively on every request a Pages Function receives — no third-party geo-IP lookup, no dependency added). The raw IP itself is never read or retained — only the two derived fields reach the KV record and the admin CSV export, satisfying #12144's location AC without the privacy cost of storing the address it was derived from. Records persisted before this AC (and any request lacking request.cf, e.g. a non-Cloudflare test harness) simply have city/country absent, which the admin CSV renders as an empty field rather than a crash. † ‡
  • ✅ marketing.ac.waitlist-city-country-in-brevo (#12392) — a waitlist signup's city and country also reach the Brevo contact record as CITY and COUNTRY, so Matt can see location in Brevo's own dashboard instead of only the KV export. Sent only when Cloudflare supplies a non-empty string; otherwise omitted (never empty strings) — a localhost/dev signup, or request.cf without geo, syncs exactly as before. Malformed geo (non-strings) is dropped and the contact sync still runs: fail-open is preserved, per #11117. Prerequisite done 2026-09-23 through the Brevo UI: CITY and COUNTRY (Text) created as custom contact attributes — Brevo silently drops attribute keys that do not exist on the account, so a 2xx response proves nothing. Verified live 2026-09-24 on UAT: a real signup produced a Brevo contact with CITY = Southampton and COUNTRY = GB, plus the role and the PPP Waitlist list membership, and both emails (team notification, signer confirmation) were delivered — checked in the Brevo dashboard, not inferred from a 2xx. New Brevo attributes default to hidden on contact pages ("Attributes not shown"), so CITY and COUNTRY were also added to the contact-details group; without that Matt would not see them. † † ‡
  • ✅ marketing.ac.waitlist-role-options-consultant-other-locum — the waitlist "I am" role dropdown (WAITLIST_ROLES, #11996) includes "Consultant - Other" and "Locum Doctor", positioned immediately after "Consultant - Psychiatry" and before "Medical Student" — preserving the existing "Medical Student before Other" ordering contract. WAITLIST_ROLES is the single source shared between the form's dropdown and the server-side validation in functions/contact-form.ts, so both stay in lockstep by construction. † ‡
  • ⏳ marketing.ac.waitlist-copy-launch-day-discount-hook — the waitlist-mode CTA copy (ContactForm's notice, rendered on the home page's waitlist section, /contact, and the standalone /waitlist page) reads "Join the waitlist today to lock-in your limited Launch-Day Discount!", replacing the earlier #11988 wording ("Be first in line. Join the PPP waitlist today and get early access the moment we launch."). Matt first suggested "Join the waitlist today to lock-in a Launch-Day Discount." (2026-09-16 comment on #11997); that shipped, but Matt then asked (2026-09-19, after seeing it live) to personalize with "your" and add "limited" — this revision implements that follow-up wording, applied identically to all three surfaces per his 2026-09-01 call direction that the on-site form and the social-media waitlist page must never diverge. Still marked ⏳, not ✅: #11997 stays for-discussion until Matt confirms this latest revision — treat it as open until he signs off. † ‡
  • ✅ marketing.ac.footer-links-to-waitlist — the site-wide Footer's primary nav link reads "Waitlist" and points at /waitlist, replacing the previous generic "Contact" link to /contact. /contact 301-redirects to /waitlist (instances/marketing/public/_redirects) so existing bookmarks, external links, and search indexing don't dead-end. This does not relax marketing.ac.cta-destination-coverage above — the footer link still resolves to its own real route, just a different one. Superseded 2026-09-20 by marketing.ac.contact-page-removed below — /contact was, at the time this AC shipped, still a real standalone page/route (only the footer's link away from it changed); it no longer exists at all.† ‡
  • ✅ marketing.ac.contact-page-removed — the standalone /contact page and route no longer exist at all (Contact.tsx deleted, ROUTES.contact removed, the header nav's loginEnabled-gated "Contact Us" entries removed) — /contact is now purely a redirect target, not a distinct surface with its own heading/copy/nav presence in any launch state. This goes further than marketing.ac.footer-links-to-waitlist above, which only pointed the footer's link elsewhere while /contact itself remained a real page that #12143 (2026-09-01) had deliberately kept titled "Contact Us." Two redirect mechanisms now both point /contact → /waitlist: the pre-existing static public/_redirects 301 (edge-level, what a real deployment actually serves) and a React Router <Redirect exact from="/contact" to={ROUTES.waitlist} /> in index.tsx (kept for local-dev parity, since the dev server does not serve _redirects) — the two are redundant by design, not a conflict, and the static rule wins in any real deployment since Cloudflare Pages evaluates _redirects before the SPA ever loads. † ‡
  • ✅ marketing.ac.functionality-preview-looping-motion — each "See it in action" tab (FunctionalityPreviewSection) plays a looping product-motion clip (preview-cpd-home-motion.mp4, preview-ppp-full-motion.mp4) instead of, previously, only a static still — Matt confirmed on the 2026-09-01 call that this "long form GIF" had been agreed but never delivered. One clip per existing tab, matching the tab structure rather than a single combined asset (Rob, 2026-09-17). Each clip is a genuine Playwright recording of a real scrolling session against the seeded account for that tier — test-cpd@ppp-test.com on /cpd-dashboard for CPD Home, test-full@ppp-test.com on /logbook/case for Full Platform — captured from UAT, never localhost (#12139), and gated by the same assertCpdOnlyNav/assertFullPlatformNav tier contract as the still captures (#12138) so a mis-credentialled recording fails loudly instead of shipping. The recorded session signs in on a throwaway, unrecorded browser context first and hands its storage state to the recorded context, which navigates straight to the target route — the first capture attempt recorded the login form itself (with the seeded account's credentials visible) into the first several seconds of the loop, because Playwright's recordVideo starts at context creation, before any navigation; this is why sign-in and recording are on two separate contexts. GlassScreenFrame gained an optional videoSrc prop (falls back to the existing static src as both the <video> poster and the no-motion case), so no new visual primitive was introduced — the glass-pane framing is unchanged. Retains a deliberate, light blur (ffmpeg gblur=sigma=2) — layout, colour and headings stay clearly legible, fine text/data does not — softer than the first attempt's sigma=6, which Rob found too strong on review; a boundary crossfade (fade in/out, 400ms) removes the loop's jump-cut. Both clips are well under a landing-page file-weight budget (under 0.4 MB each). † ‡

Home page — Features marquee touch/click interaction (#12265) ​

Matt walked the roadmap features section on mobile during the 2026-09-16 weekly tech call and found it neither swipeable nor clickable — a gap the original #9892 marquee build never addressed, since it shipped as a pure CSS auto-scroll with no interaction model at all.

  • ✅ marketing.ac.feature-marquee-touch-drag — the Features marquee (FeatureMarquee) responds to a horizontal touch drag: touching a card pauses the auto-scroll (mirroring the existing desktop :hover pause) and dragging translates the track by hand; releasing resumes the auto-scroll. Pre-fix the row had no touch handler at all — a touch neither paused nor moved the animation, so "sliding" was impossible on mobile. † ‡
  • ✅ marketing.ac.feature-marquee-links-to-feature-page (#12418) — tapping or clicking a feature card (a drag that crossed the swipe threshold does not count as a tap) navigates to /features#<slug>, the single-screen features page with that feature's explanation selected, rather than opening a dialog. Cards are real <a href> links, so open-in-new-tab and copy-address work; the click is handled client-side. The drag/tap guard survives on its own swiped flag because the pointer-up handlers clear the drag state before the browser fires the click that follows a mouse swipe — without it every desktop swipe released over a card would navigate away. Supersedes marketing.ac.feature-marquee-opens-detail-dialog (#12265, 2026-09-16, dialog with detail copy): Matt saw the popup live on 2026-09-22 and said it was not what had been agreed — a dedicated screen. The Dialog and its data-testid are removed; detail copy now renders on the /features page. † † ‡
  • ✅ marketing.ac.feature-marquee-card-text-contrast — the marquee card's title and description render in common.white / rgba(255,255,255,0.85), meeting the DESIGN.md ≥4.5:1 AA contrast floor against the dark FeaturesSection background. Pre-fix, both Typography elements had no explicit color, so they inherited dark text.primary — legible against a white surface, but the card is GlassCard tone="light", an 8%-opacity translucent white meant to sit on the section's dark navy, not an opaque white card — so the effective rendered contrast was near-zero (measured luminance 0). Rob caught it live on localhost. † ‡
  • ✅ marketing.ac.feature-marquee-detail-copy-draft — closes the placeholder-copy gap feature-marquee-opens-detail-dialog above left open: each of the 12 FEATURES entries now carries a detail field (shown in the dialog at the time; since #12418, on the /features page), distinct from the card's own one-line description (which the dialog previously just repeated). Same drafting pattern as CPD_HOME_INCLUSIONS/PPP_FULL_PLATFORM_INCLUSIONS in planTiers.ts (#7905): "Engineering drafts the copy from the specs — Matt approves wording before go-live." Copy is drafted from what is already specced for each feature elsewhere in this doc and planTiers.ts (not invented beyond it). † ‡
    • Revised 2026-09-18 (#12286) — each detail now carries a second paragraph pulling concrete, already-✅-shipped capabilities from that feature's own spec (dashboard.md, ppp-roadmap.md, cpd-home.md, wellness.md, logbook.md, ppp-passport.md/passport-cv.md, retrospective.md, appraisals-wba.md, timesheets.md, attendance.md) rather than restating the card's one-line description in different words. Every added sentence traces to a shipped AC in its source spec — nothing invented beyond what those docs already document. Rob: "it seems rather bland - can you add more detail for each?" †
    • Approved 2026-09-19 — Rob reviewed all 12 detail entries directly against the shipped specs they cite; content is accurate and traces correctly. Status promoted ⏳ → ✅, closing the #7905 review gate for this copy. One unrelated finding surfaced during review — the pre-existing "patented" wellness-algorithm claim (in the PPP Pulse card's description, not the detail copy this AC governs) could not be verified against any spec doc — filed separately as #12295 rather than blocking this AC's approval.
  • ✅ marketing.ac.feature-marquee-mouse-drag (#12285) — the Features marquee also responds to a horizontal mouse drag on desktop, mirroring feature-marquee-touch-drag above (onMouseDown/onMouseMove/onMouseUp/onMouseLeave in place of the touch handlers) plus a cursor: grab/grabbing affordance. Pre-fix, :hover paused the auto-scroll and touch-drag worked, but there was no mouse-equivalent handler at all. A first fix pass wired the handlers correctly (state updated, cursor changed) but the row still never visually moved — animationPlayState: 'paused' on the same element as a plain transform declaration leaves the CSS animation's last keyframe-computed transform in control of computed style, so the drag's translateX(dragOffset) never rendered; root-caused by dispatching real MouseEvents and reading getComputedStyle(...).transform directly (ruling out a test-tool artifact), fixed by setting animation: 'none' (not merely paused) while dragging. † ‡
  • ✅ marketing.ac.feature-marquee-drag-goes-manual (#12285) — once a drag (touch or mouse) actually moves the row past the tap threshold, auto-scroll stops permanently for that row instance — it does not resume the infinite CSS animation on release, and stays exactly where the user left it. Pre-fix (auto-scroll rows only), releasing a drag would snap back to auto-scrolling from the animation's start position. † ‡
  • ✅ marketing.ac.feature-marquee-card-equal-height (#12286) — every marquee card renders at a fixed 180px height (GlassCard already stretches its content to fill via height: '100%'), instead of each card's height following its own description-text length. Pre-fix, cards in the same row sat at visibly uneven heights depending on how long each feature's one-line description happened to be. † ‡
  • ✅ marketing.ac.waitlist-page-form-width — the standalone /waitlist page's form card renders at a 720px max-width, up from 600px. /waitlist was built mobile-first for social-bio-link taps (#12145) and its 600px cap was never revisited once /contact started redirecting there (marketing.ac.contact-page-removed above) and it began taking real desktop traffic too — at 1440px the narrow card read as squished, with wide empty margins either side. 900px (MUI's next Container breakpoint up) was tried first and rejected — the form's single-column TextField rows stretched edge-to-edge and looked worse, not better; 720px is a deliberate value in between, not snapped to a breakpoint. † ‡
  • ✅ marketing.ac.homepage-waitlist-section-column-width — the homepage's own "Join the Waitlist" section (the SECTIONS.contact in-page anchor, distinct from the standalone /waitlist page above) splits into two Grid columns at md:6, lg:4, not md:4. Both columns were md:4 (each a third of the 12-column grid, with 4/12 left empty either side of the centered pair) — at the ~900-1100px zone where md first applies (isMobile only covers <600px, so nothing forces single-column stacking there), both the text column and the ContactForm card were cramped into roughly 250px each, visibly crowding the form. † ‡
Current Status ​
Sub-featureStatusNotes
Strapline / tab title✅ Built#7537 closed
Social share card✅ Built#7671 — Athlete Doctor retired
OG image generator✅ Builtscripts/generate-og-image.mjs

Open issues on label:feature:marketing — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Implementation / Architecture ​

OG/Twitter meta tags are static in instances/marketing/index.html so crawlers can read them without executing JavaScript. The share-card image is instances/marketing/public/og-image.png, regenerated by instances/marketing/scripts/generate-og-image.mjs — a Playwright screenshot of an HTML card that inlines the approved emblem-only mark (ppp-emblem-v0.svg) on brand navy (#151D28) with a brand-blue (#117BE5) accent. Marketing E2E coverage lives in instances/marketing/e2e/.

Marketing E2E is a merge gate (#11310). The Test Marketing Site (E2E) job in ci.yml runs the four hermetic specs — smoke, header-responsive, waitlist-cta, news-admin — on every PR touching instances/marketing/**, and blocks via the CI Summary "Check overall status" step. Playwright's webServer serves the Vite production build (dist/) with vite preview, chosen over the previous npx serve dist for two reasons: vite is a lockfile-pinned devDependency (no unpinned package resolved over the network at test time), and Vite's default appType: 'spa' provides the history fallback that client-side routes such as /faqs, /news and /news-admin need — a plain static file server 404s every one of them. No secrets, no network egress, no deployed environment: news-admin mocks /api/news via page.route and deliberately asserts the unauthorised path rather than a live KV backend.

live-validation.spec.ts is excluded from that job: it targets MARKETING_URL (a deployed UAT/production domain), so it cannot pass against a local build. It remains covered by lighthouse.yml, which runs it weekly (Monday 07:00 UTC) against the deployed domain — still not a pre-merge gate on the code in a diff, since it runs post-merge on a schedule, not per-PR. (It is not in e2e.yml.) As of #11322, that weekly run's marketing-e2e job actually fails on a real test failure — the step-level continue-on-error: true on "Run live domain E2E tests" was removed, so steps.tests.outcome == 'failure' (previously dead code, since continue-on-error forced outcome to always read success) now reaches the "Fail if tests failed" step and the job goes red. This closes a real gap: before #11322, live-validation.spec.ts could regress indefinitely on the deployed domain with the workflow reporting green every week. Rob's decision (2026-08-11, #11322): drop continue-on-error in this existing weekly job now; keep the weekly cadence; defer moving to a daily/e2e.yml cadence to #11193 rather than bundling it here. Before #11310 no workflow ran any of these specs, so bdd-features: above declared executable acceptance criteria that the merge gate never actually executed — the same "green tick that inspected nothing" failure mode as #11030.

The e2e specs are type-checked too (#11324). Running the specs (#11310) is the stronger verification, but until #11324 they were the only verification: tsconfig.json includes ["src"] and tsconfig.functions.json includes ["functions"], so instances/marketing/e2e/*.spec.ts and playwright.config.ts sat outside every tsconfig and no static gate could see a renamed Playwright API, a wrong locator signature or a stale import. A dedicated tsconfig.e2e.json (include: ["e2e", "playwright.config.ts"]) is now the third project in lint:strict — chosen over widening tsconfig.json to ["src", "e2e"] so that Playwright and Node types stay out of the app's compilation and, more importantly, the app's DOM/vite types cannot mask a mistake in a spec. It caught a real defect on its first run: playwright.config.ts wrote ['github' as const], which puts the assertion on the string and widens the array to "github"[], failing ReporterDescription's fixed-length tuple. Type-level only — Playwright always accepted the value at runtime, which is precisely why nothing had noticed.

Marketing package scripts. instances/marketing/package.json exposes the site's operational scripts: build / start / preview (Vite), test (Vitest — unit tests for the Cloudflare Pages Functions under functions/), lint:strict (type-checks the app, the Functions and the e2e specs as three separate tsconfig projects), e2e / e2e:live (Playwright), generate:sitemap, verify:policy-fidelity, and seed:news. seed:news runs scripts/seed-news-kv.ts to publish scripts/news-content.json into the PPP_NEWS KV namespace; it is deliberately a human-run command rather than a deploy step, because seeded articles carry no reviewStatus and therefore publish without passing the admin review gate — see marketing-news-automation.md (#11114).

A uat→main promotion PR alone deploys marketing to prod (#12277). cd.yml gains a push trigger scoped to branches: [main], so a promotion merge (e.g. #12276) auto-runs the marketing build/gate/deploy jobs with no second manual workflow_dispatch --deploy_marketing_prod=true step. Rob: "We have to keep it simple — a uat to main PR should be all we need to deploy marketing to prod." cd.yml's push trigger was previously removed entirely to stop per-merge CD churn on uat, where merges are frequent and mostly superseded before a deploy finishes — that reasoning does not extend to main, where merges are rare, deliberate promotion events. ci-gate's if: is extended to also run on push-to-main, mirroring the #11166 fix for the identical "a skipped ci-gate permanently blocks a success-gated deploy" defect class already fixed once for the uat schedule path, rather than loosening deploy-marketing-prod's needs.ci-gate.result == 'success' check. The Cloudflare zone/DNS prod deploy (environment == 'prod', #11084) stays workflow_dispatch-only and is untouched — the two remain deliberately decoupled.

Open GitHub Issues ​
#TitleStatusPriority
#7671Align social-share card to new strapline + on-brand OG logoopenmed
Change Log ​
DateChangePR/IssueReason
2026-10-04Waitlist copy updated on both the home waitlist section and /waitlist: intro blurb "Leave your details and we'll be in touch on our pathway to launch!" (now also shown on /waitlist) and success banner "You've joined the wait list and locked in your launch day discount. We'll be in touch soon!". Both surfaces import one shared waitlistCopy.ts.#0, #12624, #11177Matt's copy request on #12624 (via admin@), requiring matching copy on both surfaces; a shared constants file makes drift structural rather than a convention.
2026-10-01marketing.ac.screenshots-captured-from-uat's profile-completion-banner clearing now works by giving the capture script's two accounts (test-cpd, test-full) genuinely complete profiles — jobContractStartDate is seeded for both in seedTestAccounts.ts — instead of pre-empting the banner via sessionStorage before first paint.#12667, #12664#12667 removed ProfileCompletionGuard's dismiss control entirely (onboarding-checklist.profile-banner-no-dismiss), so the capture script's sessionStorage.setItem('ppp-profile-banner-dismissed', '1') call became a silent no-op — caught by code review before merge, since neither capture account had a complete profile and the next asset regeneration would have shipped the undismissable banner over the dashboard screenshots.
2026-09-24marketing.ac.waitlist-city-country-in-brevo is now verified live on UAT: a real waitlist signup produced a Brevo contact with CITY = Southampton and COUNTRY = GB, plus the role and PPP Waitlist list membership, and both emails (team notification and signer confirmation) were delivered. CITY and COUNTRY were added to the contact-details attribute group in Brevo, because new attributes default to hidden on contact pages.#12441, #12392#12392's last acceptance criterion required checking a real Brevo contact record, not just a 2xx response. Recorded during the 2026-09-24 UAT demo for Rob's review (Loom Review Model, #11177).
2026-09-24/features rebuilt as one screen (all 13 features listed, selected one explained in place, hash-linked from the home marquee cards, no popup); Features added to the header, mobile menu and footer nav; phone feature strip sticks in the thumb zone above the waitlist pill (GlassSection overflow hidden -> clip so sticky works); FEATURES moved to a shared data/features.ts; hero avatars Dr.1/Dr.2 swapped; "Latest news" panel removed from the home page; every secondary page gets exactly one h1 (SectionHeading as prop); waitlist city/country sent to Brevo as CITY/COUNTRY; marketing admin vs PPP admin boundary documented in bounded-contexts.md. Supersedes marketing.ac.feature-marquee-opens-detail-dialog.#12430, #12418, #12419, #12421, #12422, #12424, #12392, #11177Matt's 2026-09-22 weekly tech call (features should go to a dedicated screen "a heads up display rather than in out in out"; news newest-first; swap two hero thumbnails; remove the Latest news panel; two admins) plus Rob's 2026-09-23 direction (nav/footer link, thumb-zone mobile navigation) and the #11177 click-through audit (missing h1). A first cut of /features stacked 13 panels and was rejected by Rob as not user friendly; the design-reviewer pass then found the sticky strip was silently disabled by an ancestor's overflow, now fixed and tested on rendered position.
2026-09-20Task 2 video-review fixes — hero pillar title line break, /contact removed and consolidated onto /waitlist (redirect + nav cleanup), widened the /waitlist form (600px -> 720px), fixed a homepage waitlist-section grid squeeze at ~900-1100px viewports, and added a synthetic cursor overlay to the walkthrough recording scripts.#12309, #11177Matt's 2026-09-19/20 review of the Task 2 walkthrough video and live-site screenshots flagged the hero copy styling, an over-narrow /waitlist page, and asked to see where the AI clicks in future recordings; a subsequent live check found the homepage waitlist section's grid columns cramming text into the form at common desktop widths.
2026-09-19Fixed an intermittent E2E flake in the "Features marquee card opens a detail dialog on click" test by emulating prefers-reduced-motion instead of clicking a continuously-animating target.#12304, #12265The test's force:true click raced the marquee's auto-scroll animation — surfaced as a red CI Summary on PR #12302's rerun, confirmed unrelated to that PR via CI failure screenshots showing the target card clipped by the viewport edge.
2026-09-19Added "Consultant - Other" and "Locum Doctor" to the waitlist role dropdown, after "Consultant - Psychiatry" and before "Medical Student".#12301, #12300Matt's direction on #11177 (2026-09-16) was posted as a comment rather than ticketed and fell through when the rest of that call's items were split into their own issues.
2026-09-19New POST /api/news/admin/discover Pages Function, gated behind the same NEWS_ADMIN_TOKEN bearer pattern as the review gate: runs createRssDiscoverySource against 3 confirmed feeds (ABC Health, AMA WA, ASMOFQ), dedupes discovered candidates against the existing queue by sourceUrl, and adds new ones as pending via the same KV write mechanism seed-news-kv.ts and the approve/reject flow already use. NewsAdmin.tsx gets a "Check for new articles" button with a loading/error state and a visible note that new candidates carry the raw RSS excerpt, not AI-drafted commentary.#12289, #12281Rob, 2026-09-19: accepted the raw-excerpt fallback and confirmed feed list to unblock #12281. AI editorial commentary (OQ-10123c) stays out of scope this pass; stubEditorialWriter is used deliberately. MJA InSight+ was dropped from the feed list — no RSS feed could be found or verified for it (Craft CMS site, no autodiscovery tag, standard paths all 404) — rather than guessing a URL.
2026-09-19New POST /api/news/admin/add-by-url Pages Function, gated behind the same NEWS_ADMIN_TOKEN bearer pattern as discover.ts/admin/review.ts: takes { url }, fetches the page server-side, extracts og:title/og:description/ og:image (falling back to <title>/first <p> when og: tags are missing), dedupes against the existing queue by sourceUrl (any review status), and writes a new pending candidate via the same KV mechanism seed-news-kv.ts and discover.ts already use. Extracted discover.ts's inlined auth/read/ index/dedupe helpers into src/data/newsQueueStore.ts so both endpoints share one implementation instead of duplicating it. NewsAdmin.tsx gets a URL input + "Add article" button with loading/error states and a specific "already in the queue" message for the duplicate case.#12289, #12282Rob, 2026-09-19: confirmed scope to unblock #12282, sequenced after #12281 — paste-URL input, og:-metadata fetch, no AI commentary matching #12281's decision, lands as pending candidate in the existing review queue, not an instant-publish shortcut. The og:image is carried through as a link-card URL (same hotlink convention rssDiscovery.ts already uses for an RSS item's own lead image), not downloaded into repo storage — there is no R2/object-storage binding in this Pages project for a runtime fetch to write bytes into; #12268's "downloaded into public/assets/news/" was a one-off manual step done offline against the 8 seed articles, not a runtime code path.
2026-09-19Add 2 new animated count-up stat boxes to the "Bridging the unmet need in medical training" panel: 89% (rate the quality of their clinical supervision highly) and 83% (would recommend their current training program), both sourced to the Medical Board of Australia's 2025 Medical Training Survey — panel now shows 6 stats instead of 4.#11832The original ask was for "competence and confidence" stats, but the Medical Training Survey doesn't measure those two words directly. Rob approved substituting the closest genuinely-measured, honestly-citable figures from the 2025 National Report (quality of clinical supervision; recommend current training) rather than stretching the source to claim something it doesn't say.
2026-09-19marketing.ac.waitlist-copy-launch-day-discount-hook wording revised from "Join the waitlist today to lock-in a Launch-Day Discount." to "Join the waitlist today to lock-in your limited Launch-Day Discount!" across all three waitlist-mode surfaces (ContactForm, /contact, /waitlist).#11997Matt's own follow-up direction (2026-09-19), asking to personalize with "your" and add "limited" after seeing the first version live. AC stays ⏳ pending his sign-off on this exact wording.
2026-09-19marketing.ac.feature-marquee-detail-copy-draft promoted from ⏳ to ✅ — Rob reviewed all 12 Features detail-dialog entries against the shipped specs they cite and approved the wording.#12286Closes the #7905 review gate for this copy (engineering drafts, Matt/Rob approves before treating it as final). One unrelated finding from the review (the "patented" wellness-algorithm claim) was filed separately as #12295 rather than blocking this approval.
2026-09-19Footer's primary link changes from "Contact" (-> /contact) to "Waitlist" (-> /waitlist). /contact now 301-redirects to /waitlist so existing bookmarks, external links, and search indexing don't dead-end. The /contact route/page itself is unchanged.#12288Matt: the footer's primary link should point doctors at the waitlist form, the actual conversion goal, rather than the generic contact page.
2026-09-18Added a doctor-facing waitlist confirmation email, sent via Brevo's Template API (templateId) rather than a hardcoded payload, so Matt can edit subject/body/branding in Brevo's dashboard with no code deploy. Sent after the existing internal notification succeeds; not-configured is silent (matches the existing subscribeToBrevo convention), a configured send failure is logged but does not block the signup.#12250Rob asked how Matt can configure "the email sent in reply" when a doctor joins the waitlist. Investigation found no doctor-facing confirmation existed at all — only an internal admin@ notification, sent via Brevo's raw API rather than a dashboard template, which is why Matt found nothing to edit when he looked in Brevo's UI.
2026-09-18Each of the 12 Features-marquee cards now carries a fuller detail paragraph shown in the tap/click dialog, distinct from the card's own one-line description that the dialog previously just repeated verbatim.#12265#12265 shipped the swipe gesture and the dialog mechanism, but explicitly left the dialog's actual content as a placeholder pending Matt's copy approval. Drafted engineering-side from already-specced feature detail (same pattern as planTiers.ts's CPD_HOME_INCLUSIONS/PPP_FULL_PLATFORM_INCLUSIONS, #7905) rather than leaving the dialog showing nothing new — flagged ⏳ pending Matt's review/approval of the wording, not treated as final copy.
2026-09-18The Features marquee now supports mouse-drag on desktop, mirroring the existing touch-drag handlers (#12265) with onMouseDown/onMouseMove/ onMouseUp/onMouseLeave, plus a cursor: grab/grabbing affordance.#12285Rob: "on mobile and desktop when I hold my mouse over the features they stop but don't allow me to swipe it left or right". :hover already paused the CSS auto-scroll and touch-drag already worked, but a desktop user with a mouse had no way to then drag the row — only pause-then-click (opening the detail dialog) was possible.
2026-09-18Each Features-marquee dialog detail gains a second paragraph pulling concrete, already-shipped capabilities from that feature's own engineering spec, and marquee cards now render at a fixed equal height.#12286Rob: "it seems rather bland - can you add more detail for each? Does our SGE docs have the detail?" and "let's make each slider panel equal size - I do not like the uneven heights". Every added sentence traces to an already-✅ AC in its source spec (dashboard.md, ppp-roadmap.md, cpd-home.md, wellness.md, logbook.md, ppp-passport.md/passport-cv.md, retrospective.md, appraisals-wba.md, timesheets.md, attendance.md) — nothing invented beyond what those docs already document.
2026-09-17Waitlist CTA copy changed to "Join the waitlist today to lock-in a Launch-Day Discount." on ContactForm and the standalone /waitlist page; removed the page's duplicate subheading now that ContactForm's own notice carries the same line.#11997Applies Matt's suggested wording from his 2026-09-16 comment on #11997 as a working draft pending his confirmation (issue remains for-discussion/open).
2026-09-17The "See it in action" section now plays a looping product-motion clip per tab (CPD Home, PPP Full Platform) instead of a static screenshot, recorded from real UAT sessions with a light blur.#12140Matt confirmed on the 2026-09-01 call that the "long form" looping GIF/video had been agreed but never delivered; the two static stills were the placeholder this replaces.
2026-09-17WaitlistRecord now carries city/country, derived from Cloudflare's native request.cf.city/request.cf.country and surfaced in the admin CSV export; the raw IP itself is never read or retained.#12144The rest of #12144 (KV persistence, admin export, Brevo integration, privacy copy, dedupe) was already shipped — this was the one remaining gap, closed without adding a third-party geo-IP dependency.
2026-09-17CPD Home pricing tile now shows an "AMC-accredited" label directly under the title; the "From Burnout to Breakthrough" hero pillar copy softened to "The High-Performance Approach, Without the Effort".#12262, #12261Matt flagged twice on the 2026-09-16 weekly tech call that the CPD Home tile did not visibly say "AMC accredited" — the copy existed but was buried in the tile's scrollable feature list, not visible on the tile itself (#12262). Separately, "Without the Effort" softens the framing toward easing effort rather than only high performance (#12261).
2026-09-17FeatureMarquee card title/description now render in explicit light colors (common.white / rgba(255,255,255,0.85)) instead of inheriting dark text.primary, meeting the DESIGN.md 4.5:1 AA contrast floor against the dark FeaturesSection background.#12265Rob caught it live on localhost after the touch-drag/detail-dialog build shipped — the card's translucent-white glass surface sits on a dark background, so unset dark text rendered at near-zero contrast.
2026-09-17FeatureMarquee now responds to a horizontal touch drag (pauses auto-scroll, translates the track by hand) and clicking/tapping a card opens a detail dialog with that feature's title/description.#12265Matt found the mobile roadmap carousel neither swipeable nor clickable on the 2026-09-16 call; detail-screen copy stays placeholder pending his final wording decision.
2026-09-17cd.yml gains a push trigger scoped to branches: [main] that auto-deploys marketing to Cloudflare Pages Production — a uat→main promotion PR no longer needs a second manual workflow_dispatch with deploy_marketing_prod=true.#12277Rob: "We have to keep it simple — a uat to main PR should be all we need to deploy marketing to prod!" cd.yml's push trigger was removed repo-wide to stop per-merge CD churn on uat (frequent merges, mostly superseded before a deploy finishes) — that reasoning does not apply to main, where merges are rare, deliberate promotion events. ci-gate's if: is extended to also run on push-to-main (mirroring the #11166 fix for the same "skipped ci-gate permanently blocks the deploy" defect class on the uat schedule path) rather than loosening deploy-marketing-prod's success check. The Cloudflare zone/DNS prod deploy (environment == 'prod') stays workflow_dispatch-only and is untouched.
2026-09-15/features illustrates each tier with its own audited screenshot, and the page is added to sitemap.xml.#12137, #12138#12137's remaining acceptance criteria — Matt asked for "maybe a screenshot of each if that's easy enough", and the dedicated page must be reachable. The screenshots are the audited CPD-Home/full-platform pair from capture-product-screenshots.mjs, so a CPD Home section cannot be illustrated with a full-platform screen (#12138).
2026-09-01Hero laptop now shows the full PPP platform (captured as test-full, route kept at /cpd-dashboard for real data) while the phone stays on CPD Home; composited device screens keep their rounded corners.#12166, #12146Matt asked on 2026-09-01 for laptop-device.png to show PPP home rather than CPD home, and separately that the mobile stay on CPD home. The route deliberately stays /cpd-dashboard: no seeded UAT account has a populated /ppp-dashboard (flat-zero Pulse chart, empty Logbook/WBA donuts, an Outstanding Onboarding 8/11 checklist over the top), so capturing it would put an empty product on the front page — the exact harm #12138 exists to prevent. assertFullPlatformNav is added as the mirror of assertCpdOnlyNav so the account/asset contract holds in both directions. Separately, Rob spotted square corners on the live phone mockup: a device screen is a ROUNDED rectangle, so its bounding box also contains bezel pixels at each corner (4,428 px on the phone, 440 on the laptop), and the paste loop wrote that box unconditionally while the black-fill pass above it was already gated on the chroma key — so a white page corner replaced the rounded bezel. Gating the paste on the same key mask, recorded before the black fill overwrites the key colour, took the phone from 4,338 white bezel pixels to 0.
2026-09-01Routed the waitlist notification email through Brevo's transactional API, removing the Azure Communication Services dependency entirely; moved the hero's AMC credential above the Join the Waitlist CTA as wording only, dropping the AMC logo.#12156, #12154, #12144, #12146The form's Pages Function fail-fast 500'd whenever AZURE_COMMUNICATION_CONNECTION_STRING was absent, and that variable was dropped from both Pages projects during the #4445 migration — so every waitlist signup on prod AND uat was rejected from 2026-04-01, for five months, invisibly. Provisioning a production ACS resource was rejected as the fix: none exists, the ppp-uk-prod Pulumi stack is explicitly marked not deployable (#11392), and pulumi up would stand up the whole production Azure estate to obtain one connection string. Brevo was already approved by Rob and Matt on 2026-09-01 and already wired for contact subscription, so the notification moves there — removing a provider rather than adding one. The send fails CLOSED (the KV write and list subscription after it still fail open) because a visitor told their signup succeeded when nobody was notified is precisely the harm #12154 caused. Separately, Matt asked on 2026-09-01 for the AMC logo to be removed and its wording placed above the waitlist button, so the regulator credential is read immediately before the decision to sign up.
2026-08-30Applied Prettier formatting to three marketing files merged unformatted by #12076. Whitespace only — proven byte-identical ignoring whitespace; no behaviour change.#12087#12076 merged useScrollToSection.ts, header-waitlist-cta-cross-page.spec.ts and its own changelog fragment without Prettier formatting. No CI job runs a format check over instances/marketing/ (its PR ran only Actionlint, Pulumi and Mobile lint), so the violation was invisible after merge and reproduces on uat HEAD. That left every downstream PR wedged between two of our own gates: the pre-commit hook refuses a commit until the files are formatted, and formatting them trips the spec-drift gate because marketing.md's code-paths glob is instances/marketing/**. Fixing it on uat clears the deadlock for all branches at once instead of once per PR.
2026-08-30Audited every interactive control on the marketing site by driving it in a browser across all 21 routes and asserting the destination each one reaches. Fixed /plans-and-pricing, which raced a fixed 100ms timeout against Home mounting and silently landed at the top of Home instead of the pricing section.#12081, #11177Matt asked to confirm all buttons work (#11177). Two prior passes verified only content and SEO copy without clicking anything, and a dead header CTA (#12074) was then found by hand on live UAT — so this pass asserted destinations, never visibility.
2026-08-30The header "Join the Waitlist" CTA now reaches the waitlist form from every route, not just Home — from a non-Home page it navigates to Home and scrolls to the contact section once it has mounted; on Home it still scrolls in place without navigating. Fixed for both the desktop button and the mobile drawer entry. The guard is fixed at the root rather than copied a third time - a new shared useScrollToSection hook (instances/marketing/src/landing/hooks/useScrollToSection.ts) owns it, and FloatingCta is refactored onto the hook, so no component that can render outside Home calls the silently-no-op scrollToSection directly any more. The hook also replaces #11812's arbitrary setTimeout(..., 100) with a requestAnimationFrame poll bounded at 3s, firing as soon as the section mounts instead of guessing a delay. A new @regression spec (instances/marketing/e2e/header-waitlist-cta-cross-page.spec.ts) asserts the post-click DESTINATION - the URL is Home and the waitlist form is genuinely in the viewport - across /faqs and /information, desktop and mobile drawer, plus the Home in-place case.#12076, #12074#12074 — Rob, live UAT: the header Join the Waitlist button did nothing at all on /faqs and /information. Root cause: Header.tsx called scrollToSection(SECTIONS.contact) unconditionally from both call sites, and scrollToSection is a deliberate silent no-op when its [data-section] target is absent; the contact section only exists on Home. #11812 had already fixed the identical defect in FloatingCta but fixed the symptom in one component rather than the shared helper, so the header reinherited the bug. It shipped because every existing header-CTA assertion only checked the button was VISIBLE, and the single test that clicked it ran only on / — so the new spec asserts the destination, never merely that no error was thrown.
2026-08-30All four product screenshots on the marketing site are re-captured from accounts whose entitlement matches the copy beside them, via a new committed Playwright script (instances/marketing/scripts/capture-product-screenshots.mjs) rather than by hand. The three CPD Home assets (devices/ipad-cpd-home.png, devices/mobile-cpd-home.png, preview-cpd-home.png) now come from the seeded CPD-only member and show the CPD-only sidebar plus a first-name-only greeting; preview-ppp-full.png comes from the full-PPP member, where the full sidebar is correct. The script refuses to write a CPD Home asset that shows PPP-only nav or a full-name greeting, and a new @regression spec in e2e/smoke.spec.ts asserts the deployed bytes match the committed capture so a stale asset cannot silently ship again.#12072, #12035#12035 — Matt, WhatsApp 2026-08-30: 'All screen shots need a quick audit of what they are representing - the CPD Home only screens display the full platform menu which is not accurate. CPD Home only should show CPD Home only user type screen.' The artwork from #11983 was captured before #11992 shipped first-name-only greetings, and from an account with more entitlement than the surrounding copy claims. The product was already correct on both counts — only the PNGs had rotted, because no gate compared them against the running app. Scripting the capture is the part that stops it recurring.
2026-08-30Pre-launch the header now offers "Join the Waitlist" exactly once per viewport, on both the mobile drawer and the desktop nav. The Contact nav item — relabelled "Join the Waitlist" by #11962 because pre-launch /contact IS the waitlist form — is no longer rendered while pre-launch, leaving only the styled CTA (the desktop button, and the drawer entry below the divider) which is the conversion element and scroll-links to the form. Post-launch (ppp-login-enabled on) the nav item returns as "Contact Us"; no post-launch behaviour changes.#12050, #12036#12036 — Matt, WhatsApp 2026-08-30, with a screenshot of the UAT mobile nav drawer: it listed "Join the Waitlist" twice in a row. Two individually-correct changes had collided (#11962''s relabel and #10122''s separate waitlist CTA). Desktop was in scope after all — the issue said to leave it unless the duplication was visible there, and a 1440px render showed the plain nav link sitting immediately beside the identical filled button.
2026-08-29/contact page heading, subheading, SEO meta, and nav label (desktop + mobile) now read "Join the Waitlist" while pre-launch waitlist mode is on, matching the actual waitlist-signup form underneath instead of the old "Contact Us — get in touch with our team for support and inquiries" copy that promised a support channel the site didn't have yet. Reverts to "Contact Us" once ppp-login-enabled flips true post-launch.#12003, #11962#11962 — found during the #11177 async click-through review. A prospective member with a real support question (billing, account access, a bug) had no working contact path; clicking "Contact Us" just funneled them into the same waitlist signup as everywhere else on the site, under a mismatched heading.
2026-08-29Punched up the waitlist form blurb copy ("Be first in line. Join the PPP waitlist today and get early access the moment we launch.") replacing the softer "You're joining the PPP waitlist — leave your details..." wording.#11988, #11811Matt called the old blurb "a bit soft" on the 2026-08-25 website feedback call and dictated more punchy wording directly.
2026-08-29Hero device artwork rebuilt with real CPD Home screenshots (iPad + phone DeviceFrame), replacing the #9892 abstract Gemini-generated dashboard fragment#11983, #11806Matt and Brooke's direct feedback on the live site — the abstract artwork read as "AI-generated" rather than as the actual platform. Deliberately reverses the #9892 non-literal-artwork decision; new DeviceFrame 'tablet' variant reuses the same real-screenshot-in-chrome pattern already used in "Works everywhere you do".
2026-08-29Added a RouteErrorBoundary around the marketing SPA's routed content so a thrown render error shows a minimal on-brand fallback instead of a silent blank page, plus @regression e2e coverage asserting /plans-and-pricing renders on both direct load and client-side nav#11968, #11959#11959 reported /plans-and-pricing rendering completely blank on UAT with zero console output. Root cause could not be reproduced (router/component/live bundle all checked out clean; best evidence points at transient 2026-08-28 Cloudflare Pages deploy flakiness) — this is defensive hardening + a regression guard, not a confirmed root-cause fix. #11959 stays open pending recurrence or confirmation.
2026-08-26Plans &amp; Pricing card font sizes bumped to the next DESIGN.md scale step -- PlanListItem feature-description text 12px -&gt; 14px, PlanCard description text 14px -&gt; 16px, both lineHeight 1.5 (#11814 item 1, the one item PR #11817's #11814 changelog entry did not actually cover -- that PR delivered the nav logo/News-link fix only).#TBD, #11814#11814's own resolution comment only accounted for 2 of its 3 listed items when it was closed by #11817 -- the font-size complaint ('font is quite small') was never actually delivered. Re-derived by reading the issue body against the live code, not the issue's closed/open status.
2026-08-26Watch mockup in "Works everywhere you do" now shows the PPP emblem on the simulated notification#11834, #11810Matt's website feedback asked for the watch item to include the logo; reuses the existing ppp-emblem-v1.svg icon mark (already used for the pricing card icons on the same page) at 20x20 rather than introducing a new brand asset. Scoped to the watch mockup only.
2026-08-26Acknowledgement of Country popup dismiss button relabelled "Got it" -&gt; "Acknowledge" (#11805 item 2). Batch of other marketing-site fixes from Matt''s website feedback pass: floating "Join the Waitlist" CTA now mounted globally (was Home-only, so absent on every other route) and no longer no-ops when clicked from a non-home page (#11812); nav logo bumped 42px -&gt; 52px and the News nav link hidden while the News page has no published articles, via a shared useHasNews hook (#11814); the AMC accreditation logo and a new "AMC-accredited CPD Home" credential line are now clickable, linking to PPP''s AMC CPD Home register listing (#11815); Plans &amp; Pricing cards widened 420px -&gt; 480px (#11811 item 3); baked-in "Sarah Chen" test name removed from two CPD Home preview screenshots (#11809 item 3).#11817, #11805, #11809, #11811, #11812, #11814, #11815Matt's 2026-08-25/26 website feedback pass (WhatsApp + Website feedback.docx) flagged the popup button copy, the disappearing floating CTA, small/mismatched nav text sizing, an empty News nav link, the AMC credential not being clickable, cramped pricing cards, and a leftover test name in product screenshots. Only #11805 item 2 changes a governed AC in this spec (the popup's dismiss-button text, marketing.acknowledgement-of-country.first-visit-popup) -- the other items are UI/behaviour fixes with no literal-text AC in this file.
2026-08-24All 11 legal/policy pages (Privacy Policy, Terms of Service, Cookie Policy, Medical Disclaimer, Acceptable Use Policy, Subscription & Refund Policy, Accessibility Statement, Copyright & Intellectual Property Notice, Data Processing Agreement, EULA, Third-Party Licenses) now call useSeoMeta, matching the "non-home routes serve their own SEO tags" AC that previously only held for /faqs, /contact, and the other secondary routes. Also corrected Privacy Policy''s Section 5/6/7 infrastructure disclosure, which still described AWS us-east-1 hosting, AWS Secrets Manager, and S3 storage after ADR-0006 moved backend compute, Postgres, Redis, and object storage to a self-hosted NAS, and moved the self-hosted-infrastructure row out of the "5.1 Third-Party Service Providers" table (self-hosted NAS is first-party, not a third-party provider) into a first-party note above it.#11765, #11177Website review click-through for #11177 found these pages were gaps in the otherwise-complete non-home-route SEO metadata coverage (#11690/#11691), and that Privacy Policy's infra disclosure had drifted from ADR-0006 (2026-08-05). Review of the initial PR (#11765) found 4 more legal pages (Copyright Notice, Data Processing Agreement, EULA, Third-Party Licenses) with the identical gap that the PR's own changelog had claimed was fully closed, plus the self-hosted-infrastructure row sitting in a table titled for third-party providers — both fixed in the same PR before merge.
2026-08-24Fixed the hero CTA button being unclickable again — the "bottom hairline" decorative Box used the MUI sx numeric shorthand height: 1, which MUI resolves as height: '100%' (a fraction of the parent) rather than 1px, silently expanding the hairline to the full hero height and, with the default pointerEvents: 'auto', sitting on top of the CTA button in the paint stack. Changed to height: '1px' (a string, exempt from the fractional interpretation) and added pointerEvents: 'none' for defense-in-depth.#11761, #11758Marketing E2E (live-validation.spec.ts:98) failed against live UAT with the exact same symptom (45s timeout, empty intercepted targetUrl) previously fixed in #11627/#11632 — but that fix only addressed the hero's two-tone glow overlay, a different absolutely-positioned decorative Box. This is a second, independent overlay with the same click-interception defect, caused by a different bug (MUI's numeric/percentage sx shorthand) than the first (pointerEvents alone). No AC change — restores the already-documented "hero CTA is always visible and functional" behavior.
2026-08-20New AC under "Strapline & SEO metadata" — non-home routes now serve their own title/description/canonical/OG/Twitter tags in raw HTML via a Pages Function (functions/[[path]].ts), not the homepage defaults.#11691, #11690Manual SEO/AEO review found every non-home route (/faqs, /contact, etc.) served identical, homepage-only metadata to any crawler/tool that reads raw HTML without executing JS, since useSeoMeta only corrects tags client-side post-hydration and the canonical always pointed sub-pages back to /.
2026-08-19marketing.information.matches-source-documents-verbatim prose updated — Info4.tsx and the other 8 unreferenced Info*.tsx files were deleted, not just excluded, closing the pending-retirement state the AC previously described.#11058#11058 deleted the 9 orphaned Info*.tsx files superseded by the July 2026 policy set (#11022); the spec should reflect that retirement completed rather than continuing to describe them as a tracked exclusion.
2026-08-17Fixed the hero CTA button being unclickable — a decorative full-viewport glow overlay was missing pointerEvents: 'none' and intercepted every click in the hero region.#11632, #11627Marketing E2E (live-validation.spec.ts) failed on live UAT; root-caused via elementFromPoint to a paint-stack ordering bug, not a flag or navigation issue. Restores the already-documented "hero CTA is always visible and functional" behavior — no AC change.
2026-08-04Embeds PPP's finalised Acknowledgement of Country as a first-visit pop-up plus a permanent site-wide footer link and a dedicated /acknowledgement-of-country page, all sourced from one shared text constant; replaces the Home "Our values" tile's unreviewed placeholder acknowledgement paraphrase with a link to the same page; and adds Cultural Wayfinder Pty Ltd's companion guide book as an internal-only reference doc outside docs/site/.#11356, #11229Kristin (Cultural Advisor liaison) relayed Jesse at Cultural Wayfinder Pty Ltd's (PPP's Cultural Advisor) finalised website text, asking for a once-only first-visit pop-up plus a permanent homepage-reachable link. Matt (product owner): "Lets go live ASAP."
2026-08-01The marketing e2e specs and playwright.config.ts are now type-checked by a dedicated tsconfig.e2e.json project appended to lint:strict, so a type error in a spec fails the cheap static gate instead of only ever surfacing as a runtime error inside the blocking Test Marketing Site (E2E) job. No acceptance criterion changes — the bdd-features specs and the gate's 44-test hermetic scope are untouched.#11326, #11324The specs sat outside every tsconfig include (tsconfig.json includes ["src"], tsconfig.functions.json ["functions"]), so a renamed Playwright API, wrong locator signature or stale import was invisible to every static gate (#11324). Option 1 of the three the issue offered was taken — a dedicated project rather than widening tsconfig.json to ["src", "e2e"] — so Playwright and Node types stay out of the app's compilation and the app's DOM/vite types cannot mask a mistake in a spec. The new project immediately surfaced a real defect it was built to catch: playwright.config.ts wrote ['github' as const], putting the assertion on the string so the array widened to "github"[] and failed ReporterDescription's fixed-length tuple. Type-level only — Playwright always accepted the value at runtime, which is exactly why nothing had noticed.
2026-08-01The marketing Playwright suite runs as a CI merge gate ("Test Marketing Site (E2E)"), covering the four hermetic specs (smoke, header-responsive, waitlist-cta, news-admin) against the Vite production build; live-validation stays out of the gate, covered weekly by lighthouse.yml against the deployed domain. bdd-features now declares waitlist-cta and news-admin, and the #7906 pricing-order AC records the shipped Passport-at-index-1 order.#11315, #11310These specs were declared as this feature's executable acceptance criteria but no workflow ran them, so the merge gate proved none of them (#11310) — the same "green tick that inspected nothing" failure mode as #11030. Running them for the first time surfaced that the #7906 pricing-order assertion had been failing since #10154, which updated the CPD expectations in that test but not the PPP list.
2026-08-01Homepage Features marquee gains Timesheets and Attendance (11 → 13 items), completing the Features list from Matt's Website-updates brief.#11309, #11308The #9892 marquee carried 11 items; the brief tracked by #8307 lists 13 — Timesheets and Attendance were missing (#11308).
2026-08-01Deleted the retired pre-July-2026 Review and Appeal policy component (Info2.tsx) carrying the superseded $165 incl-GST appeal fee; new AC marketing.information.no-stale-policy-content.#11255, #11034Stale unrendered policy content is a drift hazard for regulator-facing figures; the live page renders the July 2026 policy with the $600 ex GST fee (#11034).
2026-07-29The published /information policy pages and the /cpd-activities specialist table go back to Kristin's verbatim wording for every college reference: the surgical-mortality requirement row reads "Participate in the Australia and New Zealand Audit of Surgical Mortality (ANZASM) by completing all surgical forms sent to the surgeon by ANZASM." on both surfaces, the activity table restores the ANZASM / MALT / ASERNIP-S / "RACS courses" names, and the college list in the Assessment and Recognition policy is whole again — "Australian specialist medical colleges (RACS, RACP, RACGP, ACRRM, etc.)". verify-policy-fidelity.mjs no longer carries any substitution map and scores all 13 policies at 100.0% against the unmodified source documents. The acceptance criterion that required the genericisation is rewritten rather than deleted — renamed marketing.information.no-racs-proprietary-naming to marketing.information.matches-source-documents-verbatim — so the reversal itself stays on the governance record.#11082, #11025, #11057Matt's 2026-07-29 ruling on #11025 confined the RACS/CAPE ban to PPP's own product and feature naming, so #11105's genericisation of these regulator-facing documents is reversed. These are the pages AMC reads, and the controlled source documents were never changed, so genericising only the website had left the published page and the source PDF listing different claimable activities — the failure mode #11025 itself flagged as the reason not to fix this on the website alone. Removing the substitution map means the gate once again proves the pages match the source rather than matching a tolerated divergence from it.
2026-07-28The PPP_WAITLIST KV namespace is now created and bound to both marketing Pages projects by CD on every deploy (and the binding is verified by re-reading the project, not assumed), so waitlist signups actually persist. The write stays fail-open — it must never regress the ACS email — but both failure branches now emit a console.warn naming the binding, signup PII is redacted from the logged error, and the admin endpoint reports persistenceBound so "we are storing nothing" is no longer indistinguishable from "nobody has signed up".#11131, #11117#11117 — verified against the live Cloudflare API on 2026-07-28: no PPP_WAITLIST namespace existed on the account at all and kv_namespaces was null on both Pages projects, so every signup since #10588 was discarded. #10613 recorded creating it as "a manual Cloudflare step post-merge" and nobody performed it — the identical assumption that caused #11114 for PPP_NEWS. It stayed invisible because persistWaitlistSignup fails open by design (correctly: the ACS email is the primary path), and Env.PPP_WAITLIST is optional, so a missing binding was neither a type error nor a runtime error. The fail-open choice was right; the silence was the defect.
2026-07-28Removed RACS-proprietary naming (RACS, ANZASM, ASERNIP-S) from the published /information policy pages, genericising each activity rather than deleting it.#11105, #11025Matt's 29 April ruling bans RACS/CAPE terminology until a formal RACS agreement exists, on IP grounds. The July-2026 documents named those programmes directly and were already live days before AMC review.
2026-07-28The surgical-mortality row of the Specialist High-Level Requirements table on /cpd-activities now reproduces the published wording verbatim — "Participate in the national audit of surgical mortality by completing all surgical forms sent to the surgeon by the audit." — matching the /information rendering of the same published row cell for cell.#11082, #11057, #11025#11105 genericised this row's RACS naming on both surfaces but left the two renderings of the same published row saying different things, and the /cpd-activities phrasing was left reading "sent to Surgeon by national audit of surgical mortality". Two published, regulator-facing surfaces disagreeing on one published row is the defect class the #11057 conformance guards exist to close, so the row is conformed rather than exempted. verify-policy-fidelity.mjs is unaffected — it gates the /information contents directory, and all 13 policies remain at 100.0%.
2026-07-27Adds marketing.ac.cpd-activities-tables-match-published: both reference tables on the public /cpd-activities page reproduce their published July-2026 policy documents rather than a paraphrase. The Specialist High-Level Requirements tab now names the specialty "Pain Specialist" as published, restores the seven stripped frequency qualifiers (e.g. "Emergency Response Activity (at least 1 per year)"), keeps the published two hours columns — "Per Hour of Activity" and "Per Activity" — separate instead of collapsed into one, and leaves the Emergency Medicine leadership row's hours cells blank with its mark under Performance Review (of self), as published. The phantom seventh header column is gone, and the in-app copy of the table is held identical to the marketing copy by test.#11082, #11057This page is what a prospective member and AMC read to learn what PPP will let them claim, so a paraphrase is not good enough. The audit (#11022, #11057) found the Emergency Medicine leadership mark had been moved from "of self" to "of others" — a substantive change to which AHPRA category the requirement satisfies — with an hours figure invented where the published table deliberately leaves both cells blank, in both copies of the table at once. The frequency qualifier is the requirement, so dropping "(at least 1 per year)" understated it; and a single collapsed hours column made a value's meaning change from row to row.
2026-07-26Replaced the /information Information & Policies tab with the 13 finalised July 2026 organisational policies (16,375 words), re-authored as on-page React content rather than PDF downloads. Order is PPP's CPD Home Program Policy first, then alphabetical. Three pre-existing sections with no July 2026 counterpart (Info3 Evaluating De-Identified Appeals, Info6 Self-Assessment Criteria, Info8 Mechanisms for Informing Practitioners) are RETAINED pending Kristin's confirmation. Adds instances/marketing/scripts/verify-policy-fidelity.mjs plus the 13 extracted source texts it compares against, wired as pnpm --filter @ppp-org/marketing verify:policy-fidelity. Marks the Program-Level-Requirement wording criterion as a KNOWN DIVERGENCE and flips the spec to status: partial-drift.#11028, #11022, #11024, #11025Kristin (2026-07-14) required the finalised policies on the Information tab by end of July so AMC can review progress. On-page content rather than PDF links preserves accessibility, SEO and the mobile accordion. Transcribing 16,375 words of regulatory text by hand carries real error risk, so bulk omission is checked mechanically rather than by eye — the checker was itself corrected twice during this work after it was found to score three fully-correct components at 79.3%, 7.3% and 2.6% by ignoring data-driven tables. WHAT THE CHECKER PROVES (corrected in review — the first version of this entry, and the PR body, overstated it) is that no source word is absent from its component, and, for the two data-driven table components only, that no word appears fewer times than the source used it. That catches bulk omission everywhere, plus a deleted row, a changed CPD hours value or a flipped category marker in those two tables. It does NOT verify numeric values in prose, individual prose sentences elsewhere, or that anything was ADDED — row-level and numeric correctness for this PR was established by a separate cell-by-cell comparison (889/889 cells, 254 numeric), not by this gate. DIVERGENCE the rendered site now shows non-canonical Program-Level Requirement wording, because the source PDFs disagree with PLR_CANONICAL_NAMES and with each other. The components are deliberately NOT reworded — that is Matt's call, pending in #11024 — so the marketing spec now records the divergence rather than asserting a satisfied criterion that is no longer true. #11025 tracks RACS terminology present in the same source documents.
2026-07-22Dedicated, indexable USP marketing pages — new /for-consultants and /for-non-consultants routes reusing the existing home-page USP copy (single source in data/usp.ts) and the #9892 glass primitives, with per-route SEO metadata and sitemap registration. The home-page audience buttons keep their inline roll-out and gain a prominent "See the full page" deep-link (hybrid). Authenticated app untouched.#10840, #10436, #8307Resolves the deferred USP-pages follow-up from #8307. Direction ratified by Matt ("dedicated page for USPs") and Rob (2026-07-17 — "dedicated, indexable routes… authed app untouched"): dedicated pages beat homepage sections on SEO/discoverability while the inline reveal preserves the #9892 engagement work.
2026-07-14Waitlist signups now persist to Cloudflare KV (PPP_WAITLIST) as the durable source of truth, with a bearer-token-gated admin list/count/CSV-export endpoint — the contact form was previously email-only.#10613, #10588#10588 — a live UAT review found "Join the Waitlist" submissions were sent by email only, with no durable record, no way to list/export/count signups, and no dedupe. The KV write fails open so a missing/unconfigured binding never regresses the email send.
2026-07-09'Works everywhere you do' wearables column now shows a single watch mocking a 'You're checked in' notification (new DeviceFrame 'watch' variant, CSS/SVG-built), replacing the abstract wristband+ring illustration.#10317, #10119Matt (Dev Session 2026-07-07): the multi-device wearables illustration felt too futuristic/corporate; asked for 'just a watch to start' with a mocked check-in notification.
2026-07-09FAQ accordion question headers pick up the same navy-tinted glass fade (GLASS.surface.dark/border.dark) as the GlassSection hero above them, instead of flat white MUI-default blocks.#10313, #10121Matt (Dev Session 2026-07-07): the solid-color accordion headers looked inconsistent next to the light-blue faded hero — asked for 'a little bit of refinement to give something similar.'
2026-07-09Hero doctor avatar cluster regenerated: the 4 AI-generated portraits now show doctors in navy scrubs instead of white coats, same people/poses/background and same race/ethnicity diversity preserved.#10148Matt (WhatsApp 7 Jul 2026): white coats read as 'very American' — Australian doctors wear scrubs; match the app login/sign-up screens. Regenerated via image-to-image edit on the Generative Language API (gemini-2.5-flash-image; doctor-1 on gemini-3.1-flash-image after a repeatable safety refusal).
2026-07-07Floating 'Join the Waitlist' CTA rolls with the user after the hero scrolls away; pre-launch contact surfaces (home section heading, form notice, submit button, success message) made unambiguous that submitting joins the waitlist; CTA copy unified to 'Join the Waitlist'.#10155, #10122Matt's Dev Session feedback (2026-07-07): CTA was only at the very bottom of the page, and the generic 'Contact' form read like a support enquiry, not a waitlist signup. Pop-out modal variant deferred as Open Question 10122a.
2026-07-07Offerings tiles copy rewrite (CPD Home / PPP Full Platform inclusion descriptions, equal-height tiles, new privacy line) and "See it in action" preview bullet fix.#10154, #10135, #10138Matt's website copy review flagged stale/incomplete tile copy and asked for both tiles to read as complete, comparable feature sets and to be visually the same length. Price figures were deliberately excluded — that part of the review is tracked separately on #10117 pending Matt's GST-inclusive pricing decision.
2026-07-07Corrected the CPD Activities sticky-header AC to match the mobile fix — the TableContainer now forces overflow:'visible' at ALL widths (not overflowX:'auto' at xs), and the sticky top composes the staging-banner-aware HEADER_OFFSET_PX instead of the bare 90px nav offset.#10145, #10144, #10120#10141's per-breakpoint overflowX:'auto' at xs was itself a scroll container below md (the CSS overflow spec coerces the other axis away from 'visible'), re-trapping the sticky header off-screen on phones — the #10120 bug back on mobile (#10144). The AC still documented that broken mechanism, so it directly contradicted the shipped fix and had to be rewritten, not bypassed. Added .sources/issue-10144.json for the new src: citation.
2026-07-07Rewrote the CPD Activities sticky-header AC — the table header now freezes against the page nav with a single page scroll bar (page-level position:sticky at top: HEADER_SCROLL_OFFSET_PX, overflowX:'auto' scoped to xs only), superseding the #9892 "docking panel" (nested position:sticky box with bounded maxHeight+overflow).#10141, #10120, #9892The #9892 docking-panel implementation the AC documented produced two scroll bars and stuck the header to the panel's inner scrollport instead of the page (#10120). The AC explicitly recorded page-level sticky as tried-and-rejected, so it directly contradicted the shipped fix and had to be rewritten, not bypassed. Added .sources/issue-10120.json for the new src: citation.
2026-07-04Reconciled 4 stale #8307 ACs (lines on the "For Consultants"/"For Non-Consultants" USP sections and their motion) against the current #9892 implementation#10036, #9892, #8307Found while cleaning up the #9892 worktree that the code:/behaviour claims had drifted from the code — the buttons no longer "scroll to" USP sections (they roll out inline via a shared UspPanel + MUI Collapse, per the "navigation flow" AC added earlier in the #9892 rollout), the code: citations pointed at ConsultantsSection/NonConsultantsSection components that #9892 folded into UspPanel and removed, and the benefit lists were claimed to stagger in via staggerContainer/fadeUpItem variants that UspPanel never uses. Corrected the wording and citations rather than leaving the spec silently wrong.
2026-07-02Home hero replaced with an iOS-glass ImmersiveHero (editorial serif headline, two-tone atmosphere, scroll parallax/exit motion, Gemini-generated non-clonable dashboard artwork)#9892Wow-factor redesign for prospective doctor users (#9892). Consolidates the previous hero's verbose tagline stack (#8307 — "Life-Long CV Builder", "Real. In-Time. Accurate.", the two body paragraphs) into the new hero's more restrained copy; preserves #7907's career-long value-prop line as the literal kicker above the h1, and folds "By Doctors, For Doctors" into the subtext. The white banner, audience CTAs, and two-product cards (#7904) are unchanged. The social-card strapline ("AMC-Accredited CPD Home. Performance &amp; Wellbeing...") remains verbatim in index.html meta tags (#7671/#7379) but is no longer duplicated in the visible hero body.
2026-07-02Added a diverse AI-generated doctor avatar cluster to the hero as a social-proof element#9892Rob asked for AI-generated doctors of alternate race/ethnicity, inspired by BdHealth's "available doctors" pattern but restyled to our dark navy palette instead of light teal. Portraits are gemini-2.5-flash-image generations, not real people; no unverified statistics are claimed in the copy pending Matt's review.
2026-07-02Broadened hero copy beyond CV-building; rebuilt "See it in action" with real screenshots and glass 3D scroll tilt#9892, #7908Rob flagged the hero subtext over-indexed on CV-building versus Matt's broader Features list — now names CPD, Logbook, and Wellness explicitly. Separately, "See it in action" was found to be showing mislabeled generic UI-kit template mockups rather than the real product; replaced with genuine CPD Home and Surgical Logbook screenshots inside a new GlassScreenFrame component (dark glass panel, scroll-linked 3D perspective tilt, ambient glow) instead of the previous flat white card.
2026-07-02CssBaseline font-baseline fix, count-up stats, Features marquee, Consultants/Non-Consultants scroll motion#9892Rounding out the #9892 motion/polish pass per Rob's review of the live build — fixed a real bug (nav bar rendering in Times New Roman due to missing CssBaseline), added scroll-triggered count-up to the "Bridging the unmet need" stats, turned the static 11-item Features grid into a dual-row auto-scrolling glass marquee ("an inspiring way to get the message across"), and added scroll-reveal stagger motion to the Consultants/Non-Consultants USP sections.
2026-07-02Two products, one mission" cards now use real screenshots, distinct from "See it in action#9892, #7904Rob asked for the blurred placeholder images to be replaced with real ones, then flagged that both this section and "See it in action" would show near-identical screenshots back-to-back. Resolved by using different real screens per section (CPD Plan + PPP Dashboard overview here, vs CPD Home dashboard + Surgical Logbook in "See it in action").
2026-07-02Product cards now reuse the "See it in action" screenshots directly#9892, #7904The initial distinct-image picks showed the wrong content (a CPD Plan sub-page instead of the CPD Home dashboard; an onboarding checklist instead of real platform content). Rob asked to just reuse the already-vetted preview-cpd-home.png/preview-ppp-full.png images rather than sourcing new distinct ones.
2026-07-02Added "Works everywhere you do" cross-platform section (desktop/mobile/wearables)#9892Rob flagged that the redesign was missing the key cross-platform message. Real screenshots inside literal device frames for desktop/mobile; an abstract Gemini-generated glass visual for wearables (Whoop/Oura are data sources syncing into PPP Pulse, not platforms PPP has a native screen on, so a fabricated fake wearable-app screen would misrepresent the product). Static 3-column layout rather than a carousel since only 3 categories need showing.
2026-07-02Applied full critical-review pass — visual consistency, unified CTA button system, typography system, narrative resequencing#9892Rob asked for a critical review of the redesign's flow and brand consistency. Findings applied in the same pass — restyled the one section still using pre-redesign styling, unified every CTA button under a shared PillButton component, extended Fraunces to all section headlines, fixed a two-headlines-stacked issue, ensured the hero always has a visible CTA, and resequenced the page to lead with the problem before the product pitch.
2026-07-02Inline USP accordion, product-cards reposition, atomic-design primitives, device hover-tilt, SEO/AEO pass, responsive overflow fix#9892Rounding out the #9892 redesign per Rob's rapid-iteration review — fixed the buttons jumping past the pricing cards (now an inline roll-out), moved pricing cards after Features, introduced shared GlassSection/SectionHeading/GlassIconCard primitives for easier re-skinning, added 3D hover interactions to the device frames, added structured data/canonical/llms.txt for search and AI answer engines, and fixed a genuine horizontal-overflow bug found across a 5-breakpoint responsive audit.
2026-07-02Brought CPD Activities page (/cpd-activities) on-brand with the glass redesign#9892Rob asked to "smarten up" the CPD Activities page to match the new brand. First real-world reuse of the GlassSection/SectionHeading/PillButton primitives outside Home.tsx — hero, toggle, and table wrapper restyled; table internals left untouched since legibility matters more than decoration for dense compliance reference data.
2026-07-02Redesign CPD Activities table on brand tokens; revert Fraunces (not an approved brand asset); add CLAUDE.md Brand & Design System Guardrail#9892Rob pushed back twice — "is that the best we can do?" on the CPD Activities table (still raw hex pastels and black borders after the first on-brand pass), and "is that part of the approved brand kit?" on the Fraunces serif used across every heading. Both fixed; the Fraunces incident is now codified in CLAUDE.md so future design decisions get checked against docs/features/design-system.md before spreading across a session.
2026-07-02Sticky table header + docking scroll panel on CPD Activities table#9892Rob asked for the table header to stay visible while scrolling, then clarified the hero itself should scroll away normally while the table panel docks below the nav to use the full viewport. Page-level sticky hit a real CSS overflow-vs-sticky-containment conflict with MUI's TableContainer; resolved with a bounded scroll panel (the standard MUI sticky-table pattern) instead.
2026-07-02Halve CPD hero height (GlassSection dense variant); align Information/News/FAQs onto the same hero#9892Rob asked to halve the CPD Activities banner height, then align it with Information/News/FAQs so every secondary page looks consistent — those three pages had three different (and in two cases hero-less-on-mobile) treatments before this pass.
2026-06-30UX pass — tighten hero hierarchy and remove duplicate copy#9867, #9826White-banner descriptor lines demoted to overline + body1 to give "Take Control of your professional existence" clear visual dominance; CTA buttons differentiated (solid vs outlined); duplicate "Performance. Wellbeing. AMC Accredited CPD Home." subtitle removed from navy hero (covered verbatim by the strapline below); vertical padding tightened; "Built for doctors" overline added above Features heading.
2026-06-29Added "See it in action" functionality preview section with tabbed screenshots (CPD Home / PPP Full Platform) so prospective users can visualise the product before full walkthrough videos exist.#9772, #7908Surfaced in Kristin's demo-walkthrough feedback (29 May 2026) — prospective users needed a sneak-peek of platform functionality before how-to videos are available.
2026-06-29Add plain-English descriptions to jargon-heavy plan inclusion items on the home page pricing cards.#9767, #7905Named features (GeoSmart timesheets, Two-step verification, Increased awareness. Superior performance., etc.) lacked explanation — surfaced in Kristin's demo-walkthrough feedback. PPP team decision 2026-06-22 to add concise explainers; copy drafted by engineering, approved by Matt before go-live.
2026-06-24Homepage refreshed to lead with doctor value — banner headline "Take Control of your professional existence" plus two audience CTAs (For Consultants / For Non Consultants), a reframed navy hero tagline block, new For-Consultants and For-Non-Consultants USP sections, and a Features section.#9211, #8307Matt's direction (#8307, Google Doc 24 Jun 2026) — reframe the marketing site away from enterprise/compliance language ("A high-performance approach to the workplace", "seamlessly fulfill regulatory requirements") and toward doctor value: independence, granular data ownership, give time back. Standalone user-specific USP routes deferred to a follow-up; the banner buttons scroll to in-page USP sections for this slice. Copy is engineering's faithful rendering of the Doc — Matt approves final wording before go-live.
2026-06-21Home hero foregrounds the career-long value proposition — the lead-in copy "One platform that can carry you along your entire medical career" now renders as small text above the "Professional Performance Portfolio" title, within the navy hero band.#9041, #7907Surfaced in Kristin's demo-walkthrough feedback (29 May 2026); Matt's verbal "career-long platform" framing was a strong value proposition not conveyed in the existing copy. Matt confirmed the exact wording and placement ("above professional performance portfolio but still in the navy; small text") on #7907. No existing hero copy, pricing, product cards, or CTA changed — only the new lead-in line was added.
2026-06-19Landing-page product language aligned with in-app terminology — the full product is "PPP Full Platform" everywhere (hero card, sign-up CTA; pricing tile was already correct) and the inclusion list now surfaces the Passport as "Recruitment Compliance Passport" rather than the internal "PPP Passport" name.#8909, #7903Surfaced in Kristin's demo-walkthrough feedback (29 May 2026) — the website and app used different product language so they read as different products. Matt's 2026-06-03 decision on #7903 set the canonical naming (Q1=A "PPP Full Platform", Q2=B describe the Passport as "Recruitment Compliance Passport"), scoped to terminology only (Q3=B); the other Kristin-raised copy items are deferred to sibling issues.
2026-06-18Home pricing-card inclusion lists reordered by universal relevance to doctors — broadly-useful, common-to-all items first; person-specific or niche items last. Copy-only sequence change; the PPP Full Platform list keeps "All CPD Home features included" first and surfaces GeoSmart timesheets high.#8882, #7906Surfaced in Kristin's demo-walkthrough feedback (29 May 2026); Matt approved the universal-relevance ordering approach (2026-06-09). No inclusion text, pricing, plan structure, or CTA changed — only the array order in instances/marketing/src/landing/pages/Home.tsx. Final rank is editorial (for-discussion) so Matt can re-rank as a non-blocking fast-follow.
2026-06-17Sharpened the two-product distinction on the marketing home hero — CPD Home and the PPP Platform now appear as two distinct side-by-side product cards, each led by a large &lt;h2&gt; product heading with a kicker label and a distinguishing accent colour.#8833, #7904Kristin's demo-walkthrough feedback (29 May 2026) flagged that it was not clear there are two separate products; the prior offering boxes used small 16px h6 headings. Matt confirmed side-by-side cards with his verbatim one-line descriptions on #7904.
2026-06-17Updated the marketing strapline to "AMC-Accredited CPD Home. Performance & Wellbeing. Build a living, lifelong CV — every case, course and reflection, captured as you work." across the home hero, the &lt;meta name="description"&gt; Google-search/SEO tag, the OG / Twitter share-card descriptions, and the OG-image generator.#8779, #8423Matt's chosen Google-search line (#8423) leads with AMC accreditation and the lifelong-CV value proposition, replacing the prior "Performance. Wellbeing. CPD Home. The professional infrastructure for doctors." strapline.
2026-06-02FAQ, Information and Home pricing copy shown GST-inclusive; $165 review/appeal fee now consistently incl. GST.#8078, #8069, #8059B2C GST-inclusive decision (#8069); resolves the $165 ex/incl inconsistency (#8059).
2026-06-02FAQ, Information and Home pricing copy set to $275 AUD ex GST; removed stale 'no fees in 2026' line; Home cards now derive price from PLAN_PRICES.#8058, #8057AMC review of the public site (Matt) — consistent ex-GST pricing across faqs and information pages.
2026-05-28Marketing Header — desktop nav (including the Login button) now stays visible at 1024 px and above via a custom desktopNav MUI breakpoint, instead of collapsing to the hamburger menu at MUI's default lg (1200 px).#7839, #78131080 px is a common laptop / presentation-screen width and the previous behaviour hid the Login CTA behind an extra click, hurting marketing conversion and the live demo flow.
2026-05-27Marketing spec created; social share-card aligned to the "Performance. Wellbeing. CPD Home. The Professional Infrastructure for Doctors." strapline and OG image regenerated with the approved emblem-only mark.#7671, #7379, #7537PR #7537 updated only the browser-tab strapline (#7379); the Open Graph / Twitter card still carried the retired "Whoop for the Workplace" copy and an off-brand "PPP" circle. Brought the share card in line and added a reproducible generator.

Internal documentation — org members only