Semantic HTML first
Native controls keep browser behavior, forms, keyboard interaction, and assistive-technology semantics visible.
A lightweight, zero-runtime component system. Each component is semantic HTML plus Forma CSS, published under a readable <forma-*> tag that is never registered as a Custom Element. The browser owns native behavior; your application owns everything else.
Link the built stylesheet and write the component's canonical HTML inside its tag. There is nothing to register or initialize.
<link rel="stylesheet" href="/path/to/forma/dist/all.css">
<forma-switch class="forma-component-tag">
<label class="forma-switch">
<input class="forma-switch__input" type="checkbox" role="switch" name="notifications">
<span class="forma-switch__track" aria-hidden="true"></span>
<span class="forma-switch__text"><span class="forma-switch__label">Notifications</span></span>
</label>
</forma-switch>
Click or tap the code once to select all of it, then copy.
Every component has one primary family and a page with purpose, live examples, a mobile example, copyable HTML, API, states, accessibility, responsive and motion notes. Prefer the A–Z index if you know the name.
Buttons and grouped commands that start work. Forma styles the native control; the application decides what an action does and whether it is currently legal.
Button, Command group, Mobile action bar, Overflow command disclosure
Native text, date, numeric, range, file and toggle inputs with delegated labels, help text and form participation left to the browser.
Checkbox, Combobox, Date and time field, Date range, File upload queue, …
Radio- and checkbox-backed choice structures: segmented controls, choice cards, multi-select guidance and hierarchical selection.
Choice group, Hierarchical choice, Hierarchical multi-choice, Image choice, Multi-choice, …
Question shells and response scales that keep Unanswered distinct, keep radio semantics per row, and never compute scores.
Allocation, Best–Worst, Binary choice, Ordinal scale, Pairwise choice, …
Where am I and where can I go: shells, tabs, pagination, scope trails, trees, wizards and skip links.
Hierarchy tree, Navigation shell, Pagination, Scope trail, Skip link, …
Alerts, notifications, validation, loading and progress, and explicit operation states that never collapse unknown into failure.
Alert, Conflict review, Empty state, Freshness, Obligation panel, …
The Aegis fault presentation family: safe inline, notification, banner and blocking faults with application-authorized recovery.
Diagnostic status, Fault, Fault banner, Fault blocking, Fault details, …
Native dialog, Popover API and details/summary surfaces: modal dialogs, edge flyouts, popovers, tooltips, menus and disclosure.
Action menu, Dialog, Disclosure, Flyout, Overview disclosure, …
Intrinsic, container-aware composition primitives that recompose by available space without reordering source.
Multi-region application compositions: workspace shells, master/detail, split panes, dashboards and record headers.
Application identity, Dashboard grid, Focus stage, Master/detail workspace, Preview surface, …
Tables, ledgers, key-value lists, metrics, timelines, diffs, collections and relationship displays.
Active filter summary, Collection toolbar, Comparison grid, Comparison pairs, Data grid, …
Presentation-only building blocks for boards, diagrams and spatial canvases; geometry, routing and editing stay in the application.
Command palette and the CharacterGrid terminal family for keyboard-driven, fixed-cell interfaces.
Character grid, Character grid 3270 profile, Character grid field, Character grid keys, Character grid reveal, …
Composer, conversation, understanding review and handoff surfaces that keep agent proposals inspectable and human authority explicit.
Composer, Conversation, Handoff summary, Understanding review
Visual Engineering contracts for first-glance priority, bounded emphasis, and recognize-verify-act flows.
Security results, evidence, exceptions and unknowns presented with explicit text state rather than color-only pass/fail.
Security blockers, Security evidence age, Security evidence chain, Security exception, Security invariant result, …
The brand-neutral marketing and documentation presentation family: shell, header, hero, sections, cards, prose and footer.
Small structural helpers: visually hidden text, text roles and other composition aids.
Forma standardizes presentation without becoming a second application runtime.
Native controls keep browser behavior, forms, keyboard interaction, and assistive-technology semantics visible.
Tokens, layout, state styling, responsive behavior, physics-derived motion and forced-color support live in the design system.
Limen/application code supplies non-native behavior. Ordo/domain state decides what transitions are legal. Aegis supplies safe fault presentation data.
Every component works at 320 CSS pixels without page-level horizontal scrolling and keeps approximately 44px touch targets. Mobile reference.
Non-color cues, visible focus, reduced motion and forced colors are built in. Accessibility statement.
Every page states the smallest correct HTML, and site-manifest.json lists every component, tag, hook and docs URL. Agent contract.
Forma is the shared presentation layer for Echelon Foundry applications and marketing sites. Limen supplies behavior beyond native HTML, Ordo owns legal state transitions, Aegis supplies safe fault presentations, and Visual Engineering research informs the verification screens on every page. Brands and skins change identity without changing semantics.