Doppio: brand, system and build plan

Kind: software (a booking app). Deliverables: style-guide/, landing/, dashboard/, one shared design system.

0. Assumptions (nobody was available to ask)

  1. Name. The brief gave none, so I coined Doppio (a double espresso: two of everything, a barista plus a setup). Not trademark searched (no way to do that offline). Swap it in one place per deliverable if it clashes.
  2. Market. Australia: en-AU spelling, AUD, 24-hour-free 9:30 am times, ABN-free copy. Prices are illustrative and marked as assumed in the build.
  3. Two sides, one product. Customers book and manage appointments in the app. Businesses (the coffee operators) run the dashboard. The landing page sells the customer app, with one line for operators.
  4. Offer. Three bookable setups: Cart (compact, up to 60 guests), Bar (full counter, 60 to 200), Tasting (a private, guided flight for 6 to 14). A booking is a barista, a setup, a window of time and a place.
  5. Pricing shape. Hourly barista rate plus a setup fee plus per-guest cup allowance, 2-hour minimum. Shown as a live quote. All numbers are placeholders.
  6. No photographs. There is no photo library offline and no client photography. The landing page leads with the real product UI built as live HTML (the software rule), plus drawn product-specific SVG for setups. Real photography of carts, bars and baristas is a client supply item.
  7. No invented proof. No testimonials, customer logos or user counts.
  8. Fonts come from npm (@fontsource-variable/fraunces, @fontsource-variable/geist), copied into each static folder so nothing loads from a CDN.
  9. No violet. Warm palette only.
  10. No em-dashes anywhere (house rule). Copy uses commas, colons and full stops.

1. Brand

Positioning. Doppio is the fastest way to put a good barista in a room. Booking a coffee cart should feel like booking a table: pick the day, see who is free, pay a clear price, done. It is not a marketplace of strangers; every barista is rostered and trained by the operator you book through.

Audience.

Promise. A barista, booked.

Personality. Warm, exact, unhurried. A friendly head barista who also keeps a tidy diary. Confident without swagger, a little dry. Never "crafted with passion", never puns on every line.

Voice rules.

Sample copy.

2. Brand elements

Wordmark. "Doppio" set in Fraunces (soft, high-contrast serif), with the two o's drawn as a pair of overlapping circles (the double). A small cup-steam glyph, two stacked arcs, is the app icon: copper on cream. No gradients.

Colour (tokens in style-guide/tokens.css, also mapped into the dashboard's oklch variables):

Token Hex Use
ink / espresso #231712 text, dark surfaces
roast #4A2E22 secondary dark, headings on cream
paper #FAF6EE page background
crema #F1E4CE cards, bands
milk #FFFFFF raised surfaces
copper #B8461B primary accent, buttons
copper-deep #8E3512 hover/pressed
steam #E3B25A highlight, chart secondary
leaf #3E6B4A success, confirmed
brick #A63A2E destructive, alert
muted #6E5E53 secondary text (5.8:1 on paper)
line #E3D6BF borders

Type. Display: Fraunces Variable (opsz, soft). Body and UI: Geist Variable. Scale (1.25 ratio, fluid at the top): 12, 14, 16, 20, 25, 31, 39, 49, 61/72 (clamp). Display lines at 1.05 to 1.1 line height, body 1.55. Tabular numerals for prices and times.

Spacing and shape. 4px base: 4, 8, 12, 16, 24, 32, 48, 64, 96, 128. Radius soft-round: 8 (inputs), 14 (cards), 999 (buttons, chips). Shadows are warm and low: 0 1px 2px rgb(35 23 18 / .06), 0 8px 24px rgb(35 23 18 / .08).

Imagery. Product UI as the hero image. Where photography arrives: natural light, hands and equipment in use, no staged smiles, warm grade. Until then, flat crema grounds and line illustrations of the three setups.

Iconography. Lucide set (already in the dashboard), 1.5 px stroke, rounded caps; custom glyphs for cart, bar, tasting, cup, steam in the same stroke.

Motion principles. Motion pours: things rise, fill and settle, never bounce.

3. Information structure

Landing page (one idea per screen):

  1. Hero: headline, hard fact ("Confirmed in about two minutes"), live animated booking demo (auto-plays through type, day, barista, confirmed; pause button; click to take over).
  2. Quote builder (interactive moment): guests slider, setup, hours; price and recommended setup update live.
  3. Setups: Cart, Bar, Tasting, with who each suits.
  4. How it works: three steps.
  5. Manage: reschedule/cancel mock with working toggle between states.
  6. Offices: recurring bookings, one invoice a month.
  7. Operators: one line and link to the dashboard.
  8. Close: book CTA; footer.

Customer app (referenced in the demo and copy): Home (next booking, rebook), Book (type, when, setup, barista, review), Appointments (upcoming, past, reschedule, cancel), Account (details, invoices).

Dashboard (operator): Overview (stats: revenue, bookings, utilisation, unfilled; revenue trend; upcoming bookings table), Schedule (week calendar by barista), Roster (baristas, status, week load). Left sidebar nav, brand header, search-less to stay small.

Style guide: Principles, Colour, Type, Spacing and radius, Components (button, chip, input, card, booking row, stat, toast), Motion (live demos), Voice and copy (do/don't).

4. Implementation tasks

Shared: style-guide/tokens.css is canonical; landing/ carries a copy, the dashboard maps the same values into src/index.css.

  1. Fonts and tokens. Install Fraunces in dashboard, copy woff2 files to style-guide/fonts and landing/fonts, write tokens.css. Verify: files exist, page loads fonts.
  2. Style guide (style-guide/index.html, guide.css): every section in section 3. Verify in a browser at 1440 and 390: no overflow, motion demos work.
  3. Landing (landing/index.html, landing.css, landing.js): sections in section 3, reduced-motion handled in CSS and JS. Verify: 1440, 768, 390 screenshots, no horizontal scroll, demo plays and pauses, quote builder updates.
  4. Dashboard theme: replace the neutral variables in src/index.css with the brand, Fraunces for headings.
  5. Dashboard components: add shadcn card, badge, table, avatar, tabs, progress, separator, sidebar-free custom nav. Build Overview, Schedule, Roster views over src/data.ts (seeded, typed).
  6. Verify. npm run typecheck, npm run build, npm run lint; screenshots of each deliverable; grep for em-dashes.
  7. Links. Serve each folder locally.

5. Review focus (not covered by the happy path)