Token audit before the release
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
A timeline is a vertical rail of events in the order they happened, where each row names an actor, an action and a time, and the rail carries the continuity between them. Orvain's Timeline family is five blocks split by what a row has to hold: a day's checklist hung off time chips, a mention with the text it quoted, an upload and a scheduled call, an assignment and a reaction beside a notice the system wrote itself, and attachment rows carrying the document they produced.
Most of the design work in a timeline goes into a single sentence. An avatar sits inside it, a filename is inked differently from the words around it, a chip in the middle of the line is a link, and the whole thing still has to read as one sentence when a display name runs to forty characters. The second rule is temporal honesty. Readers treat a rail as append-only, so a row edited or quietly removed costs more trust than it saves: corrections get their own row.
Every change to one customer or one order, gathered in one place. The rail answers the support question directly: it was changed on Tuesday, by this person, from this value to that one.
The life of an issue under its description: assignments, status changes, comments and the file somebody attached. Automated rows are marked differently, so nobody gets credited for what a webhook did.
A contract or an expense moving through its reviewers, each step stamped with who signed and when. It is usually read long after the fact, so no row may depend on state elsewhere on the page.
What one person got through today, with time chips showing when each thing landed and the still-open items sitting in the same column instead of in a separate list below.
A timeline is anchored to one object and tells its story in order: this document, this order, this ticket, from first event to latest. An activity feed is anchored to a person and gathers events across many objects, usually newest first and filtered to what that person is involved in. One event can legitimately appear in both.
Put the newest at the bottom when the rail tells the story of one object, because the reader is already scrolling downward and new rows should arrive where the eye already is. Put it at the top for monitoring, where the last hour matters more than the first day. Whichever you choose, do not flip the order when a filter is applied.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
A timeline is a vertical rail of events in the order they happened, where each row names an actor, an action and a time, and the rail carries the continuity between them. Orvain's Timeline family is five blocks split by what a row has to hold: a day's checklist hung off time chips, a mention with the text it quoted, an upload and a scheduled call, an assignment and a reaction beside a notice the system wrote itself, and attachment rows carrying the document they produced.
Most of the design work in a timeline goes into a single sentence. An avatar sits inside it, a filename is inked differently from the words around it, a chip in the middle of the line is a link, and the whole thing still has to read as one sentence when a display name runs to forty characters. The second rule is temporal honesty. Readers treat a rail as append-only, so a row edited or quietly removed costs more trust than it saves: corrections get their own row.
Every change to one customer or one order, gathered in one place. The rail answers the support question directly: it was changed on Tuesday, by this person, from this value to that one.
The life of an issue under its description: assignments, status changes, comments and the file somebody attached. Automated rows are marked differently, so nobody gets credited for what a webhook did.
A contract or an expense moving through its reviewers, each step stamped with who signed and when. It is usually read long after the fact, so no row may depend on state elsewhere on the page.
What one person got through today, with time chips showing when each thing landed and the still-open items sitting in the same column instead of in a separate list below.
A timeline is anchored to one object and tells its story in order: this document, this order, this ticket, from first event to latest. An activity feed is anchored to a person and gathers events across many objects, usually newest first and filtered to what that person is involved in. One event can legitimately appear in both.
Put the newest at the bottom when the rail tells the story of one object, because the reader is already scrolling downward and new rows should arrive where the eye already is. Put it at the top for monitoring, where the last hour matters more than the first day. Whichever you choose, do not flip the order when a filter is applied.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.
Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.
That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.
The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.
Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.
That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.
The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.
Tag 4.2.0 once the audit is in and the changelog is signed off.
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.
Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.
That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.
The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.
Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.
That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.
The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.
Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.
That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.
The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.
Tag 4.2.0 once the audit is in and the changelog is signed off.
Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.
Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.
Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.
That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.
The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.