Navigation

What sds-nav-pills, sds-nav-main and sds-tabs are lists of. A bare string is a label and nothing else — what a set of choices is, where there is nowhere to go. sds-nav-rail takes one entry instead, its pages being what is under it.

Which item is current, by position, where nothing in the list says so itself. An entry marked current wins: a list naming the page it is on is stating a fact, while active is a position in a set, and believing both at once is how two items come out marked.

The current item is a filled block, never a tint: a tint reads as "hovered" or "disabled" depending on what is under it, and this system already spends hover on a colour change.

Where an item carries a marker — a section in the bar with pages under it — the block is the pair: the fill wraps the name and the marker, and so does the focus ring. A fill around half of a control is what makes the other half look like something that arrived with the row.

Where the mark goes: the way home, from anywhere on the site.

The mark, as the file it is drawn in. It is linked like every other picture in this system — see Artwork — and it is the same construction the footer draws, so the two ends of a site cannot say the name two ways.

The name, in the machine's own spelling and never title-cased. With a brand beside it the accent rule is drawn between the two; alone, the name is the mark itself rather than the quiet half of a lockup with nothing next to it.

Where the search index is, relative to the page; setting it asks for the field as well, a site with an index having a search. search alone draws a field with nothing behind it, which is a specimen rather than a site.

The site, as one entry with everything under it. The bar works nothing out from it: whoever renders the page knows which entries are its front doors, which one the reader is inside and which page they are on, and says so with front, here and current. What the bar decides is only how much of it fits — see the contract above.

A site whose sections hold nothing may hand a flat items instead, which is the same list with the second level left out.

What the toggle is called, for a reader who cannot see it is a menu.

Where sds-theme keeps the reader's choice, where it keeps one.

What this is the list of, and the list. The entry's label is the heading over it, and the way to the section's own page where it has one; left empty there is no heading, which is right where the rail is the whole navigation there is.

Which row is current is the entry that says current, never a count from the outside: a rail has one current page wherever it sits, and a caller thinking in "third item of the second group" is thinking about the markup.

The sections, nested as deep as the page nests them. An entry pointing at this page — an href that is a fragment — is a place the reader can be in; anything else is a link and is never marked.

current on an entry is what a card, a story and a server-rendered page have instead of a reader. The page wins the moment it has been read.

The heading over the list, and what the navigation is called.

The last entry is the page itself and is drawn as text whether or not a caller gave it an href — a trail whose last step is a link is a trail that was pasted from the one above it.

On sds-tab-item. The bar takes its labels off the panels, so a composed set says everything once.

For a tab whose subject has one — a file type, a tool — never as decoration on a set that reads fine without.

On sds-tab-item: the panel that is showing. The set writes it, not a page — a set claims its panels the moment it exists, and a panel nothing has claimed shows regardless, which is what a panel is where nothing switches it.

On sds-tabs. A word, and every set carrying the same one follows the choice made in any of them. For a page stating one thing in several places — the same setting in YAML and PHP, the same command for three shells — where choosing it once is the point and choosing it four times is the annoyance.

Sets are matched by the label, not the position: a set offering YAML and TypoScript has no PHP, and one that has none of the chosen words keeps the panel it is showing rather than falling back to its first. The choice outlives the page and is an order rather than a word — picking bash where it was offered does not stop a reader preferring PHP to YAML where it was not. A set writing no sync follows nothing and is followed by nothing.

Where a page has the questions as data. An answer that is blocks — what a documentation renderer hands over — goes between the tags as sds-accordion-item instead, and then this stays empty.

More than one open at a time. The platform's own exclusivity is otherwise on, and it is on because a list is easier to read than a wall.

What the set is called. Two exclusive groups on one page must not close each other's answers. The set tells its items, so a page says it once.

On sds-accordion-item. What is asked, in the summary. The answer is whatever stands between the tags, because paragraphs, lists and code blocks are what no attribute can carry.

On sds-accordion-item. Standing open — for the first answer on a page of them, so the shape of an answer is visible without pressing anything.

