Activity feeds
Display chronological changes with concise actor and event context.
Live preview
- Deploy completed
Production · version 2.4.0
- Access approved
Reviewer added to workspace
HTML
<ol class="xsh-activity-feed">
<li>
<span class="xsh-activity-feed__dot">
</span>
<div>
<strong>Deploy completed</strong>
<p>Production · version 2.4.0</p>
<time datetime="2026-10-30T10:30:00">10:30</time>
</div>
</li>
<li>
<span class="xsh-activity-feed__dot">
</span>
<div>
<strong>Access approved</strong>
<p>Reviewer added to workspace</p>
<time datetime="2026-10-30T09:10:00">09:10</time>
</div>
</li>
</ol>Installation & markup
Include the local stylesheet and script once on the page, then place the component inside a data-xsh-ui root. The example above works without a build system.
<link rel="stylesheet" href="/dist/xshna-ui.css">
<div data-xsh-ui>
<!-- Add the HTML example above -->
</div>
<script defer src="/dist/xshna-ui.js"></script>Component API
Public classes, attributes and hooks used by this example. Keep the xsh- prefix intact.
| Identifier | Contract |
|---|---|
xsh-activity-feed | Used by the example markup and component styles or behavior. |
time | Used by the example markup and component styles or behavior. |
datetime | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Native ordered list gives chronological structure; no custom behavior.
Implementation note. Activity examples are illustrative, not live event data.
Interaction contract
Behavioral components use the shared delegated runtime; visual-only primitives rely on semantic HTML and CSS. Runtime controls emit bubbling xsh:* CustomEvents; bind application handlers to those events when server persistence, API data or navigation is required.