Cocktail Hub, Education Section + Tequila Quiz, and Design Uplift

Diff main vs staging and each in-flight design branch to establish what polish is already done; curl prod HTML to confirm live state. Map proposed nav/IA changes, inventory design-system defects, enumerate the exact polish page set. Output is a markdown artifact (optionally on an internal URL).

staging is ~92 commits ahead of prod with several design branches already staged — this unit is what stops us redoing merged work.

You review the artifact and confirm IA + polish scope + which in-flight branches to land. The "done vs. to do" split is explicit.

Consolidate the accent system onto the existing warm-neutral tokens (ink / cream / warm-gray). Replace every brand-gold usage (5× additive-free, 4× cocktail, 3× where-to-find-us) with an intentional neutral token — not brand blue. Introduce a small semantic type scale to start retiring the arbitrary size sprawl; migrate hardcoded heading hex. Tokens only — no restyling yet.

Previously-invisible brand-gold accents now render as intentional neutral tokens; dark theme resolves without contrast regressions; no blue introduced as a page accent; no existing page changes color unintentionally.

No undefined brand-gold class remains; the accent system is neutral (blue not spread); type-scale utilities exist; site builds clean.

Convert arbitrary type sizes to the U2 scale, normalize spacing, tighten hero/imagery, apply consistent motion. Land any already-good in-flight branch work from U1 rather than redoing it. Ship to staging. Brand lock untouched.

Each page renders correctly mobile/tablet/desktop; age-gate still fires first; slogan lockups + logo unchanged; no gold reintroduced; no em dashes.

You review on staging and approve; visual consistency across the set; CLS not regressed.

Build 2–3 visually distinct directions (e.g. bold-editorial, cinematic-hero, product-forward), each a full noindex route on staging, all inside the brand palette (black / white / warm-cream; brand blue sparing only, never dominant). Concept imagery via imagegen (never bottle renders).

Each concept renders end-to-end and responsive; concepts carry noindex and are absent from the sitemap; they don't alter the live homepage or shared components.

You click through all concepts on staging and pick a direction. Building the winner is deferred follow-up.

Extract recipe data into a data module keyed by slug, seeded from the documented serves. Build a hub grid grouped by expression (Blanco / Reposado / Añejo). Complete the D5 checklist for the hub and every recipe — replace the broken prerender entry with a loop so each recipe ships a non-empty body.

Only publish recipes with approved names — hold the 2 unnamed Blanco serves + Extra Añejo (no signature serve) behind a content gate until you name them.

Hub lists all published recipes; curl of each recipe shows a populated body (not the empty shell); sitemap includes hub + published recipes; OG resolves; existing 3 recipes still render with Recipe schema.

All published recipe URLs prerender non-empty bodies; hub linked from nav; no soft-404; you approve the hub on staging.

Build a /learn hub with cards for each topic — the additive-free explainer, the quiz, and stubs for future topics (how to taste, agave/NOM basics). Complete the D5 checklist. Internal-link from homepage + footer to build the education entity cluster (helps sitelinks).

/learn renders topic cards; prerenders a non-empty body; appears in sitemap; additive-free still works and links back.

/learn is indexable and linked from nav + footer; you approve on staging.

Net-new multi-step flow (useState + shadcn radio-group + progress + button). ~6–8 questions, a scored result screen with a shareable summary, and an email-capture CTA on the result. The prerendered body carries a crawlable summary so it ranks + unfurls. Question copy drafted by Martin, approved by you before publish.

All-answered → correct score + result tier; no-answer disables next; back preserves answers; already-subscribed / invalid email handled; route prerenders + OG unfurls; capture records source: 'quiz'.

Quiz completes end-to-end on staging; score logic correct; capture reaches the subscriber table; you approve copy + UX.

Add 'quiz' to the valid capture sources (no migration). Add a quiz CTA block into the Welcome email builder. Because this edits approved-verbatim subscriber copy, the new CTA is approval-gated — you see the rendered email on the internal email surface before deploy. Follow the email-rendering gotchas; a dedicated drip step waits for drip activation.

A quiz signup writes source='quiz' + triggers the Welcome email; CTA renders in Gmail light + dark (readable link, no inverted-logo seam); existing sources unaffected; GA4 receives a capture event.

Test capture shows source='quiz'; Welcome email QA'd on real Gmail + internal surface and approved by you; GA4 DebugView shows the event.