Timeline: 10 Pro blocks

Timeline

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.

Get Pro to installPro10 blocksReact, Vue and Figma

MCP

November 2026 · 0 of 4 done

Friday, 6

10:30 AM

Mia ChenDesign

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.

12:30 PM

Release prep, four tasks

1:30 PM

Noah ParkEng

What the audit changed

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.

token-audit.pdf84 KB

Every block in the set#

November 2026 · 0 of 4 done

Friday, 6

10:30 AM

Mia ChenDesign

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.

12:30 PM

Release prep, four tasks

1:30 PM

Noah ParkEng

What the audit changed

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.

token-audit.pdf84 KB

Day checklist

A day of work: what happened when, what is still open, and who did it

November 2026 · 0 of 4 done

Friday, 6

10:30 AM

Mia ChenDesign

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.

12:30 PM

Release prep, four tasks

1:30 PM

Noah ParkEng

What the audit changed

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.

token-audit.pdf84 KB

Now·2:05 PM

4:30 PM

Ava Reid, Noah Park · planned

Release cut

Tag 4.2.0 once the audit is in and the changelog is signed off.

Day so far

A live day: what has happened up to now and what is still planned

November 2026 · 0 of 4 done

Friday, 6

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.

Mia ChenDesign

What the audit changed

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.

token-audit.pdf84 KB

Noah ParkEng

Day by slot

A long day to scroll: the time you are reading stays pinned

Date and mention

Thread history: the day it happened and who was pulled in

File and call

Audit trails: the upload and the booking, each with its actor

Task and reaction

Team activity: assignments, reactions and the system's own notices

Attachment events

File history: an event plus the documents it produced, each one ticked off as reviewed

Delivery tracker

Orders, shipments and any process with done, current and upcoming steps

Delivery ETA

Tracking pages where the first question is how long until it arrives

Delivery day

Same-day deliveries and any journey where the time between steps matters

When to use#

An audit trail, where the question is who did what and when.
A discussion whose replies only make sense beside the text they quote.
A day view of work, mixing what has been done with what is still open.
Feeds where automated events sit among human ones and the difference has to be visible.

The whole set, with its codePro

Pro opens the Code tab on every block here, in React and Vue, plus the Figma file and the MCP server for your editor.

Open in Blocks See plans

10:30 AM

Mia ChenDesign

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.

1:30 PM

Noah ParkEng

What the audit changed

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.

token-audit.pdf84 KB