Getting started / Component reference

Architecture

Modular cascade layers, component APIs, a predictable token system and optional scripts.

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

Overview

The distributable is ready to use. Maintainers may regenerate the predefined utility catalogue using Python 3, then rebuild the package. You never need a Node process.

Live example

Interactive · Real framework

Scoped and portable

Global styles outside this root are not reset.

Example markup

<div class="xsh-app">
  <div class="xsh-container">
    <div class="xsh-card xsh-p-6">
      <h2 class="xsh-h3">Scoped and portable</h2>
      <p>Global styles outside this root are not reset.</p>
    </div>
  </div>
</div>

Production guidance

Layer order: xsh.reset → xsh.tokens → xsh.base → xsh.layout → xsh.components → xsh.motion → xsh.utilities → xsh.overrides.

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 →

REFERENCE CONTRACT

Files, tokens and configuration

Surface	Source of truth	What to check
`dist/xshna.min.css`	Compiled framework	Styling and responsive behavior
`dist/xshna.min.js`	Optional interactions	Lifecycle, event handling and teardown
`src/css/`	Readable source	Public class names and token definitions
`src/contracts/`	Published component contracts where available	State, configuration and behavioral support

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.