Typography and status

Render styled terminal copy, hierarchy, separators, labels, and compact status signals with semantic metadata.

Overview

Render styled terminal copy, hierarchy, separators, labels, and compact status signals with semantic metadata.

Installation

npx @mwillbanks/tuil add text heading divider badge

The CLI writes source-owned components beneath the destination configured in tuil.config.ts; the default import below assumes src/components/tuil.

Loading executable example…

Components and subcomponents

API	Signature	Description
`Text`	`function Text`	Public function Text.
`Heading`	`function Heading`	Public function Heading.
`Divider`	`function Divider`	Public function Divider.
`Badge`	`function Badge`	Public function Badge.

Interaction

Read-only presentation; accessibility lives in semantic role and label metadata.

API and events

No events are emitted.

Every interactive component publishes semantic roles, labels, state, and focus identity through the renderer's SemanticRegistry. Callback failures flow to the owning application's error boundary.

Documentation flow diagram. props and runtime state; semantic registration; focus and input routing; callback or state update; rerender; S0 leads to S1; S1 leads to S2; S2 leads to S3 — **Documentation flow diagram.** props and runtime state; semantic registration; focus and input routing; callback or state update; rerender; S0 leads to S1; S1 leads to S2; S2 leads to S3

Example

import type { ComponentProps } from "react";
import { Text } from "@/components/tuil/data-display/text";

export function Example(props: ComponentProps<typeof Text>) {
  return <Text {...props} />;
}

Registry-installed components are source-owned: customize the generated file in your application, and use the package reference for the shared runtime contracts.