Doppio: brand, structure and build plan

Nobody was available for questions, so every open decision below is an assumption, marked (A). Change them freely; the tokens in shared/tokens.css make a re-skin cheap.

0. Assumptions

1. Brand

Positioning. "The barista booking app for people who host." Booking a barista should feel as easy as booking a table, and as warm as the coffee. Competitors are phone calls, quote forms and generic event marketplaces; Doppio is instant availability, fixed pricing, and a person you can see.

Audience.

  1. Hosts (primary): office managers, EAs, wedding and event planners, people planning a birthday or launch. Time-poor, mobile first, want certainty (who arrives, when, what it costs).
  2. Tasters: small groups booking a private tasting (4 to 12 people). Curious, gift-minded.
  3. Operators (dashboard): the catering company owner and rosterer. Want fewer double bookings, visible utilisation, quick roster decisions.

Promise. Pick a day, pick a barista, done. We bring the cart; they bring the craft.

2. Brand elements

3. Information structure

Landing page (one page, scroll story)

  1. Nav: wordmark, How it works, Experiences, Pricing, "Book a barista" button.
  2. Hero: headline, sub, primary CTA, secondary "See how it works"; right side animated cup/steam illustration plus a floating booking card that cycles through states.
  3. Social proof strip: counts (events poured, cups served) with count-up, venue types.
  4. Interactive booking preview (the core sell): 4-step widget (experience, date and time, setup, confirm) with live price and a confirmation animation. Fully working in vanilla JS.
  5. How it works: 3 steps with scroll-driven reveal.
  6. Experiences: Office mornings, Events, Private tastings (cards with tilt/hover).
  7. Manage it all: app features (reschedule, add guests, chat with barista, invoices), shown as an animated appointment-card stack.
  8. For operators: one band teaser for the dashboard (utilisation, roster).
  9. Testimonials, Pricing (3 tiers, monthly/per-event toggle is out of scope; per-event only), FAQ accordion.
  10. Final CTA and footer.

App information architecture (customer app, described; dashboard is built)

Home (next booking, quick rebook) / Book (flow above) / Appointments (upcoming, past, detail with reschedule and cancel) / Messages / Account.

Dashboard (business side, built)

Sidebar: Overview, Bookings, Schedule, Roster, Customers (stub label only), Settings (stub). Built views: Overview (stat cards: revenue, bookings, utilisation, avg. rating; revenue chart; upcoming bookings table), Schedule (week calendar grid by barista with booking blocks), Roster (barista cards with availability and status). Bookings is the table with filters/status badges, reachable from Overview and sidebar. Hash routing, no router dependency.

4. Personality and voice

Personality. Warm, unfussy, quietly expert. A friendly head barista: knows the craft, never snobbish. Confident short sentences, small jokes, never puns on every line.

Tone dials. Marketing: playful 6/10. Booking flow: calm and clear 3/10 playful. Errors: plain and kind, no blame, say what to do next. Dashboard: efficient, numbers first.

Rules. en-AU. Sentence case. No exclamation marks except the confirmation moment. No em-dashes. Say "barista" not "service provider", "booking" not "reservation".

Sample copy.

5. Shared design system

shared/tokens.css is the single source for static pages (CSS custom properties: colour, type, space, radius, shadow, motion). The dashboard maps the same values into shadcn variables (oklch) in dashboard/src/index.css. Style guide documents both. Spacing is a 4px base (4, 8, 12, 16, 24, 32, 48, 64, 96). Radii: 8 / 14 / 22 / pill. Shadows are warm (espresso at low alpha).

6. Deliverables and build order

  1. shared/tokens.css, shared/base.css (components used by the style guide and landing: buttons, badges, inputs, cards).
  2. style-guide/index.html: tokens, colours, type scale, spacing, radii, shadows, components, icons, motion demos (with replay), voice and copy.
  3. landing/index.html + landing.css + landing.js: sections above, reduced-motion support, responsive at 360, 768, 1280.
  4. dashboard/: theme, sidebar layout, Overview, Schedule, Roster, mock data; typecheck and build pass.
  5. Verify: serve at 127.0.0.1, run dashboard build, screenshot-free checks (HTML validity, console errors via headless if available).

Execution detail was kept in a separate task plan (not included).

7. Non-goals

Real payments, auth, backend, the customer app itself (only described and previewed on the landing page), imagery photography, i18n.