Doppio: brand, system and build plan

Nobody was available to answer questions, so the planning step was run as "state the call, write it down". Every assumption is listed in section 0 and can be overturned without breaking the system.

0. Assumptions

  1. Name. None was given, so the product is Doppio (the double shot). Short, spellable, brandable, says coffee without saying "bean". Fictional; check trademarks before launch.
  2. Market. Australia first (assumed Australian market): AUD, GST-inclusive pricing, dates as 18 Nov, 24-hour-or-am/pm shown as "9:30am", sample places are Melbourne and Sydney.
  3. Two sides. Customers book (landing page leads to the booking flow, then "My bookings"). The business (a barista-hire operator) runs the dashboard. The dashboard is the business side only, as requested.
  4. Offer. A booking = a barista + a setup (Cart, Bar or Tasting table) + a duration + a headcount. Priced per hour per barista plus a setup fee. All prices and figures in the build are sample data, labelled as such in the dashboard, never presented as real customer metrics.
  5. No fabricated proof. No testimonials, logo walls, customer counts or review scores anywhere. The landing page sells with the working product preview instead.
  6. Imagery. No photographs were supplied and no network image source is used. The pages are type-led (the chosen theme is half type by design) and the interactive booking preview is the visual. Photo slots are listed in section 7 for the owner to fill.
  7. Stack. Style guide and landing: dependency-free static HTML, CSS and a little JS, sharing one tokens.css. Dashboard: the existing Vite + React + shadcn (base-nova, Tailwind 4) project, no router, no backend, in-memory sample data.
  8. Motion. The Broadside theme prefers a still page. The brief explicitly asks for motion graphics, so motion is added as printing motion: stamps, ticket feed, count-ups, all transform/opacity, all disabled or finished instantly under prefers-reduced-motion.
  9. Fonts. Google Fonts links for the static pages (with Impact / Arial Narrow fallbacks); @fontsource packages in the dashboard if installable offline, else the same Google link.
  10. Light only for the brand. The dashboard keeps the project's .dark class but it is mapped to an inked variant (ink stock, buff type).

1. Brand

Positioning. The easiest way to put a real barista, and a real bar, in any room. Booking a coffee cart should be as simple as booking a table, and managing it should be as simple as a paper diary.

One line. Book a barista. Bring the bar.

Audience.

Idea. Doppio is a printer's bill for coffee: the notice pinned to a market stall. Tall condensed capitals, one hot red, buff paper, ink rules. It reads like an event poster, which is exactly what the customer is booking. Not the cream-and-kraft "artisan roastery" look, not a SaaS gradient.

Personality. Warm, brisk, a bit theatrical, never precious. A barista who has the queue handled. Confident like a poster, plain like a receipt.

2. Brand elements

Element Decision
Wordmark "DOPPIO" in Bevan (slab), uppercase, with a doubled underline rule (two 2px rules, 3px apart): the double shot. No symbol needed; a favicon is a Bevan "D" in a square ink block.
Colour Paper (buff) oklch(92% 0.028 88), Paper 2 and 3 for bands and wells, Ink oklch(18% 0.01 50), Muted oklch(43% 0.02 62), one accent Vermilion oklch(53% 0.19 33) ("crema red"). Success oklch(50% 0.12 150) and error oklch(52% 0.19 27) for states only. Rule: vermilion is used once per screen region as the signal.
Type Display: Six Caps (fitted, uppercase, 0.88 line height). Titles and wordmark: Bevan. Everything read: Archivo Narrow 400/500/600. Labels are body face, sentence case, untracked. Three families, no more.
Shape Square corners, 1px / 5px / 3px rules, double-rule frames, no shadows.
Imagery Plain daylight documentary photographs of cart, cup and barista at eye level, printed duotone ink on buff in a double-rule frame, square. Never type over a photo. Half the page stays type.
Iconography Lucide, 1.5px stroke, square caps, ink only (vermilion for one active state). Used small and functional; never decorative. No emoji.
Motion "Printing, not bouncing". 120 / 220 / 420 ms, ease-out cubic-bezier(.16,1,.3,1). Things stamp in, feed out like a ticket, numbers tick. Only transform and opacity. Every animation has a reduced-motion end state, and content is visible without JS.
Texture A faint speck grain on bands and wells only, never under running text.

