Installation
A3S UI is published on npm. Install the stable package from the registry; GitHub installs remain useful only when testing unreleased source changes.
Package installation
Install the package
Import Tailwind and A3S UI
The default export includes base tokens, every component, and the A3S style pack. Load it after Tailwind so a later preflight does not reset component boundaries or controls.
Load interactive components
Most components are CSS-only. Import the complete runtime when the application uses menus, select, tabs, split panes, or other interactive composites.
Or import the runtime once and only the controllers you use.
Use semantic markup
CSS imports
Split imports
Use split imports when application CSS already owns its dependency graph.
JavaScript imports
The public runtime namespace is window.a3sUI. It initializes registered components on page load and observes newly inserted DOM.
Dockview layout integration
Install the Dockview 8.1 MIT package and the host-framework adapter when an application needs a dockable workspace. This integration is separate from the 116 semantic components and does not enter the default CSS or JavaScript runtime.
See Dock Workspace for complete capability and licence boundaries.
Server-rendered templates
Optional Nunjucks and Jinja templates ship with the package.
See Templates for macro parameters.
Semantic and framework adapters
The package also ships a machine-readable component manifest, a small DOM annotation runtime, and optional React and Vue element adapters. These entrypoints preserve the same semantic HTML contract; they do not contain application state, task transport, or product logic.
React and Vue are optional peer dependencies. Install only the framework used by the host application, then import components from @a3s-lab/ui/react or @a3s-lab/ui/vue.
See Integration for native HTML, React, Vue, manifest, selector, snapshot, and deterministic test examples.
Icons
Icons are deliberately not bundled. Documentation examples use inline Lucide-compatible SVG, but applications may use any icon system. Icon-only controls always need an accessible name.
