EventTimeline
Place regimes, events and calendars on one time axis a reader can inspect.
@luc/ui/chartsWhat it shows
Place dated events on a shared time axis, optionally with guide lines that connect them to a surrounding reading.
Live preview
Six dated events grouped by category; the timeline enriches the axis rather than replacing it.
<EventTimeline
events={[
{ at: "2026-01-15", label: "Rate decision", category: "Macro", tone: "info" },
{ at: "2026-03-02", label: "Earnings", category: "Company", tone: "accent" },
{ at: "2026-04-18", label: "Index rebalance", category: "Index", tone: "neutral" },
{ at: "2026-06-09", label: "Volatility spike", category: "Market", tone: "negative" },
{ at: "2026-08-27", label: "Guidance cut", category: "Company", tone: "accent" },
{ at: "2026-10-06", label: "Rate decision", category: "Macro", tone: "info" },
]}
guides
height={260}
ariaLabel="Event timeline"
/>Controls
Height
A chart measures its container, so it always needs a definite height.
State
The surface the chart is in — loading, empty and error are drawn by the component.
Accessible name
A drawing is not readable by a screen reader, so it needs a name that states what it shows.
The same fixture as the live preview above; the controls change how it is drawn, not what it measures.
Code
import { EventTimeline } from "@luc/ui/charts";
<EventTimeline
events={[
{ at: "2026-01-15", label: "Rate decision", category: "Macro", tone: "info" },
{ at: "2026-03-02", label: "Earnings", category: "Company", tone: "accent" },
{ at: "2026-04-18", label: "Index rebalance", category: "Index", tone: "neutral" },
{ at: "2026-06-09", label: "Volatility spike", category: "Market", tone: "negative" },
{ at: "2026-08-27", label: "Guidance cut", category: "Company", tone: "accent" },
{ at: "2026-10-06", label: "Rate decision", category: "Macro", tone: "info" },
]}
guides
height={260}
ariaLabel="Event timeline"
state="ready"
/>Not controllable here
series / rows— The numbers are the caller's; the fixture above is the example.
Copy for an AI agentA specification an agent can act on: the import, the setup, the chosen props, the data contract and the accessibility expectation.
Implement `EventTimeline` from Luc UI. It is: Place regimes, events and calendars on one time axis a reader can inspect.
Import it with: import { EventTimeline } from "@luc/ui/charts";
Requires: react ^19.0.0; react-dom ^19.0.0; react-hook-form ^7.0.0 (optional, for @luc/ui/forms/react-hook-form); tailwindcss ^4.0.0; node >= 22 (repository tools). Import the stylesheet once at the app root and wrap the tree in `LucProvider`. Both come from the package that publishes @luc.
Chosen configuration: `height={260}`, `state="ready"`, `ariaLabel="Event timeline"`.
Accessibility: keep the component's own semantics. Do not re-implement its ARIA wiring, do not add roles it does not declare, and make sure every interactive element is reachable and operable from the keyboard with a visible focus state.
Styling: use Luc UI design tokens and the component's own props. Do not restyle with raw colour literals and do not override the component's internal structure with page CSS.
Motion: respect `prefers-reduced-motion`. The component already does, so do not disable it.
Reproduce this state:
```tsx
<EventTimeline
events={[
{ at: "2026-01-15", label: "Rate decision", category: "Macro", tone: "info" },
{ at: "2026-03-02", label: "Earnings", category: "Company", tone: "accent" },
{ at: "2026-04-18", label: "Index rebalance", category: "Index", tone: "neutral" },
{ at: "2026-06-09", label: "Volatility spike", category: "Market", tone: "negative" },
{ at: "2026-08-27", label: "Guidance cut", category: "Company", tone: "accent" },
{ at: "2026-10-06", label: "Rate decision", category: "Macro", tone: "info" },
]}
guides
height={260}
ariaLabel="Event timeline"
state="ready"
/>
```Usage
The values are prepared by the caller: this component draws the points it is given and computes no statistic of its own, so units, scaling and any summary have to be settled before the data reaches it.
It is drawn by the ECharts engine.
Worked examples with real data are on the family overview: Time series & sequence
import { EventTimeline } from "@luc/ui/charts";<EventTimeline
events={[
{ at: "2026-01-15", label: "Rate decision", category: "Macro", tone: "info" },
{ at: "2026-03-02", label: "Earnings", category: "Company", tone: "accent" },
{ at: "2026-04-18", label: "Index rebalance", category: "Index", tone: "neutral" },
{ at: "2026-06-09", label: "Volatility spike", category: "Market", tone: "negative" },
{ at: "2026-08-27", label: "Guidance cut", category: "Company", tone: "accent" },
{ at: "2026-10-06", label: "Rate decision", category: "Macro", tone: "info" },
]}
guides
height={260}
ariaLabel="Event timeline"
/>Data contract
`events` contain `at`, `label` and optionally `category`/`tone`; `guides` toggles the vertical guides. Dates and categories are supplied metadata, not inferred from the label.
Important configuration
Choose `guides` only when the event relation to the axis matters, use category/tone consistently, and keep labels short enough to avoid collisions.
Guidelines
When not to use
Do not use an event timeline for undated sequence steps; use a process or milestone chart when the order, not the date, is the fact.
Configuration
| Export | Kind | Signature |
|---|---|---|
EventTimeline | 15 documented props | ({ events, guides, format, labelMode, range, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, eager, }: EventTimelineProps) => import("@types/react").JSX.El… |
EventTimeline props
Type: EventTimelineProps
Values the compiler reads from the declaration.
| Prop | Type | Default | Notes |
|---|---|---|---|
ariaDescription? | string | undefined | — | |
ariaLabel? | string | undefined | — | |
className? | string | undefined | — | |
description? | string | undefined | — | |
eager? | boolean | undefined | — | Create the engine on mount rather than when the surface is approached. |
events | readonly TimelineEvent[] | — | |
format? | ChartFormat | undefined | — | |
guides? | boolean | undefined | — | Draw vertical guides from the axis to each marker. |
height? | string | number | undefined | — | |
labelMode? | "auto" | "never" | undefined | — | When to print each event's own label beside its marker. A sparse history (a handful of halvings, the Pi Cycle crossovers) reads better with the label on the marker: the reader sho… |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
range? | { ranges: readonly string[]; value: string; onValueChange: (value: string) => void; windo… | — | A presentation window over the events the caller already holds. A fifteen-year transition history is unreadable on one axis, so the plate offers the same lookback presets every ot… |
state? | ChartState | undefined | — | |
title? | string | undefined | — |
Accessibility
A chart is a picture of data, so it needs a name that states what it shows, and the numbers must exist as text somewhere on the page — in a table or a written summary — because a drawing is not readable by a screen reader and cannot be copied.
What happens on the server, and when hydration changes it.
Family
Time series & sequence
Regimes, events and calendars over a shared inspection cursor.
Related