Components / Component reference

Navigation and breadcrumbs

Navbar, link groups, breadcrumb trail and active navigation states.

V1 BETA / DOCUMENTEDLive variants · API · Accessibility · Responsive guidance

LIVE COMPONENT REFERENCE

Navigation states and pagination

Use aria-current for the active destination; every navigation region should have an accessible label.

Actual Xshna CSSResize to test wrapping

HTML · COPY AND USE

<nav class="xsh-nav" aria-label="Example section navigation"><a class="xsh-nav-link" aria-current="page" href="#xsh-gallery-navigation">Overview</a><a class="xsh-nav-link" href="#xsh-doc-code">Examples</a><a class="xsh-nav-link" href="#xsh-doc-guidance">Guidance</a></nav><nav class="xsh-breadcrumb" aria-label="Breadcrumb"><a href="../index.html">Documentation</a><a href="buttons.html">Components</a><span aria-current="page">Navigation</span></nav><nav class="xsh-pagination" aria-label="Example pagination"><a class="xsh-page-link" href="#xsh-gallery-navigation" aria-label="Previous page">←</a><a class="xsh-page-link" href="#xsh-gallery-navigation" aria-current="page">1</a><a class="xsh-page-link" href="#xsh-gallery-navigation">2</a><a class="xsh-page-link" href="#xsh-gallery-navigation">3</a><a class="xsh-page-link" href="#xsh-gallery-navigation" aria-label="Next page">→</a></nav>

Overview

Use xsh-navbar, xsh-navbar-nav, xsh-nav-link and xsh-breadcrumb with aria-current=page for current location.

Live example

Interactive · Real framework

Example markup

<nav class="xsh-navbar" aria-label="Example navigation"><strong class="xsh-brand">Xshna</strong><ul class="xsh-navbar-nav"><li><a href="#" class="xsh-nav-link" aria-current="page">Overview</a></li><li><a href="#" class="xsh-nav-link">Products</a></li><li><a href="#" class="xsh-nav-link">Company</a></li></ul></nav>
<nav aria-label="Breadcrumb"><ol class="xsh-breadcrumb"><li><a href="#">Home</a></li><li><a href="#">Library</a></li><li aria-current="page">Components</li></ol></nav>

Production guidance

Navigation link targets in demos are placeholders. Use valid routes and a label for each nav landmark.

Customize this component through --xsh-* CSS tokens, data-xsh-* configuration attributes and documented xsh-* utilities. Use the optional JavaScript distribution only when an interactive behavior is needed.

Build with confidenceOpen interactive design playground →

EXACT NAMES FROM THE SHIPPED STYLESHEETS

Complete selector inventory

These selectors exist in the current distribution. An entry in this table does not imply that arbitrary modifier combinations are meaningful; use the examples above for the intended composition.

Class	Purpose	Delivery
`.xsh-nav`	Core component	CSS-only
`.xsh-nav-link`	Composable modifier / structure class	CSS-only

ENGINEERING AND INTEGRATION

Implementation details

Semantic structure

Use the documented Xshna classes with semantic HTML rather than replacing native elements unnecessarily.

Compose existing xsh- classes on the appropriate HTML element. Keep content order meaningful when CSS is disabled.

Interactive behavior

Verify focus order, disabled behavior and descriptive labels for interactive patterns.

Load xshna.min.js only if the documented interaction needs it. Your application remains responsible for data, persistence and business rules.

Responsive and localization

Test narrow containers, long translations and user-defined text sizes.

Test 320px-wide viewports, container-constrained instances, keyboard zoom, longer translations and right-to-left text where relevant.

Theme and customization

Use --xsh-* CSS variables for theme values and data-xsh-design / data-xsh-density on the xsh-app root.

Prefer design tokens over hard-coded overrides so components remain coherent across personalities.

ACCEPTANCE CHECKLIST

What to verify before shipping

Confirm every documented class used by the feature exists in the release CSS.
Navigate controls using Tab, Shift+Tab, Enter, Space and Escape where appropriate.
Test with reduced motion, high contrast, 200% text zoom and a narrow mobile viewport.
Verify disabled, loading, empty, error and long-content states where relevant.
Check actual application behavior independently of the preview: these examples use illustrative data.