Service

The form#

Three states: the form, what it does when it fails, and what it says when it worked. The failure matters most. A summary at the top, focused, each line a link to its field. A mark on the box is enough for a reader who sees the whole form, and nothing for one who does not.

One record#

The page behind a row of the list. Components/Content/Table draws the list and gives every row its way in; this is what the way in leads to. It is the shape any record's page falls into. Its name, what a reader can do to it, what it stands at, what it consists of, and what happened to it, in that order.

Nothing here is a class of this page's own. A value somebody copies is an sds-code block with its term as the caption. A list of commits is a table.

The status#

It reports sources, not a service: nothing here runs on a host. Two of the sources are the reader's own machine, and the page says so instead of a blank. The status colours carry the subject, and they still sit only in badges and result rows.

One source#

The page behind a row of the status list, and the only one with work in progress. Every other surface reports something settled. A reader reads this one while a job runs. A share above, the stops below, and what each one wrote inside the stop that wrote it.

A layout finds out what it lacks only under a page that changes while it is open. What does a stop still ahead offer? Where does the block a row opens onto start? What marks the current row when both status colours already mean something?

What holds until when#

The page a self-hosted project cannot do without, and almost always a bare table with colours in it. Two things fix most of it. The date the page was last true, at the top where a reader meets it. And a phase that is a word and a glyph rather than a fill. A support state in colour alone is one half the readers cannot read.

The order is the reader's: what to run now, how long each release has, what it needs, what is in progress. The archive is last, because it is for an audit and not for a decision.

What it reads and what it sends#

The page procurement reads, and the one place where an open project beats a hosted one. Somebody who has the source can check every claim here. So the page consists of things a reader can go and check, not of badges. An address for reports, a named team, an advisory history, a stated retention.

The address comes first. On most pages of this kind it is a line in the footer, where a researcher who found something gives up the search. Here it is the first thing under the heading, because it is the only part of this page with a deadline.

The page that is not there#

The address the reader asked for is the headline, the source that answered is the lead, and the search field is the nearest real thing. Three named pages, not a link to the front page. It keeps its chrome: a 404 without the header has also lost the navigation.