Application shells
Combine navigation, workspace header, and content using a responsive structure.
Live preview
Application overview
A compact responsive enterprise shell.
HTML
<div class="xsh-app-shell">
<aside>
<strong>Northstar</strong>
<nav aria-label="Preview sections">
<a href="../../components/index.html">Overview</a>
<a href="../../guides/installation/index.html">Settings</a>
</nav>
</aside>
<div>
<header>Workspace / Dashboard</header>
<main>
<h3>Application overview</h3>
<p>A compact responsive enterprise shell.</p>
</main>
</div>
</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-app-shell | Used by the example markup and component styles or behavior. |
aside | Used by the example markup and component styles or behavior. |
main | Used by the example markup and component styles or behavior. |
header | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Navigation and main content use landmarks and real anchor elements.
Implementation note. A full app should expose one main landmark and a clear heading hierarchy.
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.