Reference

Design system

Every ratio was computed with tools/a11y/contrast.py against all three grounds. This page is noindex: it documents the template for whoever builds with it.

The hardest divergence in the project so far

The roadmap line for this day is "tour dates, music embeds, merch", which is almost word for word what the singer-songwriter template already is. Two adjacent days with the same brief is the exact clone-pair failure this project keeps documenting. The answer was not a different palette — it was asking what is actually different about a band, which is that a solo artist is one person deciding and a band is four people with a shared bank account and usually nothing in writing.

So the tour section here is six lines and a sentence saying that a full listing is a whole page in its own right. Deliberately refusing to build the good version of a section, because the good version already exists one day earlier, is the only move that actually prevents a re-skin.

Former members stay, and are not emitted

Two people who left are listed with dates and reasons, marked in a word with a glyph before any colour. The structured data does the opposite: only current members are emitted as member, because a departed member published as current is the same class of error as day 113 publishing a sold-out show as an available event. The page is for humans and the markup is for machines, and they are allowed to say different true things.

The accent is not a status

--member-past is its own token. On a page whose most-read section is a list of decisions about money, "left the band" must not share a hue with a heading — and it is not a failure state either, which is why it is a warm brown rather than a red.

Type

Tokens

The border token clears 3:1 against all three grounds, which is what WCAG 1.4.11 asks of a non-text boundary. It is never used for text.