lab · exploring

Timeline in practice

Real product screens on one Timeline (issue activity, order tracking, a support conversation with a reply thread, a deploy pipeline, a changelog, a narrow notification feed, a security audit log and a day agenda) that between them use every marker, state, size, line, slot, separator, collapse and date format.

frameworksastro
Exploringtimelinecardavatarstampbadgebutton
scenarioIssue activity

A small timeline in a card mixes dot events, a status change with badges in the heading, an avatar comment with a card body, a full-bleed comment, a review with actions, a markerless row and a collapsed run. Every heading should sit on its marker's centre line, and badges should not push the meta onto its own line.

PIN-214

Retune the danger ramp for dark mode

Opened by Marta Silva in Color system

In review
scenarioOrder tracking

A large step tracker with times: reached steps fill and colour the line, the current step is ringed, the rest are hollow and muted. The courier card in the current step's body should not stretch the rail. The cancelled order on the right ends on a danger step with its own marker and a custom state word.

Order #1042

2 items · Standard shipping

Order #1039

1 item · Express

scenarioSupport conversation

A comment section with no connector between top-level comments: avatar markers, author and relative time in the header, reactions in the footer, an internal note on a warning card, and a reply thread that drops to the small size by itself. The thread's collapse starts expanded, so 'Hide replies' should show on first paint.

scenarioDeploy pipeline

A CI run with a dashed connector: a stage eyebrow above every step (the marker stays on the title), a meta slot whose parts join with a dot, success, warning and danger stamps, a failing job whose log sits in a card, retry and logs actions, and steps that have not run yet drawn as upcoming state stamps.

Deploy #2291 to production

main · a1f9c3e · triggered by Kenji Mori

Failed
scenarioRelease history

A large changelog grouped by month. The month labels sit on the rail at the left, and the line runs through them unbroken. Each release has a version badge in its heading, a rocket stamp, a bullet list body and a link action.

scenarioNotification feed in a narrow panel

A 320px column: long headings must wrap under themselves (never under the marker), the meta wraps after the heading, unread items use a primary dot and read ones neutral, and grouped follow-ups use markerless rows.

Notifications

scenarioSecurity audit log

Absolute UTC timestamps in a monospace time (passThrough.time), a custom meta slot with device and place, danger stamps for a blocked sign-in, a custom formatter, every meta inline after its heading (a dense log), and a long run of routine sign-ins collapsed at the end of the list — the toggle row should draw no trailing line.

scenarioDay agenda

A schedule split by separators, with same-day time ranges as the kicker above each title, past meetings as done steps, the meeting in progress as the current step on a full-bleed card, and attendee avatars in an actions row. Ranges that end today read as plain ranges unless they are running now.