Sidebar navigation
Organize administration sections into a calm and scannable side rail.
Live preview
HTML
<nav class="xsh-nav-rail" aria-label="Workspace">
<span class="xsh-nav-rail__eyebrow">WORKSPACE</span>
<a href="../../components/index.html" aria-current="page">◫ Components</a>
<a href="../../guides/theming/index.html">◈ Appearance</a>
<a href="../../guides/accessibility/index.html">◇ Accessibility</a>
<a href="../../guides/javascript/index.html">⌘ Developer tools</a>
</nav>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-nav-rail | Used by the example markup and component styles or behavior. |
aria-current | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Navigation links use native keyboard semantics.
Implementation note. Use real route URLs, not JavaScript-only clickable containers.
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.