Timeline

Events with dates and status labels.

A timeline presents a plan or a bring-up roadmap as stages with a status and an optional date. It reuses the inline badge tones, so status text stays readable without JavaScript.

  1. Done2026-08

    Bring-up

    UART, U-Boot, kernel, Device Tree, microSD and eMMC.

  2. In progress2026-09

    Hardware validation

    Ethernet, USB, Wi-Fi, Bluetooth, PCIe/NVMe, HDMI, audio and sensors.

  3. PlannedQ4 2026

    Preview

    Test image with known limitations, SHA-256 and pinned component versions.

  4. Release

    Supported

    Regression matrix on a release candidate before the stable release.

{% <devlab.timeline> %}
{% <devlab.timeline_item title="Bring-up" status="done" date="2026-08"> %}
UART, U-Boot, kernel, Device Tree, microSD and eMMC.
{% </devlab.timeline_item> %}
{% <devlab.timeline_item title="Hardware validation" status="active" date="2026-09"> %}
Ethernet, USB, Wi-Fi and Bluetooth.
{% </devlab.timeline_item> %}
{% </devlab.timeline> %}
ComponentParameterRequiredDefaultDescription
devlab.timeline---List container for stage items; takes no parameters.
devlab.timeline_itemtitleYes-Stage name.
devlab.timeline_itemstatusNoplanneddone, active, planned or blocked; unknown values fall back to planned.
devlab.timeline_itemdateNoEmptyFree-form date or period label such as 2026-09 or Q4 2026, rendered as plain text.
devlab.timeline_itemlabelNoStatus nameVisible badge text; pass a localized or project-specific name.
devlab.timeline_itemheading_levelNo3Heading level for stage names, from 2 to 6. Match it to the surrounding outline.

Place devlab.timeline_item directly inside devlab.timeline. Stage bodies render Markdown, and each status is carried by the badge text, so colour is never the only signal. Use heading_level when the timeline sits under a heading that is not an h2.