A sixty-page PDF is a beautiful artefact and a terrible tool. It goes stale within a quarter, it cannot be searched properly, and nobody can copy a hex value out of it without squinting.
The same content published as a small website solves all three problems and costs about the same to produce.
Tokens, not screenshots
Colour swatches that copy to the clipboard. Type scale rendered in the live typeface at real sizes. Spacing shown as CSS custom properties your engineers can paste directly.
When the manual is the source of the tokens, drift between design and code stops being inevitable.
When the manual is the source of the tokens, drift stops being inevitable.
Rules with reasons
Every rule in a manual should carry a one-line reason. 'The accent appears once per composition, because restraint is what makes it read as emphasis.' A rule with a reason can be applied to a situation you did not anticipate. A rule without one gets ignored the moment it is inconvenient.
Working on something where this applies? I take on three or four substantial engagements a year. Start a conversation. It costs nothing and usually clarifies more than it takes.
