A developer tool's marketing site: the hero, the argument, the pricing. Aperture records a service's calls, queries and jobs in production and replays one of them against the code on a laptop.
Direction
Archetype: editorial spread, led by an interface-product hero (changed in the 2026-10-29 uplift: the page now opens on the product itself rather than a transcript beside the headline). The first fold is the debugger at full width: a 500 set at 56px in a red stage, the failing step named beside it, +30.0 s at the right, and a control that scrubs back to the cause (step 4). The headline is a 40px caption above it, not the hero. Six blocks, five column rhythms. The argument hangs its numeral in one margin and its evidence in the other, and movement 3 swaps the two sides.
Data stance: prose-first. Every figure sits inside a sentence or a margin line naming what it counts.
Density: comfortable, on Tailwind's single --spacing: 0.25rem base. One block breaks it: the recording list runs at 14px on 1.45 leading, against 64px between movements and 96px at the two ends.
The one bold thing: every colour is a measured step. No default indigo, no gray-400 body text, no gray-300 control border, and the pricing figures are set tabular.
Generator
tailwind_theme.py --theme colors
tailwind_theme.py --theme scales
Both write tokens.css. That file is generator output; nothing here edits it.
Measured first
tailwind_theme.py --pitfalls # exits 1; all six defaults fail, none appear here
tailwind_theme.py --ramps # first step reaching 4.5:1 on white, per hue
--ramps puts the accent at teal 700 rather than 500. Only six of the 26 hues reach 4.5:1 on white at step 500, and teal is not one of them.
Palette
Three families, from tokens.css only: slate (neutral), teal (accent), red (the over-volume state). The page declares the semantic layer once and flips it per theme, so the markup names roles rather than steps.
| Pair | Where | Ratio (contrast.py) |
|---|---|---|
white on teal-800 | primary button, light | 7.55:1 |
slate-600 on white | every muted line, light | 7.56:1 |
teal-700 on white | links, numerals, focus ring | 5.44:1 |
slate-100 on slate-900 | the tight band, both themes | 16.28:1 |
teal-300 on slate-950 | accent, dark | 13.71:1 |
slate-950 on teal-300 | primary button, dark | 13.71:1 |
slate-400 on slate-950 | muted line, dark | 7.68:1 |
red-600 on white | over-volume state | 4.92:1 |
Two border tokens, not one. slate-200 (1.23:1) separates rows and never bounds a control. slate-500 (4.77:1 light, 4.23:1 dark) is the boundary of anything SC 1.4.11 covers. Muted text sits a step darker than WCAG asks, at slate-600, because APCA reads 4.77:1 as a 24px colour.
The second state
The pricing block carries a real volume control. Past a plan's included replays that plan states the overage in words and money rather than going quiet; the page loads at 40,000 a month so the page shows the state before anyone touches the control. The workspace line carries a 37-character customer name, the string that breaks a two-column definition list: the label track is measured at 8rem rather than left to auto, so the name wraps in the track that is left instead of starving the label to nothing.
Deviations
No build step, so this page declares the semantic tokens on :root rather than in @theme inline and writes out the utilities they would generate. Names and values match what that block emits. The favicon and the two theme-color metas carry the sRGB of their own tokens, because neither attribute can hold a var().
Uplift, 2026-10-29
- Hero is the product. A recorded request (
tr_8f21c4, POST /checkout/confirm, 53 spans, 3 services) replays in a debugger window: six recorded steps, source with syntax colours and a sliding current-line bar, a values panel, one sentence per step, and a native range as the scrubber. It loads on the failing step, so the answer is already visible and the reader scrubs back to the cause. Play, previous, next and the step list are keyboard-equivalent; the slider carriesaria-valuetext. - One story, consistent figures. job:reprice wrote a quote at 14:00:39; the request at 14:02:11.338 read it 92 s later; tenders sum to $412.00 against a $488.00 quote (delta minus $76.00); the gateway timed out at +30,014 ms (14:02:41.352Z). The chain figure, the trace file, the diff terminal (500 to 409 in 12 ms, fix on checkout.rb:60) and the replay all agree.
- Pricing as evidence. A hand-drawn SVG (JS, drawn to the pixel width) plots cost per seat against replays a month, direct-labelled at the line ends, with the crossover (11,000 replays) annotated. The slider moves a marker; each plan card states its cost at that volume (Solo 19 + 0.010 x 35,000 = $369 at 40,000). The over-volume state stays.
- Phone. The debugger becomes a player: code, controls directly under it, then the step's sentence and values; the step list collapses into the scrubber's marks.
- Design notes recomposed: direction lines as ruled entries, two measured pairs as swatches, every table row with its own swatch.
- Widths. Past 1600px the shell grows from 80rem to 90rem.
- New measured pairs (all from the same palette): slate-400 on slate-900 6.79, slate-100 on red-950 14.72, sky-300 / amber-300 on slate-900 10.73 / 12.36, red-300 on slate-900 9.37. The code window is dark in both themes, so these are declared once.
- Known tool findings left: boson's
sticky-never-stickson the code highlight (it sticks to the left edge of its own horizontal scroller on purpose) and a 2pxfixed-height-clipped-texton the h1;direction_checkstill reads the hero as undecided because it does not recognise an interface hero built from live markup.
Round four
- The headline column and the intro column hang from one top line (eyebrow and first line of the deck start together); they were both bottom-aligned, which left the intro 90px above the headline.
- On a phone the sentence, the Start recording button and its cost line sit above the product, so the first screen holds the action and the top of the failing request. The source pane keeps a thin bar and fades its right edge while there is more to scroll (scroll-driven, so no script; nothing fades where the pane does not overflow).
Round nine
Judged against Linear, Vercel, Sentry and Tailwind's own site, the first fold held and the page around it did not: no navigation, no footer, no questions answered before the sign-up. Findings, worst first.
- Phone code panel (sev 3). At 360 and 390 the failing line,
timeout: 30, was cut off by a sideways scroller. Source lines now wrap under their own indent wherever the pane is narrower than the longest line (a container query on the pane, so a phone, a tablet and a 200% zoom all get it) and the current row carries its own highlight, because the sliding bar assumes equal row heights. Checked on an emulated phone (touch, 3x) at 360 and 390. - Controls moved under the pointer while scrubbing (sev 2). The sentence under the code is one line on some steps and two on others, so the scrubber shifted 9px. The panel now reserves the height of its longest sentence; all six steps measure 629px.
- Scrubber labels collided (sev 2). Below about 400px of rail, "request" ran into "flag" and "charge" into "timeout" (a tablet, or 200% zoom). Only the two ends are named there.
- Clock beside the controls at 360 (sev 2). The next button touched "+30,014 ms". The Play button is narrower on a phone and under 352px the clock takes its own line.
- Chart tags collided (sev 2). Below the 11,000 crossover the Solo and Team value tags printed on top of each other and the dashed marker ran through the annotation. Tags now carry the plan name and stack where the lines are within a tag's height; the marker starts under the annotation when it would cross its words; the crossover mark sits under the reader's marker.
- A figure that disagreed with the slider (sev 2). "12 x $79 = $948" never moved when the volume passed Team's 50,000. It now reads seats times the cost at the chosen volume.
- Touch targets (sev 2). Under a coarse pointer the back link, theme toggle, step controls, links, both sliders and the footer links reach 44px; the visible rail stays thin.
- The cause was named but never marked (sev 1). Step 4 now says "The cause" in the stage, "the cause" in the step list, and wears an amber tick on the scrubber; its spoken value says so too. Amber is the syntax string colour already declared for the code window.
- No navigation or footer (sev 1). A sticky bar (only where the screen is at least 640px tall, so never at 200% zoom) with four in-page anchors and the primary action; a footer of in-page links. The design notes follow the footer and stay last.
- Questions before you start (sev 1). Five disclosures under the plans, first one open, each answer built from figures already on the page.
- The hero strip repeated the band (sev 1). 1.4 % and 42 ms appeared twice; the band now carries 12 inputs and the 256 KB threshold instead.
- Locals panel: in a column under 15rem the values sit under their labels instead of breaking "Payments::Timeout" mid-word.
Left alone: the design notes do not mention the round-nine additions (they describe the direction, not the changelog).
Round ten
A cold second read, doing the page's task (understand it, start a trial) as a backend lead. Heuristics before and after (0 to 4): visibility 3/3, real world 4/4, control and freedom 2/3, consistency 3/3, error prevention 2/3, recognition 4/4, efficiency 3/3, minimal 4/4, recovery 3/3, help at the point of action 3/4. Total 31 to 34.
- The trial could not be started (sev 3). All three plan buttons were
type="button"with no handler, and every "Start recording" scrolled to the plans, which ended at those buttons. Every start control now opens one native dialog: what is charged (nothing, no card), what happens after the trial, when a plan renews and how to stop it, above "Start the trial". Starting it moves focus to the running state (install commands with Copy), changes every control that offered it to "Trial running", marks the chosen plan card and rewrites the hero line. "Cancel the trial" is the way back; Escape, "Not now" and the backdrop close. On a phone it is a bottom sheet. Links still reach#pricingwithout script. - Contact sales was a dead button (sev 3). It opens the same dialog as a request: the price, the renewal and the stop first, then a work email checked on send (never on blur), then "Request sent", and the card button reads "Request sent".
- Price, renewal and stop were in a paragraph far from the action (sev 2). Each plan card now carries its renewal and stop line directly above its button.
- Self-hosted said "Every month $400" under "$4,800 a year" (sev 2). One fact stated two ways, and it read as a monthly charge. The row is "Averaged over a month".
- The hero line stopped at "no card" (sev 1). It now says nothing is charged unless a plan is picked.
- The sticky bar never said where you are (sev 1). The link for the section on screen is marked.
- Driven at 1440, 390 and 360 (touch, 3x), light and dark, and 1920 after the last edit: open, focus lands on the heading, Escape returns focus to the opener, cancel, invalid and valid email, backdrop close, no sideways scroll.
Inventions (the brief gives none of these): the trial is plan-less until a plan is chosen, and reads "Day 1 of 14, 0 of 5,000 replays used"; cancelling a trial ends it with nothing to settle; self-hosted "renews each year, cancel at any time and the next charge stops" extends "renews the same way"; "Sales has your request and will reply" promises no timing; nothing is sent anywhere.
Round eleven (2026-11-10)
- The Team card spoke to a customer the page has not met (sev 2). Under "Start recording" a block read "Your workspace / Seats in use 12 of 40", as if the reader were a signed-in account with 12 seats, on a page whose promise is a trial with no card. The brief did not set up a signed-in visitor: the workspace line is the 37-character name that stress-tests the definition list (see "The second state"). The block now reads as an example: "Example team" for the name row, "Seats / 12 of up to 40" (Team allows 2 to 40, already on the card), and "At this volume / 12 x $79 = $948" unchanged, still following the volume slider. The long name and the 8rem label track are kept.
- Invention: none. "of up to 40" restates the card's own "Seats 2 to 40".
- Driven after the last edit at 1440 light, 390 dark, 360 light, 1920 dark: no page errors, no horizontal overflow, total moves to 12 x $499 = $5,988 at the slider maximum.
Round twelve (2026-11-10)
- The pricing chart's live labels printed over the annotation and the axis on a phone (sev 2, and a sev 1 beside it). At 360 and 390 the "Solo $849" tag landed on "From 11,000 replays a month, Team costs less than Solo." and both became unreadable. Measured over all 121 slider steps (text boxes, tspans for the annotation), the overlap was not only 85,000 to 90,000: at 360 it hit 67 of 121 steps and at 390 64 of 121 (10,000 to 33,000 and 73,000 to 115,000), the worst 92.7 x 15.7 px, and the left of the range also ran the "$300" axis figure into "Solo" and "Team" tags. 1440 and 1920 had none.
- Fix.
placeMarkerno longer fixes a tag to one side of its dot. It tries each tag on its preferred side above the dot first (the old place), then the other side, then below, then a line higher or lower, clamps it inside the chart, and keeps the first pair of places where neither tag touches an axis figure, an end label, the annotation, either dot or the other tag; among those it crosses the fewest plan-line points and keeps the dearer plan's tag the higher.drawChartrecords those fixed boxes and the two lines as points. Where nothing is free it takes the least overlap. Wide screens, where nothing collided, keep their old places. - Result. Worst text-box overlap over every step, light and dark, at 360, 390, 1440 and 1920 (also 479, 480, 768): 0 px. At 320 (chart 288 px wide) the static "Solo $1,169" end label touched the annotation at every step and the steeper Solo line ran through a three-line annotation; see the next line.
- Invention: none. No copy, number or token changed. At the extremes a tag may sit below its dot or above the plot, and at 0 it crosses a plan line (its knock-out stroke keeps it readable).
- Driven after the last edit at 1440 light, 390 dark, 360 light, 1920 dark: no page errors, no horizontal overflow.
- 320 px (follow-up). Under a 316 px chart the annotation breaks into five short lines ("From 11,000 / replays a / month, Team / costs less / than Solo.") and starts at the axis, so it clears the end labels and the Solo line. Worst text-box overlap at 320, light and dark, all 121 steps: 0 px; no plan line passes through the annotation at any width measured (320, 360, 390, 479, 480, 768, 1440, 1920). Driven again at 1440 light, 390 dark, 360 light, 1920 dark and 320 light: no page errors, no horizontal overflow.
Round fifteen (2026-11-10)
- The phone header had no way to a section or to Start recording over a 13,200 px page (sev 1, reproduced at 390 and 360). Below 64rem the four section links were hidden and below 40rem so was the header action; the bar held Portfolio, the mark and the theme toggle. Fix. Below 64rem a menu button (hamburger, becomes a cross when open, named "Menu") opens a disclosure under the bar with the four section links; it is a
<button aria-expanded aria-controls>and a<nav aria-label="On this page">. Opening moves focus to the first link; Escape closes it and returns focus to the button; a press outside, choosing a link, Tab leaving it, or the bar widening to 64rem closes it; the section on screen carriesaria-current="location"and a bar on its leading edge (the samelocate()that marks the desktop links). Below 40rem the bar keeps the one primary action in a short form, "Start", with "recording" kept for assistive technology so the name is still "Start recording", and the Portfolio link moves to the foot of the menu. Between 40rem and 64rem the bar keeps Portfolio and the full label. Without script the button stays hidden and the page reads as before. At 320 the wordmark drops to 14px and the gaps to 4px so the five controls fit without overflow. Desktop (64rem and up) is unchanged: every bar item measures the same box at 1440 and 1920. - Copy threw when the browser refused the clipboard (sev 1). Both Copy buttons (terminal and trial dialog) now share one handler; a refused or failing write turns the label to "Not copied" for 1.8 s and shows a visible line, "The browser would not copy. Select the two commands above and copy them by hand.", beside a red rule; a success restores the screen-reader-only status. No page error.
- At 120,000 each end label printed twice (sev 1). At the top of the range the marker tags repeat the line-end labels word for word, so they are hidden there and shown again below it.
- "From 11,000 replays a month, Team costs less than Solo" is false at exactly 11,000, where both cost $79 (sev 1). The annotation now reads "Above 11,000 replays a month, ...", in all three line breaks. Worst text overlap over 88,000, 120,000 and 11,000 at 320, 360, 390, 700, 1440 and 1920: 0 px.
- Inventions: the short label "Start" on a phone and the label "Menu" for the menu button (no product fact); the copy-failure sentence, which states no policy. Not touched:
var tightis read before it is assigned indrawChart, so the 320 px annotation start-at-the-axis branch never runs; the annotation still clears everything there (0 px). - Driven after the last edit at 1440 light, 390 dark, 360 light, 320 light, 700 light and 1920 dark: no page errors, no horizontal overflow; menu open, Escape, Tab out, outside press, section link, Start while open; Copy refused; slider at 120,000, 11,000 and 88,000.