Critical review
Reviewer stance: senior brand and product designer, checking all three deliverables against PLAN.md and against each other. Evidence: full-page captures at 1440 and 375 (light and dark for the dashboard), a design-rule detector, a fresh finish review, and reading the code.
What holds up: one coherent world (cobalt, crema, ink, milk) carried across all three surfaces; a hero that demonstrates the product; plain, consistent copy and numbers (the $540 and $1,380 quotes match across landing, style guide and logic); status always shown by word and shape; the dashboard is scannable at a glance.
Problems, most important first. "Fixed" means changed in this pass (see CHANGES.md).
- Local preview links were stale (delivery). The preview servers had stopped or been displaced; restarted on fresh ports.
- Dashboard: the primary action "New booking" did nothing. A dead primary button in an operator tool destroys trust. Fixed: it opens a side sheet with a real form (client, experience, day, start, length, guests, venue) that adds a pending, unassigned booking, validates guest limits using the same rules as the landing, and surfaces in the alert, schedule and table.
- Dashboard: assignment is silent and irreversible. "Assign next" and "Assign" changed data with only a transient note and no undo. Fixed: the note now carries an Undo button that restores the previous state.
- Landing accessibility: selection groups were announced as radios but did not behave like radios.
role="radio" buttons were all tab stops with no arrow-key support. Fixed: single-select groups now use role="group" with aria-pressed buttons, which is honest semantics for what they do.
- Landing accessibility: the auto-scrolling drink marquee had no way to pause except hover (fails WCAG 2.2.2 for content moving over 5 seconds, and is unavailable on touch). Fixed: a visible pause/play button.
- Landing: anchor targets hid under the sticky header (every nav link and CTA landed with the heading clipped). Fixed with
scroll-margin-top.
- Landing: the operators CTA ("Get early access") scrolled to the customer booking widget. Wrong promise for the audience and a copy/behaviour mismatch. Fixed: an inline operator sign-up (email field, validation, local confirmation, clearly marked as demo, nothing sent).
- Brand coherence: dashboard card titles were not in the display face. shadcn's
CardTitle is a div, so the h1-h3 rule never applied and titles rendered in Geist 500, flatter than the brand voice and inconsistent with the landing and style guide. Fixed by styling [role=heading] with the display face.
- The style guide did not cover the third surface. No schedule block states, no status legend, no token-to-shadcn mapping, no focus or accessibility notes, so the "one design system" claim was only half documented. Fixed: a new "Dashboard and accessibility" section with schedule block states, the shadcn variable mapping table, focus ring and target size rules.
- Dashboard mobile header truncated the greeting ("Good morning,...") and the "now" line crossed block text on the in-progress booking. Fixed: the title collapses to "Overview" on small screens, and the now marker sits behind block content.
- Dashboard navigation did not reflect scroll position. "Overview" stayed highlighted wherever you were. Fixed with an observer that updates the active item.
- PLAN.md drift. The plan still said some nav items were stubs and described the hero cup as an icon in the ticket. Fixed.
Not fixed, deliberately (disclosed):
- No photography or real brand imagery; vector illustration only.
- Landing has no mobile navigation menu (single-page, short; the sticky CTA stays available).
- The two dashboard navigation entries, Bookings and Revenue, remain anchors on one page rather than separate screens.
- The booker is a front-end preview, not connected to a real backend or payments.
npm run lint still has the one pre-existing error in the shadcn-generated use-mobile.ts.