Purpose: a practical guide to the primary screens and their connections. Read alongside the main handover. Reviewed 11 September 2026.
Evidence key: Live = observed in the deployed UI; Source = current implementation reviewed; Intended = documented future behaviour; Reference = existing design prototype. Screen states described from source are not claims of end-to-end production verification.
flowchart LR
Public["Landing /"] --> Start["Start /start"]
Public --> Login["Sign in /login"]
Start --> Calendar["Calendar /club"]
Login --> Calendar
Calendar --> Add["Add people /club/add"]
Add --> Review["Review people"]
Review --> Calendar
Calendar --> Profile["Person profile"]
Calendar --> Confirm["Current: gift review / confirm"]
Profile --> Message["Birthday-message draft"]
Calendar --> Message
Calendar --> Account["Your details"]
Profile --> Requests["Share birthday / address / wish link"]
Requests --> Guest["Guest completes request"]
Guest --> Profile
Confirm --> Checkout["Shopify checkout"]
Checkout --> Complete["Confirmation / return / recovery"]
Calendar -. "Intended" .-> Shop["Collections shop"]
Shop -. "Selected product" .-> Confirm
The live interface uses the wordmark, back links, person-specific actions, and an account/settings control. Keep users oriented when a deep link starts them partway through a journey.
Route: / · Audience: visitor · Evidence: Source; the signed-in live visit redirects to the calendar.
Job: explain the reminder service, the freedom to decide each time, and the next step. Primary action: Start your calendar. Existing members can sign in.
Current source includes the service promise, free membership, how it works, product examples, delivery information, referral offer and first-paid-gift welcome card. The September 7 design reference introduces stronger imagery and an example reminder.
Design: make the reminder-and-action loop tangible early. Keep membership, gifting cost and benefit conditions easy to separate. Ensure the page agrees with acquisition creative and the welcome message. Signed-in redirect and narrow mobile layouts are part of the screen contract.
Route: /start · Audience: new member · Evidence: Source.
Sequence: enter names/dates → review and correct → save your list → mobile/reminder choice → texted code → verified account and saved calendar.
A missing birth year is normal. A person with no known day/month can remain on the list for a later request. Invitations may prefill the inviter. Authentication is deferred until the list has value to the visitor.
States to design: empty input; mixed known/unknown dates; impossible date; corrected row; removing an unsaved row; code sent; code expired/incorrect; resend/change number; sending failure; saved confirmation; no usable reminder channel. Returning to the list should preserve work.
Content requirement: describe exactly what is saved and which dates can produce reminders. A mobile used for a sign-in code does not, by itself, establish permission for reminder texts.