Timeline

Timeline

Things one under the other, each on a marker, joined by a line: the steps of a procedure, the events of a history, the stages of a run. What each holds is free — a line of text, a table, a form — and the line runs down the whole of it, to the next marker.

Steps in order

Numbered, with the three states the stepper knows: the steps behind are drawn solid, the one being done stands out, those ahead wait.
  1. Get the sources

    Clone the repository and install its dependencies.

  2. Configure

    Copy the example environment and fill in the database address.

  3. Create the database

    Run the migrations; this is the step in progress.

  4. Deploy

    Build the assets and publish the release.

Anything under a title

Each item holds whatever it needs — properties, a message, buttons. An icon replaces the dot, and a tone colours the marker the way it colours a marker or a block.
  1. Order placed
    14 March, 09:41
    Reference
    ORD-2026-0142
    Amount
    € 184.00
    Payment
    Card ending 4242
  2. Payment received
    14 March, 09:42
  3. Shipped
    15 March, 16:05
    Running late

    The carrier announces one more day.

  4. Delivery

A history

No order to follow, only events: dots, a date under each title, and a category colour where it tells something.
  1. Version 2.0 released
    2 September
  2. Reviewed by the team
    28 August
  3. First draft
    12 August

Steps not decided yet

As on the stepper: a step that depends on an answer not given yet takes no number and moves none of the others.
  1. Get the sources
  2. Choose a plan
  3. Depends on the plan
  4. Deploy

Written by hand

The component is only a way of writing the shape from a list. The same classes written in the page give the same timeline, with anything in it.
  1. A plain dot
  2. An icon in place of the dot

    Any markup, written in the page.

In vue

The same timeline in a vue tree. What the twig takes as markup is a scoped slot there, so a component can stand under an item's title.