System overview
Example document · edited today
Document cards
Represent a file or document with metadata and a safe next action.
Live preview
Read guide
HTML
<article class="xsh-document-card">
<span class="xsh-document-card__icon">DOC</span>
<div>
<h3>System overview</h3>
<p>Example document · edited today</p>
</div>
<a href="../../guides/installation/index.html" class="xsh-button xsh-button--secondary xsh-button--sm">Read guide</a>
</article>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-document-card | Used by the example markup and component styles or behavior. |
xsh-document-card__icon | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Link is a real documentation destination.
Implementation note. Do not label UI-only examples as downloadable assets.
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.