Components / Component reference

Alerts and callouts

Dismissible notices, semantic status treatments and editorial callouts.

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

LIVE COMPONENT REFERENCE

Alert intent variants

Semantic messaging: information, success, warning and danger. Include a plain-language description and required next step.

Actual Xshna CSSResize to test wrapping

Success notification

Your changes were saved successfully.

Warning notification

Review the pending fields before continuing.

Danger notification

The request could not be completed. Please try again.

Info notification

New information is available in your workspace.

HTML · COPY AND USE

<div class="xsh-alert xsh-alert-success" role="status"><strong>Success notification</strong><p>Your changes were saved successfully.</p></div><div class="xsh-alert xsh-alert-warning" role="status"><strong>Warning notification</strong><p>Review the pending fields before continuing.</p></div><div class="xsh-alert xsh-alert-danger" role="alert"><strong>Danger notification</strong><p>The request could not be completed. Please try again.</p></div><div class="xsh-alert" role="status"><strong>Info notification</strong><p>New information is available in your workspace.</p></div>

Overview

Add data-xsh-variant to xsh-alert. A descendant button with data-xsh-alert-dismiss removes the notice; developers must persist dismissals themselves if required.

Live example

Interactive · Real framework

System update

Everything is operating normally. This alert can be dismissed.

Example markup

<div class="xsh-alert" data-xsh-variant="info" role="status">
 <div class="xsh-alert-content"><strong class="xsh-alert-title">System update</strong><p>Everything is operating normally. This alert can be dismissed.</p></div>
 <button class="xsh-alert-close" data-xsh-alert-dismiss aria-label="Dismiss alert">×</button>
</div>

Production guidance

Do not use role="alert" for every informational message; reserve assertive live announcements for important updates.

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-alert`	Core component	CSS-only
`.xsh-alert-close`	Composable modifier / structure class	CSS-only
`.xsh-alert-content`	Composable modifier / structure class	CSS-only
`.xsh-alert-danger`	Composable modifier / structure class	CSS-only
`.xsh-alert-success`	Composable modifier / structure class	CSS-only
`.xsh-alert-title`	Composable modifier / structure class	CSS-only
`.xsh-alert-warning`	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.