Review of Crema Crew deliverables
Method: headless Chrome screenshots of all three deliverables (desktop and mobile), a 375px iframe probe that measures real horizontal overflow, node checks of the quote logic, and a read of each file against PLAN.md. Note: a plain 375px headless screenshot is clipped by Chrome's minimum window width, so mobile layout was measured with the iframe probe instead.
Priority-ordered problems
P1. Dashboard overflows horizontally on mobile (real, measured)
At 375px the page is 688px wide. The stat cards, charts and tables get cut off on the right. Cause: the dashboard content grid has no min-width: 0, so the 640px schedule and wide table force the column wider. Violates the "responsive" brief and PLAN section 3.
P2. Dashboard numbers contradict each other
Stat card revenue ($7,785) does not equal the revenue chart total ($9,505); utilisation chart, roster hours and the stat card were three unrelated hand-typed sets. A business owner would stop trusting every figure. Fix: derive revenue, utilisation and barista hours from the one bookings list.
P3. Landing page vertical rhythm is broken
.wrap sets padding: 0 x, which beats the section padding, so How it works, Manage, Quotes and FAQ lose all vertical spacing. Headings touch the section above (visible: "Three steps" against the demo, "Good questions" against the testimonials). Hurts hierarchy across the whole page.
P4. Dashboard is not on-brand by default and some content is illegible
- It opens in dark mode on dark-preferring systems, but the brand is warm and light first (PLAN section 2).
- Pending schedule blocks use 70% opacity, which makes their text unreadable (Bluebird Studio).
- Buttons are rounded rectangles; the brand says pills (style guide, landing).
- Chart value labels float at the top of each column instead of sitting on the bar, so values are hard to read against bars.
- The roster's progress bar and hours text wrap onto separate rows, leaving the status and hours misaligned.
P5. Dashboard usability is thin
No way to filter bookings by status, no count of what needs action, and on mobile the table hides the service entirely. A rosterer's first question is "what is pending?"; there is no answer short of reading every row.
P6. Landing interaction and accessibility gaps
- Option groups use
role="radio" without arrow-key behaviour (a broken ARIA promise). Use toggle buttons with aria-pressed.
- After "Confirm booking", focus stays on a now-hidden button; the confirmation is not announced or focused.
- Stats are
0 without JS and mid-count in a screenshot; set real values in the markup.
- Global
:focus-visible forces border-radius: 6px, which makes pill buttons turn square when focused.
- In reduced motion the steam animation runs once and ends invisible, so the illustration loses its steam entirely instead of showing it static.
- Typography details:
x and - used as multiply and minus, straight quotes in testimonials.
P7. Brand coherence and PLAN gaps
- PLAN promises pricing information on the landing page; there is none beyond the quote.
- Services use generic icons (a calendar for "Pop-up bar"); the imagery plan called for cup/cart illustrations. The hero is the only illustration.
- The style guide says "Ember is the only action colour" but buttons use Ember Dark. The guide also has no dashboard mapping, no token names table and no dark-mode palette, so "one design system, three deliverables" is not demonstrated.
- The landing nav has no mobile menu (links are hidden under 860px).
Accepted, not fixed
- Landing mobile nav shows only the CTA; with a single-page layout and a sticky CTA this is acceptable. Noted for a later menu.
- Dashboard is sample data only, with no booking actions (assign, confirm): out of scope per PLAN assumption 6.