Status indicators
Present compact service or process status with readable labels.
Live preview
OperationalDegradedOffline
HTML
<div class="xsh-row">
<span class="xsh-indicator xsh-indicator--success">Operational</span>
<span class="xsh-indicator xsh-indicator--warning">Degraded</span>
<span class="xsh-indicator xsh-indicator--danger">Offline</span>
</div>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-indicator | Used by the example markup and component styles or behavior. |
xsh-indicator--success | Used by the example markup and component styles or behavior. |
xsh-indicator--warning | Used by the example markup and component styles or behavior. |
xsh-indicator--danger | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Each indicator has its status written in text, independently of the dot color.
Implementation note. Use accessible text rather than color-only red/yellow/green states.
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.