Data & machine output

A judgement about the reader, not about the data: compact where the list is the work and scanning beats reading, airy where the rows are read rather than scanned, medium where one table has to serve both.

Lets a table wider than its column scroll inside itself rather than taking the layout with it. A property rather than a wrapper the caller has to remember: a class the element cannot emit is a class that invites the markup to be written by hand again.

How wide the table itself is, where a source said so. The class layer has no name for it and cannot have one: it is a fact about these contents rather than a kind of table, which is the reason a row carries style too.

cls is the cell class for the whole column — sds-td-name for the identifier the machine owns, sds-td-meta for anything secondary.

A cell is text, or a component where it is a piece of state rather than a value — the badge that says how a row answered. selected emits is-selected.

The language, lower case as a fence writes it. Not lang, which is the global attribute naming the human language — and since the host is display: contents, lang="json" would send every screen reader to a language tag that does not exist for the whole block.

The languages the highlighter is taught are declared rather than surveyed, and the value is open at the edges because it arrives from a Markdown fence: refusing to print a word is not a service.

A block as text, highlighted by code-lang exactly as content between the tags is. The two are the same block from two kinds of caller: content for a renderer that already holds markup, this for one that holds the source — a story, or a page that has to render statically.

Styled lines, which no attribute can carry. shell is a command, and its $ prompt is one of the three places --accent appears; ok is a success line, marked with the mono font's check because emoji are forbidden outright; comment and plain are literal. code sets a fragment inside the line as a command — a path, a flag, a tool name.

What the block is, in a sentence, above it. It may also be written between the tags as <div class="sds-code__caption"> — the form for a caption carrying markup, and for a page read before the element upgrades. Either way it belongs to the element, so the element places it.

The copy button. What lands on the clipboard is what the block says and none of what frames it — no language, no button label, and no $, which in a shell is an error. A browser with no clipboard gets no button: a control that cannot do its one job is worse than none.

An affordance in the head that is not the copy button — a filename, a count, a link to the file. It stands where that button would, so the two are an either-or: for copying, set copy and let the component own it.

The file the diff is of — a path, so it sets in mono.

context, add or del. The tint is deliberately faint, so a changed line reads as changed without the row becoming the loudest thing on the surface.

The value being documented, verbatim. Mono, like everything else the machine named, and never prettified.

Where a link to this one entry lands, and what the mark beside the name points at. Without it the entry carries no address and the mark is left off — which is what a value excluded from the index wants.

A badge beside the name. Stated where it is true and silent where it is not: a reference of fifty values, half of them marked "optional", says nothing twice as loudly.

The two the reference always states, in that order and never alphabetised: a reader comparing two entries compares them line by line.

Anything else the source named, printed the same way and in the order it was named. The label is whatever it was called and is set as a label, so since stays since.

The description, where a caller holds it as one string. Out of a document it is blocks — paragraphs, a list, an admonition — and those are written between the tags instead, which is what the entry keeps every one of.