← Back to the screen

Design system portfolio

Design record: Trinity Rovers

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

An amateur football club: recent results, the coming fixtures, the Division Two table, and how to join. Brief #15.

Direction

LeverDecision
ArchetypeDocument, set as a matchday programme: a full-bleed claret cover, then one column scrolled top to bottom. No shell, no rail, no dashboard. On a phone a four-item bottom tab bar (Matchday, Fixtures, Table, Join) tracks the section in view.
Data stanceTable-first. The league table takes the full measure; the position-by-week chart and prose sit either side of it. Every figure on the page is derived from one set of results.
DensityBootstrap default spacing, with button padding tightened through --bs-btn-padding-y.
The one bold thingIt does not look like Bootstrap, and no competing selector was written to achieve that.

Generator

tokens.css is generated output and is linked, never edited. The command that produced it:

bootstrap_tokens.py --both

Read before the palette moved, and cited in the spec panel:

bootstrap_tokens.py --buttons
bootstrap_tokens.py --component .btn
bootstrap_tokens.py --component .table

--buttons exits 0 both before and after the palette change. It reads the pinned bootstrap@5.3.8 release rather than this page, so its answer is the baseline the page's own claret is measured against: white on #0d6efd is exactly 4.50:1, and white on this page's --bs-primary #7a1e30 is 10.21:1 (contrast.py).

The data

The season is generated, not typed. mulberry32 seeded with 43147 draws Poisson goals for a 12-team double round-robin built by the circle method, and the build asserts every figure the page prints: P = W + D + L, points = 3W + D, GD = GF − GA, the table's order, each club's form string, the chart's rank per week and the cover's line "Rovers 23 points, 28-12". The cover score is the last played fixture. Nothing in tokens.css changed.

The countdown is pinned to a page clock, Thursday 29 October 2026 9:30 UTC, against a Saturday 31 October 14:00 UTC kick-off, and says so beside the figures. It does not read the visitor's clock, so the cover agrees with the table and the fixtures whenever it is opened. The calendar button is a data: .ics with the same kick-off.

Stylesheet order

bootstrap.min.css   (vendored beside the page, Bootstrap 5.3.8)
tokens.css          (generated)
<style>             (the brand layer)

The vendored file was bootstrap-5.3.8.min.css. bootstrap_lint skips only a file named exactly bootstrap.min.css and otherwise reads the framework as page code (130 errors), so it was renamed; the content is byte for byte the same. The root-level name is kept because build-index resolves a slug's accent by first match in alphabetical order, and a vendor/ folder broke that check.

Bootstrap comes first. tokens.css writes its dark values to [data-theme="dark"], which ties with :root on specificity and would lose to any framework file loaded after it.

Themes

<html> carries both data-theme and data-bs-theme, set before first paint by a blocking script. Bootstrap's dark block redefines 52 of 117 variables and inherits --bs-primary, so all 26 brand variables are restated under :root[data-theme="dark"] and under @media (prefers-color-scheme: dark) { :root:not([data-theme="light"]) }.

The second state

The standings table has a real control above it (a .btn-check radio pair, CSS only, no script) that swaps between the league-confirmed table and the table after Saturday's round. In the provisional view:

Measured

PairRatio
white on --bs-primary #7a1e3010.21:1
cream #f7f3ec on the cover claret #7a1e309.23:1
body ink #22191b on paper #f7f3ec15.53:1
body ink #ede6da on #171311 (dark)14.88:1
--bs-border-color #8a7e6c on paper3.60:1
--bs-border-color #736858 on #1713113.38:1
focus ring on paper3.46:1
focus ring on #1713114.34:1
dark cover claret #fbf7f0 on #8f24387.94:1

The cover, the chart and the join form

The cover is one claret slab (--tr-solid, --tr-solid-deep, --tr-ink-on-solid, with color-mix for soft ink and hairlines): last Saturday's score at display size, the next fixture and the countdown beside it, and the protest notice under both. Archivo's width runs through font-stretch, not font-variation-settings.

The chart is inline SVG, a bump chart of all twelve clubs by week, in a wide and a phone geometry. Rovers is the one saturated line, the others are quiet, and the promotion and relegation bands are tinted with --bs-warning for the drop so it cannot be read as the club's claret. Form marks are letters in role="img" elements with a spoken label. The join form is name, email, position, a side picker and a note; its sent state replaces the form and is announced.

What Bootstrap does not expose

One blue literal is compiled into bootstrap.min.css and no --bs-* variable reaches it: #86b7fe in .form-control:focus, so a focused field carries a blue border for as long as it has focus. Bootstrap's own .focus-ring utility puts a claret ring around it. The supported fix is a Sass rebuild, which a single no-build file cannot do, so it stays and is named in the spec panel.

#0d6efd in .form-check-input:checked is a second such literal, and it is no longer on the page: the side picker is a checkbox toggle group (.btn-check plus .btn), which is Bootstrap's own component, reads the same --bs-btn-* variables as every other button here and carries a 36px target rather than 17px. The select chevron is not a literal either: --bs-form-select-bg-img reaches it, and it is brand ink in both themes.

