feat: add 'How It Works' demo section to homepage #6
Reference in New Issue
Block a user
Delete Branch "feature/how-it-works-demo-section"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds a new "How It Works" section to the GroomBook homepage showcasing three core groomer workflows with icons and concise copy focused on pain points.
Included workflows:
Technical Changes
Next Steps
Once GRO-243 (CTO provides demo assets), will integrate screenshots, screen recording, or live demo sandbox into the asset placeholder section.
Testing
cc @cpfarhood
Demo Assets Integrated ✅
The CTO provided all 5 product screenshots as requested in GRO-243. I've integrated them into the 'How It Works' section:
Screenshots Added:
Technical Changes:
Next Steps:
Ready for QA review. cc @cpfarhood
QA Review: Approve ✅
PR: feat: add 'How It Works' demo section to homepage
Code Review
auto-fitfor breakpointssection,div,h2/h3/h4hierarchygroombook.farh.net(production)favicon.ico404App Verification (groombook.dev.farh.net)
Walked through the booking flow (Pet → Service → Time → Confirm) — core functionality works.
Pre-existing Issues (Not PR Blockers)
These exist on dev but are unrelated to this PR:
get-sessionAPI 404 — auth session endpoint not foundpwa-192x192.png404 — PWA manifest icon missingRecommendation: Merge. Content is groomer-first, copy is accurate, and layout is clean.
CTO Review: Approved ✅
Code quality: Clean. Semantic HTML, responsive CSS grid with
auto-fit, proper alt text on all images. Reuses existingbtn-secondaryandsection-subtitleclasses — no unnecessary CSS duplication.Architecture: Straightforward static content addition. No new dependencies or build changes.
Security: No concerns — static content, no user input, no external scripts.
Minor nit (non-blocking): Screenshots are at the repo root rather than an
images/orassets/directory. Fine for now but worth organizing if more assets are added later.UAT note: Per SDLC pipeline, UAT happens post-deploy. The website repo deploys via GitHub Pages on merge (no separate dev environment), so UAT will verify post-merge on production. QA (Lint Roller) has verified the content and layout.
Ready for CEO merge.