Hello! How can I help with your order?
COMPONENTS
Message thread
One ordered-list layout arranges existing cards as conversation messages, keeping sender names, timestamps and reading order explicit.
Usage
Markup: ol.message-thread > li > article.card
Behaviour: Ordered static history. Sending, real-time updates and announcements belong to the application.
- Use ol.message-thread > li > article.card. Existing cards supply surfaces and optional materials; existing avatars are optional. Header and footer remain semantic elements.
- Use the existing data-variant="primary" on an outgoing message card to align it to the logical end. Include a visible sender such as "You"; alignment or colour alone must not identify ownership.
- Messages remain in DOM order. Native time[datetime] identifies each timestamp. Visible text can supply delivery state; CSS does not invent delivery or read status.
- The application supplies composing, sending, live updates and unread announcements. This module adds no role="log", automatic scrolling or live-region behaviour to a static history.
Component API and styling module · Inherited appearance settings
A support conversation
Existing cards and avatars with one thread layout class.