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
- (A1) Product is a two-sided booking app. Customers book a barista plus a cart or bar setup for events, offices and private tastings, then manage appointments. The business side (dashboard) is operated by a small-to-mid coffee-catering company.
- (A2) Market is Australia (owner is in AU): AUD, metric, en-AU spelling (colour, organise), 12-hour times.
- (A3) Name is invented: Doppio (Italian for "double": the barista and the bar, two shots, you and your guests). Short, speakable, no trademark check done. A rename is a find and replace.
- (A4) Product data in the demos is fictional (people, venues, revenue). No backend: dashboard uses typed mock data in
src/data.
- (A5) Static pages (style guide, landing) are plain HTML, CSS and vanilla JS, no build step. Dashboard is the existing Vite + React + shadcn (base-nova) project.
- (A6) Fonts load from Google Fonts (static pages) and Fontsource (dashboard). System fallbacks keep layout stable offline.
- (A7) Light theme is primary. Dashboard also supports dark (existing theme provider), using espresso tones.
- (A8) Landing CTA is "Book a barista" to an in-page interactive preview; no real signup is wired. Nothing is sent or published anywhere.
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.
- 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).
- Tasters: small groups booking a private tasting (4 to 12 people). Curious, gift-minded.
- 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
- Wordmark. "doppio" in lowercase Fraunces (soft, high-contrast serif, optical size high), with the two
ps' counters echoing two cups, and a small copper "crema dot" after the word as the signature punctuation. Monogram: a rounded square with a double-ring (two concentric circles, a cup seen from above). Always copper dot on espresso or cream, never gradients.
- Colour. Warm, high-contrast, food-safe.
- Espresso
#2A1810 (ink, dark surfaces)
- Crema
#F7EFE2 (page), Foam #FFFAF2 (cards), Latte #E8D9C2 (borders, fills)
- Copper
#C4572B (primary action; AA on Foam for large text and UI, #A8451F Copper Deep for small text)
- Pistachio
#6B8F5E (success, confirmed), Saffron #E0A526 (pending, highlights), Berry #9B2F46 (destructive)
- Neutrals are warm browns, never grey. Contrast checked: Espresso on Crema 14:1, Copper Deep on Crema 5.4:1.
- Type. Fraunces (display, 600, with "soft" axis) for headlines and numbers of moment; Inter (UI and body). Mono: JetBrains Mono for times and booking refs. Scale is a 1.25 ratio from 16px with fluid clamp for display sizes.
- Imagery. No stock photos (none available). Imagery is drawn: flat illustrative SVG scenes of carts, cups, steam, latte art in the palette, plus grain texture. Direction for later photography: overhead, natural window light, hands in frame, no faces staged.
- Iconography. 1.75px rounded stroke, 24px grid, rounded joins, one accent fill allowed (copper). Lucide in the dashboard matches closely; custom glyphs (cup, cart, bean, steam) in the style guide.
- Motion principles. (1) Pour, not pop: easing like liquid,
cubic-bezier(.22,1,.36,1) ease-out, 200 to 500ms. (2) Steam rises: ambient motion is slow, vertical and subtle. (3) Confirm with a flourish: one delight moment per flow (booking confirmed: cup fills). (4) Motion explains state change, never decorates a data table. (5) prefers-reduced-motion: all transforms and loops removed, replaced by instant state or opacity fades.
3. Information structure
Landing page (one page, scroll story)
- Nav: wordmark, How it works, Experiences, Pricing, "Book a barista" button.
- 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.
- Social proof strip: counts (events poured, cups served) with count-up, venue types.
- 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.
- How it works: 3 steps with scroll-driven reveal.
- Experiences: Office mornings, Events, Private tastings (cards with tilt/hover).
- Manage it all: app features (reschedule, add guests, chat with barista, invoices), shown as an animated appointment-card stack.
- For operators: one band teaser for the dashboard (utilisation, roster).
- Testimonials, Pricing (3 tiers, monthly/per-event toggle is out of scope; per-event only), FAQ accordion.
- 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.
- Hero: "Book a barista. We bring the bar." Sub: "Fresh espresso for your office, event or tasting, booked in about a minute."
- Alt headlines: "Good coffee, minus the logistics." / "Your guests will remember the flat white."
- Step labels: "Pick the vibe", "Pick the day", "Pick the setup", "You're sorted".
- CTAs: "Book a barista", "See how it works", "Reschedule", "Add guests".
- Microcopy: empty state "Nothing brewing yet. Book your first barista and it'll appear here." Success "Booked! Priya will be there at 8:30 am, cart ready by 9." Error "That slot just got taken. Here are the closest times." Cancel confirm "Cancel this booking? Free until 48 hours before." Loading "Warming the machine".
- Dashboard: "Good morning, 7 bookings today" / empty roster "No one rostered. Add a barista to start taking bookings."
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
shared/tokens.css, shared/base.css (components used by the style guide and landing: buttons, badges, inputs, cards).
style-guide/index.html: tokens, colours, type scale, spacing, radii, shadows, components, icons, motion demos (with replay), voice and copy.
landing/index.html + landing.css + landing.js: sections above, reduced-motion support, responsive at 360, 768, 1280.
dashboard/: theme, sidebar layout, Overview, Schedule, Roster, mock data; typecheck and build pass.
- 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.