Actions & Selection
Toggle
Toggle controls a binary pressed/unpressed state with modern Radix-style variants and sizes. Make the next action easy to recognize. Use visual emphasis deliberately and distinguish an action from a persistent selection or a navigation link. Import it from @/components/kamod-ui/toggle.
Source · Design reference · API reference · Theming · Styles
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthInstallation
Import Toggle from @/components/kamod-ui/toggle.
pnpm add @kamod-ch/uiCopy an example with @kamod-ch/ui or the matching @kamod-ch/ui/… subpath. The code block switches between those two installs. Connect The Global Theme CSS and Tailwind Source Detection before your first render.
Usage
Use variant, size, and controlled state props to match toolbar and settings use-cases.
import { Toggle } from "@kamod-ch/ui";Choose a complete composition from the examples below; required child components and props vary by pattern.
Component Examples & Variants
Explore Toggle in Different Contexts, from the starting pattern to the compositions below. Begin with Basic Toggle, then compare the examples that match your content, state and layout. These are working patterns to adapt, not a list of interchangeable variant values: check the API Reference before using a prop or combining behaviors. Look at the surrounding labels, supporting text and spacing as well as the component itself.
Read the Result and Its Implementation Together. Use each showcase’s Code view to inspect imports and composition, or its Prompt view to prepare a setup or adaptation brief. Try the narrow preview and local theme controls before connecting real data, and use Reset to return an example to its initial state. Keep layout changes in class utilities where appropriate; follow the Component Styles Guide for hierarchy and the Theming Guide for shared surfaces and colors. The Accessibility Notes explain what to preserve when making those changes.
Basic Toggle
Represent a Persistent on/off Choice. Use Toggle for a boolean pressed state, such as an active formatting option. An initial pressed value establishes the starting presentation, while subsequent changes should represent a persistent choice rather than a one-time command.
Keep its accessible name stable enough to understand the state and connect the pressed value to the actual feature; use an ordinary Button for actions without a retained selection.
import { Toggle } from "@kamod-ch/ui";
import { Bold } from "lucide-preact";
export const Example = () => (
<Toggle defaultPressed aria-label="Toggle bold">
<Bold class="size-4" />
</Toggle>
);Toolbar Actions
Keep Formatting Choices Independently Meaningful. Arrange related toggles in a formatting toolbar when each button represents an on/off option. If the choices need shared exclusive or multiple selection behavior, compare Toggle Group before assembling separate state handlers.
Give each icon a clear accessible name and keep pressed states synchronized with the edited content rather than only the last pointer interaction.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthVariants and Sizes
Match Visual Weight to the Toolbar. Choose the outline treatment when a toggle needs a more explicit boundary and an icon size when its symbol is sufficient visually. Give icon-only options accessible names that explain the setting they enable or disable.
Preserve a clear pressed state and visible keyboard focus in every combination, and avoid making the active treatment indistinguishable from a hover effect.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthProps and Data
Configure Toggle using the contracts below. Read the documented options alongside the Source Definitions to understand which values your application supplies and which details the component owns. Start with a prop or helper, then follow its type link to inspect the declaration without leaving the page.
Props, slots and variants for this component.
Type cards are extracted from this checkout’s TypeScript source at build time. Props inherited through HTMLAttributes, Omit or variant helpers remain references in those declarations; their fields are not flattened here. Match the reference to your installed version, and check a package’s exports before writing an import type. A type exported by a source file is not necessarily re-exported by @kamod-ch/ui.
Component Props
? means a field can be omitted; it does not promise a fallback value. Existing documented defaults remain alongside the descriptions. For callbacks, check the argument and return types before connecting your own state or services.Toggle
ToggleProps
| Prop / type | Description |
|---|---|
children | Configure
|
class | Configure
|
defaultPressed | Configure
|
disabled | Configure
|
name | Configure
|
onClick | Configure
|
onPressedChange | Configure
|
pressed | Configure
|
required | Configure
|
size | Configure
|
value | Configure
|
variant | Configure
|
Data Type Reference
Expand a card to inspect and copy the exact declaration. The code header identifies its repository file; follow imported or inherited types in the Implementation Source when you need the complete dependency chain. Required-field summaries cover fields declared directly in that type. Source-only helpers and inferred schema outputs describe the local implementation, not additional props you can pass to every component.
Toggle Props
6 declared fieldsTogglePropsToggle.tsx. Referenced types retain their original names; inspect that file for imports and supporting definitions. Inspect the Complete Definition of ToggleProps before adapting it.Accessibility
Toggle renders a button with aria-pressed reflecting its state. Pressed state represents a persistent choice, not just the brief visual feedback of clicking a normal action button.
You have the pieces. Put them into one real interaction, keep its state in one place, and check the result with the content your application will actually show.
Connect the Foundation
Return to Choose and Compose Components to connect this reference to a working screen. Keep global CSS in one entrypoint and import only the components that screen needs.
Build the Surrounding Screen
Find a neighboring interaction in the Component Library, or start with a complete Block. Replace sample content and destinations before refining the layout; a local class change can stay with the composition.
Make the Result Hold Up
Use shared theme roles for changes that belong everywhere. Then review the whole journey: keyboard focus, long labels, narrow screens and a clear way to recover when something fails.
Keep a link to the source and note your intentional changes. Your next edit should begin with a clear decision, not another search.