Feature lists
List product capabilities with consistent icons and generous whitespace.
Live preview
- Self hosted
Deploy to your existing infrastructure.
- Semantic markup
Standard HTML and robust interaction patterns.
- Theme tokens
Customize the visual language.
<ul class="xsh-feature-list">
<li>
<span aria-hidden="true">✓</span>
<div>
<strong>Self hosted</strong>
<p>Deploy to your existing infrastructure.</p>
</div>
</li>
<li>
<span aria-hidden="true">✓</span>
<div>
<strong>Semantic markup</strong>
<p>Standard HTML and robust interaction patterns.</p>
</div>
</li>
<li>
<span aria-hidden="true">✓</span>
<div>
<strong>Theme tokens</strong>
<p>Customize the visual language.</p>
</div>
</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-feature-list | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Native list and text identify capabilities independently of icons.
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.