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

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

P7. Brand coherence and PLAN gaps

Accepted, not fixed