3. Information hierarchy

Landing page (job: book)

Anatomy follows "book": the action first, then proof the product works, then the details, then the action again.

  1. Nav: wordmark, 4 anchors (Try it, How it works, Setups, Pricing; shown as a scrolling row on mobile), one primary action "Book a barista".
  2. Hero (Marquee/Poster): fitted display "BOOK A BARISTA. BRING THE BAR." One sentence, one primary and one secondary action. Visible without scroll at 1280x800.
  3. Interactive booking preview (the signature): a working mini booking card. Pick setup, headcount, hours; the price, barista count and a printed "ticket" update live, with a "Confirm" that stamps the ticket CONFIRMED.
  4. How it works: three steps as a pinned timetable bill (Choose, Confirm, Pour), with a looping demo of the ticket moving through states.
  5. Setups: Cart, Bar, Tasting table as three bill columns with particulars as rows.
  6. For the day itself / manage your bookings: reschedule, add a barista, forward confirmation (the customer app's "My bookings" shown as a built UI card).
  7. Pricing: a table, sample rates, GST noted.
  8. Close (an FAQ was cut to keep the page under the word budget): vermilion band with the booking form (date, headcount, email), hours and the address.
  9. Footer: index columns.

Customer app (screens named, shown on landing, not built as a separate deliverable)

Book (setup > when > details > confirm), My bookings (upcoming/past, reschedule, cancel), Booking detail (ticket, barista, add-ons), Account.

Dashboard (business side, app screen, sidebar layout)

  1. Sidebar: Overview, Schedule, Bookings, Roster, Settings (inert placeholders where not built).
  2. Overview: four stats (revenue this month, bookings, utilisation, average booking value), revenue chart (14 days), utilisation by setup.
  3. Upcoming bookings table (status badges, barista, setup, time, value) with a filter.
  4. Schedule: week calendar grid by day with barista lanes, booking blocks, click for detail sheet.
  5. Roster: barista cards/rows with availability this week, hours booked, skills, status. All data labelled "Sample data".

4. Voice, tone and sample copy

Voice. A sale bill read aloud: the date, the place, the lot and the hour, each said once. Short sentences. Trade words (cart, bar, shot, service, bump-in) used correctly. Capitals for shouting, small print for explaining. Tone. Warm and unfussy; reassuring on money and timing; a little dry-humoured in empty and success states; never exclamation marks, never "oops".

Place Copy
Hero headline BOOK A BARISTA. BRING THE BAR.
Hero sentence Pick a setup, a time and a headcount. A trained barista and a full cart arrive early and leave nothing behind.
Primary action Book a barista
Secondary See how it works
Booking preview label Try it: price a booking
Ticket stamp CONFIRMED
Section heads How a booking runs. / Three ways to set up. / Change your mind, not your caterer.
Pricing note All prices include GST. One barista per 60 guests, added for you.
Button microcopy Confirm booking, Reschedule, Add a barista, Forward confirmation
Success Booked. Your barista will message you the day before.
Empty (bookings) Nothing on the books. Quiet week.
Error (slot) That slot just went. The next one is 30 minutes later.
Validation Add a headcount so we can send enough baristas.
Dashboard empty No bookings match. Clear the filter to see the week.
Dashboard status Confirmed, Pending, Needs barista, Completed
404 / fallback Not on the menu.

5. Design system (shared by all three deliverables)

6. Implementation plan

Order is chosen so the shared system exists before pages use it.

Price maths (landing preview and sample data). Rate per barista-hour: Cart 85, Bar 110, Tasting 140 AUD. Setup fee: Cart 120, Bar 220, Tasting 90. Baristas = ceil(guests / 60), min 1. Minimum 2 hours. Total = baristas x hours x rate + setup fee. GST is included (shown as total / 11).

7. Material ask (open items for the owner)

Photographs (hero cart at an office, close-up of a pour, the bar at a wedding, tasting table), a real address and hours, real prices, a customer quote with a name, and any logos permitted. All are absent today and nothing was invented in their place.