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.
Components / Component reference
Timeline and steps
Activity timelines and ordered workflow stepper patterns.
LIVE COMPONENT REFERENCE
Timeline and stepper states
Progress is conveyed with both ordering and explicit step labels; use aria-current for the active step.
Actual Xshna CSSResponsive preview
- Created
10:00 — Project initialized
- Review
10:45 — Awaiting approval
- Published
Final step
- Profile
- Review
- Launch
HTML · COPY AND USE
<div class="xsh-ref-formgrid"><ol class="xsh-timeline"><li><strong>Created</strong><p>10:00 — Project initialized</p></li><li><strong>Review</strong><p>10:45 — Awaiting approval</p></li><li><strong>Published</strong><p>Final step</p></li></ol><ol class="xsh-steps"><li class="xsh-step" data-xsh-complete>Profile</li><li class="xsh-step" aria-current="step">Review</li><li class="xsh-step">Launch</li></ol></div>Overview
Use xsh-timeline for activity and xsh-steps with xsh-step for progress; indicate the active step with aria-current=step.
Live example
Interactive · Real framework- Project created
9:30 AM
- Design approved
11:15 AM
- Ready to publish
- Details
- Review
- Publish
Example markup
<div class="xsh-grid xsh-md-grid-cols-2 xsh-gap-6"><ol class="xsh-timeline"><li><strong>Project created</strong><p class="xsh-muted">9:30 AM</p></li><li><strong>Design approved</strong><p class="xsh-muted">11:15 AM</p></li><li><strong>Ready to publish</strong></li></ol><ol class="xsh-steps"><li class="xsh-step" data-xsh-complete>Details</li><li class="xsh-step" aria-current="step">Review</li><li class="xsh-step">Publish</li></ol></div>Production guidance
Use ordered lists because order carries meaning. State changes require application code.
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 →
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-timeline | Core component | CSS-only |
.xsh-timeline-event | Composable modifier / structure class | CSS-only |
.xsh-timeline-vertical | Composable modifier / structure class | CSS-only |
Implementation details
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.
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.