Every component in the language, grouped by layer. Each page carries live examples, the markup that produced them, its knobs, and the rules it answers.
The control everything else is measured against: an outlined box at the control weight that gains its block under the cursor. One button per view is the primary.
On or off for one setting, when nothing else is on screen to compare it against. The track fills to assert the state; the slug that moves is the ink line in both states.
A control that is only its label. Not a button, which draws a box; not a link, which goes somewhere. It does something to the view you are already looking at.
Boon uptime
The third stays red under the cursor: the hover weighs one class, so the ink lands on top of it.
One line of text on the darkest surface in the language, so it reads over anything it lands on. The box is the language's; the coordinates are the consumer's.
A button and a popover wearing the closed box and list styling of a select - the dropdown to reach for when the platform will not let the language draw the native one.
Real checkbox and radio inputs with the browser control painted out. They submit, tab and toggle with no script, because they are the control rather than a picture of one.
The centred column every view sits in, at one of three measures. The default suits a browsing view; the two modifiers exist because prose and dense catalogs genuinely disagree about width.
Narrow measure
Reading width, inside a page that has already paid its gutter.
An auto-filling card grid whose minimum column width is per-instance, because a grid of ten app cards and a grid of sixty catalog entries are the same component with different minimums.
A picker choosing what the surface beside it shows. Two objects on one plane — the list is sunk into the panel, the thing it picked stands out of it — rather than two panels parted by a hairline.
One thing you can open, drawn as a raised surface you press. Its optional top strip is the one place a card carries colour, and only when there is real data to put in it.
The drag strip across the top of a window, filled with the ink line so the app's content reads as sitting inside the outline rather than under a second toolbar.
AxiBridge — watching 4 folders
The strip is the drag handle; the buttons opt back out of it.
Vertical navigation, for a set too large for a tab strip to hold. The category you are on is filled and blocked; a section under it is brightened text.
A real <dialog>. Focus trapping, Esc-to-close, inertness and the top layer come from the browser rather than from a script this language does not ship.
A stack of transient messages in the corner of the page. The CSS ships the region and the message; appearing and leaving on a timer are the consumer’s, because this language ships no script.
A ranked list of rows inside a panel. Rows are separated by rules rather than outlined or blocked, because the panel is the raised thing and the table is its interior.
A framed line chart, its horizontal gridlines drawn as hard stops in a repeating gradient. The geometry is the consumer's; the ink and weight are the language's.
A scope that draws a charting library's furniture in the language: grid, axis, ticks, hover band, legend and brush in the neutral ramp, every series kept in its own colour. Bound to recharts.
A cited quotation, marked by an accent rule down its left edge - the only place in the language where colour marks a block rather than filling a shape.
Third-party programs are used at your own risk — ArenaNet tolerates addons rather than endorsing them.
The five meanings and the three neutral steps, as single-purpose classes. For a mark that carries a status or a comment where there is no component to carry it - a number in a sentence, a word in a legend.
Uptime 99.2% against a
94% floor (rolling 30 days).
Every interactive object fades and refuses the pointer when it carries `disabled` or `aria-disabled="true"`. No class to add: the state is declared once, for all twenty-four of them.
A scrollbar down the side of a narrow strip is a channel, not information. The class says it for a consumer’s own scroller; the strips the language ships say it in the same rule.
Every scrollbar is a rectangle of the rule ink in a transparent channel. Nothing to write: it is declared once, in base.css, for the page and every pane and well that scrolls.