Data

Timeline

Vertical event timeline with completed, active, and pending states.

Quick Preview

Order placed
Jun 1, 10:00
Your order #4821 was placed successfully.
Payment confirmed
Jun 1, 10:02
Payment of $149.00 was confirmed.
Shipped
Jun 2, 14:30
Package dispatched from warehouse.
Out for delivery
Jun 4, 08:45
The courier is on the way.
Delivered
Estimated Jun 4
Package delivered to your address.

Installation

// Copy from
src/components/data/Timeline.tsx

Examples

All statuses

Completed step
Step 1
This step is done.
Current step
Step 2
You are here.
Upcoming step
Step 3
Not started yet.

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a data component named Timeline in React/Next.js.
Goal: recreate the same overall UI and behavior as the Timeline reference from a component gallery.
What it needs to communicate: Vertical event timeline with completed, active, and pending states..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Make data density readable with crisp spacing, hierarchy, and state styling.
- Use accessible labels, legends, and semantic structure when needed.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- events: TimelineEvent[] — required — Array of timeline events
- className: string — Additional CSS classes

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- 3 status states
- Custom icons
- Date display
- Connector line

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`events`*	`TimelineEvent[]`	-	Array of timeline events
`className`	`string`	-	Additional CSS classes