Composition & Layout
Separator
Separator trennt Inhalte visuell oder semantisch in modernen Layouts. Build a clear hierarchy with reusable structure, consistent spacing and semantic surfaces. Keep layout decisions close to the content they organize. Import it from @/components/kamod-ui/separator.
Source · Design reference · API reference · Theming · Styles
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthInstallation
Import Separator from @/components/kamod-ui/separator.
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
Nutze horizontale Separatoren fuer gestapelte Bereiche und vertikale Separatoren fuer Inline-Gruppen oder Menues.
import { Separator } from "@kamod-ch/ui";Choose a complete composition from the examples below; required child components and props vary by pattern.
Component Examples & Variants
Explore Separator in Different Contexts, from the starting pattern to the compositions below. Begin with Horizontal Separator, 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.
Horizontal Separator
Separate Related Content without Adding Another Surface. Place a horizontal Separator between distinct blocks of related content. It creates a quiet visual boundary within the reading flow without requiring a separate card surface or additional heading for every division.
Keep it visually secondary and decide whether it conveys a meaningful structural boundary or is purely decorative before choosing its accessible treatment.
import { Separator } from "@kamod-ch/ui";
export const Example = () => (
<div class="w-full max-w-md space-y-2">
<h4 class="text-sm font-medium leading-none">Blog</h4>
<p class="text-sm text-muted-foreground">
Read product updates, release notes, and engineering deep-dives.
</p>
<Separator />
<h4 class="text-sm font-medium leading-none">Docs</h4>
<p class="text-sm text-muted-foreground">
Browse setup guides, API references, and usage examples.
</p>
</div>
);Vertical Separator
Give Inline Groups a Quiet Boundary. Set orientation="vertical" for a separator between compact inline groups. Give the surrounding row a meaningful height so the line can distinguish neighboring content without becoming an oversized decorative element.
Set a usable surrounding height, keep spacing balanced on both sides and let narrow layouts adapt instead of leaving an isolated divider on a wrapped line.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthList
Create a Consistent Rhythm in Dense Lists. Insert horizontal separators between compact list rows when full borders would add unnecessary visual weight. Keep the spacing consistent so each item remains a recognizable unit rather than appearing attached to the following row.
Align it with the content structure, preserve enough vertical space for wrapped text and avoid duplicating a border already supplied by the row component.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthProps and Data
Configure Separator 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.Separator
SeparatorProps
| Prop / type | Description |
|---|---|
class | Configure
|
decorative | Configure
|
orientation | 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.
Separator Props
2 declared fieldsSeparatorPropsSeparator.tsx. Referenced types retain their original names; inspect that file for imports and supporting definitions. Inspect the Complete Definition of SeparatorProps before adapting it.Accessibility
Separator defaults to a semantic separator role and exposes its orientation. Set decorative when the line only adds visual spacing; that removes the semantic role/orientation rather than announcing every ornamental rule.
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.