the glyph set

One mark per thing the backend does

Search by what the thing does, not by what it looks like. The index holds every drawing by purpose and by name, so bin finds actions-delete.

actions-document-edit actions-file-pdf actions-folder-add actions-code-merge actions-history actions-arrow-end

The set

Four figures rather than four adjectives. Every one of them is a count somebody can arrive at from the catalogue, which is the difference between a fact and a claim wearing a number.

392

glyphs

Every one of them drawn on the same 16 × 16 canvas, at one stroke weight.

4

releases answered for

12.4, 13.4, 14.3 and main. Each glyph says which of them it holds for.

0

dependencies

One sprite per category and a stylesheet. Nothing to install to read a name.

18 ms

to answer a lookup

From the bundled index, with nothing booted and no request leaving the machine.

Start where you are building

The set groups by the part of the interface it serves, not by the part of the repository it lives in. Somebody who adds a toolbar wants the first of these and will never think to open the fourth.

Records

Open, edit, move, translate and lock the things a page consists of.

Browse records

Files

Folders, uploads and the file types a listing has to tell apart at a glance.

Browse files

History

Commits, branches, comparisons — what changed, and what it used to be.

Browse history

Direction

Arrows and chevrons, including the ones that turn with the reading direction.

Browse direction

One tag, wherever it goes

The identifier is the contract. The drawing behind it can change; the name will not move, and nothing has to go into your own tree for it to render.

html

<sds-icon name="actions-document-edit"></sds-icon>

Nothing to install inside TYPO3

Every release pins a tested version of the set. Check which one before reaching for a glyph added last month — the catalogue says per glyph, not just per release.