Bin Collection app (UI reference)
Visual reference for the polished Bin Collection app (PR #17+). Screenshots are captured from the #/bins route on a tablet-width viewport (~1024px), owner and house sitter modes.
Screenshots
| File | Description |
|---|---|
docs/images/bin-collection-owner.png | Owner mode — collection information, hero, timeline |
docs/images/bin-collection-house-sitter.png | House sitter mode — same hierarchy, informative copy |
After UI changes, refresh screenshots:
- Run
npm run devand openhttp://localhost:5173/#/bins. - Capture owner mode, then switch to house sitter in Settings and capture again.
- Save PNGs to
docs/images/using the filenames above.
Layout (top to bottom)
- Collection information — single block (6am, Wagtail Road location).
- Next collection hero — type → date → relative time → bin line; Lucide icon and subtle council colour accent.
- Summary cards — next household and next garden waste (garden card visually secondary).
- Upcoming collections timeline.
- Missed bin note (easthants.gov.uk).
- Brown bin collapsible (accepted / not accepted with icons).
- Council recycling guidance ↗ — external EHDC link.
The Home dashboard card for Bin Collection is unchanged; only the full app view is documented here.
See also bin-collection-maintenance.md for schedule data updates.
Guest mode and non-production hostnames
On sandbox, test, demo, and other non-production stacks, guest / house sitter mode must not show the bundled owner home bin calendar (Wagtail Road demo schedule shipped in the repo for owner QA). That leak looked like “guests see our real collection dates” on *.lovely-hub.com test hubs even though the bug was client-side fallback logic, not cross-hub D1 or shared Worker data.
Fix (app): bin schedule resolution uses usesBundledOwnerHomeBinFallback() together with runtime-config.json → hubEnvironment (from scripts/write-hub-runtime-config.mjs at hub Pages deploy). Bundled owner-home data is only used when the hub is intentionally vanilla (test / staging / sandbox / demo) or when the profile has no configured schedule — not for named customer site ids on sandbox hostnames.
Operator check: open #/bins in guest mode on a disposable hub; dates should match the hub’s profile or empty/setup state, not the default owner-home CSV. Redeploy hub Pages after manifest or hub_environment changes so runtime-config.json matches the Wrangler env.