← Back to the screen

Design system portfolio

Design record: Solviva

The four direction lines behind this page, the generator command that produced its tokens, and the pairs it was measured against.

A twenty-four-cover coastal restaurant: the room, the menu, the booking.

The direction, settled before the first section existed

The second scrimmed block is the caption on the full-bleed pass photograph. It used to sit under the image on a band of night ground, which between a bleed photograph and the cream menu reads as a slab of near-black carrying one 13px line, a rule nobody drew, and widening the band only made the slab bigger. The caption now rides the image's own bottom edge on the gradient lux_tokens.py --scrim prints for edge-anchored text (0.58 at the caption's end, nothing by 45%), which costs less of the photograph than the 0.576 flat wash text free to land anywhere would need. Measured afterwards on the real crop, shooting twice so a cream glyph could not be read as a bright background pixel: the worst pixel behind the caption is #4d4947 at 1440, #47413e at 1280 and #444444 at 375, giving 8.40:1, 9.47:1 and 9.19:1 against a 4.5:1 floor.

The second state is the booking answer. A restaurant with two services a night and nine tables turns people away most evenings, so the hard state here is not an empty list: it is "no", said in a way that keeps the guest. The page ships with the form set to a Sunday, and the panel beside it says the room is dark, names the next two tables that fit the party, offers the counter to anyone booking for two or fewer, and offers the first table outright.

The book answers four ways and all four are reachable: a table, a full service, a dark day, and nothing left in the fortnight, which the last evening in the list produces for a party of six. Taking an alternative sets the form to it and asks again, so the guest confirms the table they can see rather than one named in a button; confirming writes it into the panel and leaves a way back out. Focus follows the panel whenever the control that moved it has just been replaced.

Generator

lux_tokens.py --both > tokens.css

The brief names lux_tokens.py. --both earns its place by emitting the day mood the menu section needs. Nobody hand-edits tokens.css; the generator owns every line of it.

Why this product suits this system

The system exists for the one thing this page has to do: make a room feel expensive on a phone in a dim bar, while somebody decides where to take somebody to dinner. Its hardest rule (solve the scrim, never guess it) is the rule a coastal restaurant breaks first, since the hero is a bright sea through tall windows and the caption goes straight on top of it. Its type scale reserves an eyebrow at 11px with 0.18em of tracking, which carries most of the genre's signature. Its palette holds three families and one metal, which is what keeps a menu from reading as a dashboard with a serif bolted on.

Deviations from CONTRACT.md

§2, "every <img> is a data: URI". The four photographs live as files under img/ and the page references them by path. The first build inlined them and the numbers decided it: the document came to 303 kB, 104 kB of that base64 hero on the LCP path, and every device downloaded both hero crops because no media attribute can choose between two data URIs, and a data URI cannot carry a srcset at all, so inlining would cost the page the width selection that is the whole point of the image work. As files the document is 42 kB, a phone fetches a 102 kB portrait crop, a 2× laptop a 202 kB wide one, and a browser without AVIF falls back to WebP. The page still reaches no other origin.

§5, "both themes … prefers-color-scheme … data-theme". This system publishes night and day as which room a page is in rather than as a user preference, and its skill rejects reading them as a dark-mode toggle. <html data-mood="night"> sets the page; the menu section declares data-mood="day", so both moods appear at once. tokens.css still carries the generator's @media (prefers-color-scheme: light) block, which governs any page that declares no mood at all.

APCA disagrees with WCAG on two small-text pairs. The 11px to 12px uppercase eyebrow, brass on night, measures 8.36:1 and Lc −57.3; the button label, ink on brass, measures 5.59:1 and Lc +42.3. Both clear WCAG 2.2 AA and both fail APCA at that size. Both sizes come from the system's own scale and component rules, which the contract lets win. The eyebrow carries font-weight: 500 rather than 400 to narrow the gap.

Image resolution. The two full-width crops stop at 2560px. A 1440 display at 2× asks for 2880 and a 1920 one for 3840, and serving either would put the hero past the 250 kB the system caps it at. The page buys 1.78× on those two and a true 2× on the two editorial frames. CREDITS.md has the measurement.

Lint findings this page keeps

