Content

Named for the fill each one is. raised sits on the canvas and has to read as a plane; sunken is machine output — code, logs, structured content.

The plane with no fill is not one of its answers: an unfilled hairline plane carrying a title and prose is sds-card, down to the class it writes.

The statement. heading and not title, which is a global attribute.

It may also be written between the tags, which is the form a document uses: a plane on a product surface holds a sentence somebody composed and a property carries it, while a passage set beside an argument is paragraphs, a list or a block of its own — markup, or nothing.

The tracked-out line over the title, where a set of these is numbered or named as a set. A title carrying the number reads as part of the sentence.

A glyph above the label, where a set is told apart before it is read. It never stands alone.

Layout for the plane. The host draws nothing, so this is what reaches the element that is actually laid out.

Left empty there is no heading at all — a card holding a byline or a figure names itself inside its own body, and an empty heading is a level in the document outline with nothing under it.

A sentence as a property lands in a paragraph; blocks written between the tags land in a container, because a document's summary is paragraphs and often a list.

Where the card goes. Without one the title is a title and the card is not a target either.

The picture. Named src because everything in this system that takes a file names it src.

The tracked-out line over the title: what a set of cards is named or numbered as, or when the entry is from — the same register and the same line.

What kind of thing it is. Drawn as a badge beside the label, with no tone, because it is a fact about the card rather than a result.

One line under a hairline: what the reader gets there, who it is for, what state it is in.

The call to action, in words. Drawn only where there is an href, since it says the card goes there.

How wide the set runs, or whether it runs as a wall at all. flush is the gutter taken out — the cards share a hairline and the set reads as one block.

Concrete — 5, 240, 12.4+ — never "many". Set in sans: mono means the machine named the thing, and a count is a fact about the software rather than a string it returns.

What the figure is in — ms, %, kB. Its own property rather than part of the value: the element sets it a step down and joins it with the narrow no-break space a number may not be split from, and a page that has to know that codepoint is a page that will forget it.

What was counted, in the label register.

The whole the figure is a part of, said after it — 2 of 3 — a step down and a shade back, the way a unit is. Only where the figure really is a part: a measurement is out of nothing. It is words and not a bar, because a set of figures is read across its notes, and a drawing under one of them pushes that line out of step with the rest.

A glyph over the figure. Muted and never in a status colour, for the reason a card's is: a figure is a subject, not a result.

What the figure is bounded by. Without one the number is a boast — and this is the whole reason the component exists rather than two divs.

Long enough to be worth borrowing, short enough to stand at heading size: a borrowed sentence is a statement and is set like one. No quotation marks are drawn — the block is set apart by its measure, its size and a rule at its start, which is position rather than ornament.

Who said it: a person, a document, a release note.

What they are to the subject, where the name alone does not say.

Where it can be read in full. The attribution carries the link.

When, and anything else in the label register: a release, a revision.

The mark, drawn only where these are given. A byline derives initials from the name because a byline is a person; a quote does not, because half of what is worth quoting is a document, and a monogram of a filename is a person invented for a source that has none.

When, and anything else in the label register: a release, a reading time, a revision.

The mark. Taken from the name where it is not given, and two letters at most. Never a photograph: a face is a file to fetch, keep in step and hold a licence for, and none of that says who is answerable.

Where the name leads — a profile, or the source it is attributed to.

No monogram, for an attribution that is not a person: a document, a release note, a file. Initials derived from a filename are a person invented for a source that has none.

Not decoration: ok names where an answer came from, warn a degraded one, error none, info a fact about the surface. Only warn tints the block.

The fact, in a line. Sentence case, and never a category name. Optional, because a note whose body is a document's own prose has nothing to head it with.

Or nothing, when the body is written between the tags instead.

An explicit glyph, where the tone's own says less than the note does. The glyph is never dropped: a colour alone leaves the meaning to whoever can tell the tones apart.

What the glyph says out loud. Each tone names its own word, and a caller may say a truer one — a renderer collapsing many admonition types onto these tones knows which this was, so caution and danger stay apart after both became warn.