The internal reference a team keeps: tokens, component states, the accessibility bar, and the reasoning behind each.
Use this template — freeNo card. The template opens in the editor.
Design system documentation fails in a specific way — it records what was decided and not why, so the next person changes it back. This template keeps a place for the reasoning next to the value, and uses tabs and toggles so the reference stays scannable as it grows.
Code blocks
tokens and snippets with syntax highlighting
Tabs
component states without five separate pages
Toggles
the reasoning, folded away until someone needs it
Matrix grid
the accessibility bar, stated rather than implied
Diagram
how the pieces relate
Task lists
what is adopted and what is still pending
Send the document as a link rather than an attachment and it reports back: when it was opened, which sections held attention and for how long, what was skipped, and whether the reader came back on a later day.
It measures what was on screen and for how long. It cannot tell you whether someone read a word, and it does not claim to — and every recipient can see exactly what is recorded, from a link on the document itself.
Yes — a synced block holds a passage that stays identical in every document using it, so a version number or a contact is corrected once.