Timeline
Displays a dynamic, ordered activity history with status colors and optional item actions.
Live TypeScript example
Try the component here, then use the source below in your application.
Interact with the Timeline example. The code below shows its actual inputs and callbacks.
import '@bluui/web/styles.css'
import { createTimeline } from "@bluui/web";
export function mount(host: HTMLElement) {
return createTimeline(host, {
"IsCompact": false,
"IsReversed": false,
"Items": [
{
"Key": "created",
"Title": "Order received",
"Description": "Order #BLU-1042 was placed by Jordan Lee.",
"Timestamp": "Today · 09:12",
"Color": "Success",
"Icon": "✓"
},
{
"Key": "paid",
"Title": "Payment confirmed",
"Description": "$249.00 paid by card.",
"Timestamp": "Today · 09:14",
"Color": "Success",
"Icon": "✓"
},
{
"Key": "packing",
"Title": "Preparing shipment",
"Description": "Your order is being packed by the warehouse team.",
"Timestamp": "Today · 10:30",
"Color": "Processing",
"ActionLabel": "View order"
},
{
"Key": "delivery",
"Title": "Estimated delivery",
"Description": "Arriving in 2–3 business days.",
"Timestamp": "Oct 14–15",
"Color": "Default"
}
]
}, { ItemClick: key => { host.dataset.activity = key; } });
}
const instance = mount(document.getElementById('example')!)
// When this page or framework component is removed:
// instance.destroy()
Install the library and add the host element
npm install https://bluui.blutekmedia.com/downloads/bluui-web-0.2.6.tgz<div id="example"></div>This example uses the downloadable @bluui/web package. Your application handles persistence and authentication through its typed callbacks. The starter ZIP includes this same example.
This reference documents the published Block’s parameters, events, and types. The web examples adapt those inputs to browser callbacks. Open native showcase ↗
- Web examples
- Supported4 states checked · no automated failures
- TypeScript
- Supported2 states checked · no automated failures
- OutSystems
- Needs work2 states checked · 2 rule failures
Minimum requirement: WCAG 2.1 AA. Supported means the listed checks passed; full conformance is not yet declared.
Evidence and remaining verification →Purpose and use
Displays a dynamic, ordered activity history with status colors and optional item actions.
Keyboard design guidance
Activity items follow list order. Optional item actions are keyboard accessible.
This describes the intended interaction. The dated audit above identifies verified behavior and current gaps.
In your application
Provide useful labels, preserve visible focus, and test the component with your actual content. Use text alongside status colors and check contrast in each state.
Events0No events yet.
Interact with an example to see its events.