Status lists
Show a small system-health summary with readable severity labels.
Live preview
- APIOperational
- DatabaseOperational
- Background jobsDelayed
HTML
<ul class="xsh-status-list">
<li>
<span class="xsh-dot" style="color:var(--xsh-success)">
</span>
<strong>API</strong>
<span>Operational</span>
</li>
<li>
<span class="xsh-dot" style="color:var(--xsh-success)">
</span>
<strong>Database</strong>
<span>Operational</span>
</li>
<li>
<span class="xsh-dot" style="color:var(--xsh-warning)">
</span>
<strong>Background jobs</strong>
<span>Delayed</span>
</li>
</ul>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-status-list | Used by the example markup and component styles or behavior. |
xsh-dot | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Native list structure and written statuses provide nonvisual meaning.
Implementation note. Status information shown here is illustrative, not connected to monitoring.
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.