Timeline
Read-only chronological history with structured titles, descriptions and semantic status markers.
Purpose
Use Timeline for read-only chronological history such as activity, status changes or audit events.
Event history
Installation
With the Siteplane registry alias configured, add the component and import the installed source from your app.
CLI
pnpm dlx shadcn@4.16.1 add @siteplane/timelineImport
import { Timeline, TimelineDescription, TimelineItem, TimelineTitle } from "@/components/ui/timeline";Need the machine-readable source metadata? View registry JSON.
Usage
Timeline is for read-only chronological events. Use Stepper when the user can move between steps.
import { Timeline, TimelineDescription, TimelineItem, TimelineTitle } from "@/components/ui/timeline";
export function Example() {
return (
<Timeline>
<TimelineItem variant="success"><TimelineTitle>Build passed</TimelineTitle></TimelineItem>
</Timeline>
);
}Examples
Semantic variants, marker shapes, icon markers and activity logs are props of the same primitive.
Variants
Marker shapes
markerLabel exposes decorated markers to assistive technology as labeled images.
Custom marker
marker swaps the dot for an icon; pair it with markerLabel for accessibility.
Activity log
API Reference
The reference lists the source-owned exports and props that are easy to miss in visual examples. Inherited Base UI props remain available unless the wrapper narrows them.
- Compose
Timeline,TimelineItem,TimelineTitleandTimelineDescription. TimelineItemaccepts semantic status variants, an optionalmarker, and marker shapesbar,diamond,dotorring.- Keep title, description and optional marker content in DOM order so chronology remains understandable without visual styling.
Motion
Component motion uses the shared Siteplane motion contract. See the global motion guide for provider setup, tokens and reduced-motion behavior.
- Timeline is static by default and does not animate events on initial render.
- State accents do not require a reduced-motion override.
Accessibility
- Keep DOM order identical to the visual chronological order.
- Status must remain readable in text or another non-color cue; marker color alone is not enough.
- Timeline is read-only. Use Stepper when people can control or navigate process steps.
Implementation Guidance
- Use status variants only for real semantic meaning, not decoration.
- Do not turn a Timeline item into a hidden workflow button.
- Prefer Stepper for interactive progress and Resource List for non-chronological entity collections.