Data
Activity Feed
Displays chronological events with native list and time semantics.
Usage
Anatomy
The parts and how they nest, taken from the preview above.
Examples
Compact activity
People, actions, and timestamps in aligned rows.
Grouped by day
Date headings separate chronological event groups.
Review request
Rich details and a working acknowledgement action.
Empty activity
A clear starting point before events arrive.
Loading activity
A named loading state with hidden placeholder rows.
Load failure and recovery
An application-owned error state with a working retry using sample events.
Recommendations
| Guidance | Practice |
|---|---|
| Do | Use a consistent chronological order. Include the actor, action, and a meaningful timestamp. |
Usage boundaries
| Guidance | Boundary |
|---|---|
| Scope | Use Task List for progress through planned work. The application supplies and orders events. |
API reference
Public props from @mizen-labs/ui. Use exported prop types for the complete TypeScript contract.
| Prop | Type | Default | Description |
|---|---|---|---|
| | <ol> | Ordered event list. |
| | <li> | Responsive event row with optional media, content, and a timestamp. |
| | <div> | A wrapping content column for summary, description, details, and actions. |
| | default | Uses divided rows or a continuous thread behind optional media. |
| | <div> | Aligns the summary and time while allowing rich content to use the full column below. |
| | <div> | 36px avatar or decorative event icon, aligned with the summary. |
| | <p> | Primary event text at body size. |
| | <p> | Muted supporting event text. |
| | <div> | Inset surface for comments, attachments, and supporting content. |
| | <time> | Requires dateTime and caller-formatted text. |