Skip to content
TIS Design System

TIS Design System

This documentation organizes the Design System around components. Technology is an implementation decision within the same design contract.

The v1 HTML/CSS/JS implementation remains stable. vNext publishes the real state of the four outputs defined by ADR-023; a technology is selectable only when a functional, verifiable implementation exists for that component.

Start with components

Section titled “Start with components”

The component catalog organizes all 26 contracts by purpose and shows the status of all four implementations. Functional outputs open their pages; planned or unavailable outputs remain visible without offering an inert link.

Integrate with your technology

Section titled “Integrate with your technology”
  • Web CSS is the stable, framework-agnostic implementation;
  • React is distributed in beta as source through the shadcn registry;
  • Ark/Zag has independent beta adapters exposed component by component in the catalog;
  • Angular is a native beta library validated through a local tarball;
  • AI agents use structured APIs and the same human-readable pages.

How to read a component page

Section titled “How to read a component page”

Every component separates content into four views:

  • Design: preview, anatomy, variants, and states;
  • Usage: when to use, when not to use, and composition;
  • Implementation: installation, public contract, and technical architecture;
  • Accessibility: semantics, responsibilities, and validation evidence.

For architectural decisions, read Architecture and coexistence. The complete production catalog remains in the stable v1 documentation.