copy-lint.ignore records three, each with its reason. directional covers "above the water", which says where the room sits rather than where the layout sits. title-case covers "Cala Rotja · Menorca", a place and an island, both spelled the way the map spells them. label-period covers the menu's <dd> lines, which are complete sentences, and in the allergen case a safety message that the system's voice reference insists stays plain and complete.

Uplift round, 2026-10-29

Round three, 2026-10-29

A cold critic scored the page 6.5: the photograph was superb and "Solviva" was in DejaVu Serif. Measured: the generator's stacks name Canela, Ogg, Editorial New, Suisse Intl and Neue Haas Grotesk, commercial faces nobody has and none loaded, so every visitor fell through to Georgia and the system sans.

Round four

Round nine, 2026-11-09

Heuristics, ten scored 0 to 4: 29 before, 35 after. Before, below 3: status 2 (on a 390px phone the answer sat a screen and a half under the date just touched), and match with the real world, error prevention, recovery, control, help at 3 or under (the slip promised "the kitchen telephones" and asked for no number).

Left: no persistent "Book" mark once the cover is scrolled (it would sit on photographs and need its own scrim; taste, severity 1). The phone cover shows cliff, not water, because a 1:2 crop of this frame cannot hold both (taste). Boson reports focus-not-visible on every control; Tab with computed styles shows a 2px brass ring on all of them, so it is its probe, not the page. Boson's launch check wants a privacy policy for a form that sends nothing.

Round ten, 2026-11-09

A second reader, cold, scoring the one task (booking a table). Heuristics, ten scored 0 to 4: 31 before (round nine's 35 did not survive a second read), 36 after. Before, below 3: error prevention 2 (the no-show cost sat last, in 12px, under the form, not at the button; a diner could not say what would not suit them although the menu asked), recovery 2 (confirming was undoable only by silently dropping the table, and touching any control after confirming dropped it with no word), control 2 (a one-task page 10,000px long with no way to the book once the cover had gone), help 3, consistency 3.

Inventions, each minimal: "past the hour" for when the fifteen minutes run; the optional dietary field; that releasing a table is the same as cancelling inside the free window (the page offers no other cancel). Left: no door on the cover (the cover's own button is the door there), the door is last in tab order (taste).

Round eleven (2026-11-10)

A reviewer booked Tuesday 15 September at nine for two. The slip said "Booked for two" while calendar cell 15 and the Service chip still read "Nine" and "A table" (sev 2: the act did not change the figures it touches). Reproduced before editing in all four states.

Round twelve (2026-11-10)

A reviewer picked Four, then Saturday 19 September. The calendar cell said "Seven" (the only sitting free for four) while Service kept "Nine" and the answer said "Nothing for four on Saturday 19 September at nine", offering Wednesday 23. On a phone the status bar said "Nothing free at nine" right after tapping that cell (sev 2: the page answered no to a date its own calendar had just promised). Reproduced before editing at 1440: 50 of 200 combinations of start service, party and date, in both orders, ended in a no beside a calendar cell that was neither Full nor Dark.

Round fifteen (2026-11-10)

A reviewer confirmed Tuesday 15 September at nine for two ("Booked for two."), then tapped Three. The panel said "Released: a table for two ... Put it back" above a fresh form for three, the calendar cell went back from Booked to Nine, and tapping Two again left an empty form with no Put it back: the booking was gone with no word from the guest (sev 2, reproduced at 1440 before editing). Two sev 1 notes from the same file: Release this table and Ring the restaurant were identical brass caps, and after a release the phone strip read "See slip" with no slip.

Inventions, minimal: the sentences of the change notice, "Change", "Keep my table for ...", "Changed. It was ...", and the rule that Change and Change back are the only ways a held table becomes another. No new price, date, seat count or policy. Left: the dietary hint and a return-guest shortcut from the same file (help 3, flexibility 3) need facts the brief does not give.

Round nineteen (2026-11-10)

A reviewer typed "+34 971 22" (six digits) as the telephone and pressed Confirm. The page booked and wrote "The kitchen telephones the evening before, on the number you gave" for a number nobody could ring (sev 1). The rule was seven digits or more, and any letters were stripped before counting. Reproduced before editing at 1440, 390, 360 and 1920: it booked at all four.