.form-control does compile its padding, height and font size as literals, so a text field keeps Bootstrap's geometry at this page's radius, colours and type. That is the honest remaining limit of theming through variables.

Colour mode is read from data-bs-theme and from no media query, so the pre-paint script sets it; the system-preference block is defined against a consumer that drops the attribute.

Layout

The two fixtures tables are one spread above 75em and stack below it. Side by side they share a column model (table-layout: fixed, date 4.5rem, ground 9rem, kick-off 5rem) so the pair reads as one decision and the headers line up across the gutter; stacked and on a phone the layout is auto, so the date and score shrink to fit and never overflow into the column beside them.

Every points cell reserves the same mark gutter, so the withheld em dash, the −3 deduction and the footnote letters hang outside the number and every figure in the column right-aligns on one axis.

Round four

Round nine

Found by reading below the fold, driving the states and emulating a phone at 360 and 390.

Round ten

A second, colder read. Fresh score 31/40 against round nine's 35.

Inventions: the 5 November date is arithmetic on the page's own "about a week" and tonight's session; the echo line's wording; the sentence "Every other result from Saturday is in the table below, also not yet ratified" restates the existing caption.

Round thirteen (2026-11-10)

Defect, from the round 11 independent read: on a phone the After Saturday table's notes sit about 900px below their markers (note a at y 4330 from a marker at 3408, 390 wide; 4477 from 3476 at 360) with no link back, so a reader who followed a marker was left where the notes end. Reproduced at 390 dark and 360 light before editing. The reviewer's "about 2,300 px" table did not reproduce as a height: the table measures 1,140px (390) and 1,191px (360), twelve rows of 78 to 132px; 2,300 is roughly where it starts on the page (table top 3,123px). So the height was not cut; the form strip under each club is the brief's own decision and the other columns already collapse on a phone.

Pattern: the phone table already is the Bootstrap "fewer columns" answer (W, D, L, GF, GA and the form column are .tr-opt, hidden under 48em inside a .table-responsive), so it was kept. Stacked rows would roughly double the height, and a details toggle per row needs script the page does not load and hides the note from a reader who is looking for it. What was missing is the standard footnote contract: a marker that goes to the note and a note that goes back. Each note now ends with links, "Back to the Trinity Rovers row", "Back to the Ockbourne Athletic row" (note a has two markers) and "Back to the Whitcombe Athletic row", pointing at ids on the markers (ref-a-rovers, ref-a-ockbourne, ref-b-whitcombe). They are plain fragment links with no script; the browser focuses the target, so focus returns to the marker (checked: document.activeElement is the marker after each back tap). The back links are 44px tall under a coarse pointer and 24px otherwise; the marker has scroll-margin-block: 35vh so it lands with the rows above it in view. Desktop gets the same links (keyboard readers gain a way back); nothing else on desktop changed.

Invention: the link wording only. No product facts.

Round fifteen (2026-11-10)

Defect, from the round 14 read (ship line: the 38px phone inputs and the 25px cover link sit under 44px touch targets). Reproduced before editing at 390 dark and 360 light, touch, scale 3, in both table views: join name and email 354.9x38 (327.6x38 at 360), the position select the same, See it in the table 148x25.2, the note markers 24x24, the Portfolio link 104x43.8, and every toggle label and side picker 43.6 high (the round nine padding landed a hair under 44).

Fix, under pointer: coarse only, so nothing changes on desktop (the 1440 and 1920 form still measures 38 and 24):

Measured after, every visible link, button, input, select and toggle label, both views, 390 dark and 360 light: smallest 104.2x44 (the Portfolio link); nothing under 44 in either axis.

Other severity 1 notes fixed: the countdown day cell is padded like hours and minutes (02, and 00 at kick-off); the sent echo no longer says "no position" and reads "no preference on where you play", matching the field's option; note a now says what Rovers have either way.

Inventions: note a's sentence "Rovers have 26 points if the result stands and 23 if it does not". 26 is 23 plus the three held points; 23 is the confirmed figure, with a replay or other ruling not modelled. The echo wording.

Left alone: the marker-to-note distance (about 900px on a phone). The notes follow the twelve-row table, and moving them above it would put footnotes before the thing they annotate; the back links and the provisional banner (which already states the rule above the table) are the honest answer, so it is not shortened.

Round seventeen (2026-11-10)

Defect, from the round 16 read (sev 2, and the ship note): Whitcombe Athletic carry a three-point deduction (note b, 15 August), shown in After Saturday as 23 -3 b but absent from Confirmed, which gave them 25 with no mark. Reproduced in the DOM at 1440 before editing: Confirmed row 3 Whitcombe 7-4-1 = 25, no mark; After Saturday 7-5-1 = 26 less 3 = 23, with the mark. The generator (tools/_bs-data.mjs, seed 43147) confirmed the cause: the 12-round table was built with no deduction, the 13-round one with it.

The reviewer wrote that Confirmed would be 22 and still 3rd. It is not: Rovers have 23, so applying the deduction moves Whitcombe to 4th and Rovers to 3rd. Fix, all in index.html:

Inventions: that the deduction counts in every week of the chart (the page does not say when the league applied it; the owner called it pre-season), and the caption sentence saying so. The deduction, its date and its wording were already on the page.