On sds-accordion-item. The address of this one answer, and it lands on the answer rather than on the question: a fragment pointing into a <details> is what unfolds it, and one pointing at the element leaves it shut. So there is no rule forcing the fold and nothing watching the hash.

How many there are in all — the list, not the page. The row is told the total and the page size and divides, so nothing hands over the same fact twice.

One-based, the way it is written in the page. The current page is text, not a link.

A page's whole address, with {n} where its number goes. A list is as often at ?q=…&page=2&sort=date as at the end of a path, and a caller that can only append has to reorder the query it already has. A template with no {n} is treated as a prefix.

What was counted, in the label register. Left off, the row ends with the bare number.

Both halves or neither: a control with a target and no name cannot be read, and one with a name and no target does nothing. Missing, that end of the row is empty — an inert control is a control a reader tries.

What the row is called for a reader who cannot see that it is one.

Where the index is. Hits are resolved against the index's own address rather than against the current page — the index lists every page as the build sees them, and a reader is rarely standing in the root.

The height of the box, sds-field's own three — the box is one, so what a size changes is decided there. A bar running its controls at sm runs the search at sm too, or the row has two heights standing in it.

One entry per hit, in the order they are read. Every field sds-search-result takes is a field here, the thumbnail among them.

What was searched for. Handed to every hit, so the marking happens once and in one place, and named in the heading of an empty answer.

What was searched, said where the hits would have been. The default names the titles and opening lines a site index keeps; a caller searching something else says what that was. Blank leaves the heading alone.

Where it is, as the site's own trail. Mono, because a path is a machine-named thing.

The sentence it was found in, cut from the text and not written for the list.

What was searched for. The marking happens here, not in the caller: what is highlighted has to be what was searched for, and a page marking by hand marks what it thinks it searched for — the two part the first time a query is normalised.

What kind of thing it is — reference, guide, changelog. Optional, like the path and the release it shares its line with: where a source reports none of the three, the line is dropped rather than drawn empty, so a list of hits has no hole above its titles.

The release it holds for, where it holds for one.

The picture the thing found carries. Beside the words and never over them — a hit stays a line, so a list of them is still read down one edge. A photograph is cropped to the same box whatever shape the file is; a drawing keeps the colours it was exported with and is fitted rather than cropped.

Leave it empty where the picture repeats the title, which is most of the time: the heading beside it already names the target.

The columns. They reflow by their own minimum, so no breakpoint decides how many fit.

href makes the heading the page it names, where what the column collects is a section with a page of its own: that page is reachable from its column or from nowhere, and repeating its name as the first entry under it is a column saying the same word twice. The heading keeps the label's colour rather than taking the links' — at theirs it reads as the first entry of the list it names. A column that collects links belonging together rather than a section leaves it out.

What this is. Stated, never implied — and never whose it is. A required property rather than a slot a page may forget to fill, because a page that says nothing about itself leaves a reader to guess.

It sits under the lockup rather than in the line at the bottom, and not in the micro register that line is set in: it is the one thing in a footer somebody reads rather than scans, and fine print is what a page uses to be forgiven for what it says.

The machine's name for it, set as the machine's: a product, a package, a repository — verbatim, and never title-cased. It is the name in the lockup: a reader who scrolled this far has left the bar behind, and the mark alone is a picture they have to already know.

The mark, as the file it is drawn in — the same file the bar carries, and shown the same way.

Whose product it is, where that is a second name: the first half of the lockup, with the accent rule between the two. Left out, the mark is one name and there is nothing to separate.

Whose it is and from when. A separate line from the note because it is a separate claim.

What the reader is reading, where the site has a version. It stands in the closing line, set in mono like anything the machine names.

What has to travel with it: a licence, a legal page, the manual it was built from.

Where else it lives — a repository, a chat, a feed. At the far end of the line, because they are the one thing in a footer a reader looks for by position rather than by reading.

Drawn as the marks they are: the glyph at 24, no word beside it and no external glyph after it. The label is what the link is called and is on the element for whoever cannot see it. This is the one place a brand glyph stands alone — in a column the same link is labelled, because there it is read rather than looked for. An entry with no mark in the set keeps its label, so an account is never a link nobody can name.