Carafecafe website template Tailwind

The menu card is set once a season; today's soup, a dish that sold through, the terrace closing for the season and “weekend brunch is walk-in only until the 27th” are dated paper sheets clipped over the card's corner, each one striking the row underneath it, hiding that row's photograph, and disappearing by itself the moment it expires. A slip is data rather than a notice: it carries a kind, a target, a date window and its typed lines, and slipsFor() throws at build time on an orphan target, a replaced dish the target service does not serve, an unknown hours row, a policy on a service that takes no bookings, or a window that ends before it starts. Thirteen routes ship. Five public pages, each of them built in both languages: a home page that opens on whichever of the five services is being served at the hour a visitor arrives, the whole card by time of day, hours and access and house rules, the booking policy, and the privacy notice. Then three that stay in one language: an editing guide, a living component styleguide, and a 404 that still says what is on. The fixture is one spine. Mireille, a 34-seat café-bistro on rue Beaubien Est in Rosemont, Montréal, with a bilingual card of 52 items across 10 sections and 5 services, 12 of them photographed and 40 rendered as type-only rows, because a menu component that only survives a dozen dishes with pictures has not been tested. Every figure on every page resolves through that one file: open until 17:00, laptops away until 14:30, the second batch of kouign-amann at 14:30 and usually gone by 11:00, the washed Sidamo that went on the grinder last Tuesday, and “card last changed Mon 14 Sep”, which is the maximum modified date over the whole card rather than a line somebody remembers to update. The editing guide is a route, not a PDF. /handover renders the six bands of the home page live under numbered stamps, maps every region on screen to the fixture field that fills it and the WordPress screen that will edit it, walks the four editing tasks a café owner performs after handover, shows all five slip kinds beside the five shapes the build refuses to draw, and states six boundaries plainly. The fixture is shaped as that content model key by key, so the WordPress block theme and its companion plugin are a port rather than a rewrite. Three presets ship as token swaps with identical composition: Zinc, a Paris-style zinc bar in stamp red; Cresson, a morning-and-brunch café in watercress green with a blush slip; Faïence, a tiled bakery-café in enamel cobalt with an apricot slip. Each is one attribute on the root element, and each was authored in OKLCH and verified pair by pair in light and dark across 84 tokens per mode. Twenty-two photographs were generated for this theme and ship with it: one counter at five hours of one day, twelve dishes, the room, the façade and its terrace, the grinder, and the same counter wiped down at dusk. The hero sets its type straight onto the photograph with no gradient scrim, because the overlay region of every plate that can be a hero was measured on the encoded file instead. Self-hosted Brygada 1918, Radio Canada and Sometype Mono, three faces for three materials: the card is typeset, the slip is typed, the chrome is UI. Built for Tailwind v4, Next.js 15 and React 19, with every colour, size, radius and face in theme.css. What it does not do is as deliberate. No cart, no checkout, no delivery, no PDF menu, no star ratings, no Instagram embed, no gift-card commerce, and no claim about a table being free. Booking is one documented provider seam plus a link to the café's own reservation page; takeaway is the same shape, a named link-out with the commission-free direct option stated, and no order form. A gift voucher is an enquiry, written by hand at the counter. Three things the build earns and states: no third-party script anywhere, so the site needs no cookie banner; access facts a wheelchair user can act on, a door 86cm wide, a washroom door of 80cm with a grab rail and tables at 74cm; and every photograph generated for this theme, with no stock. The site is bilingual fr-CA and en-CA from one string layer and one component tree, French served under /fr with a dropdown switch in the header on every page, foreign-language runs marked so a screen reader says them correctly on either build, and the enquiry form ships a Law 25 privacy notice in both languages naming what it collects, who reads it and how long it is kept.