Install & Connect CSS
Load the shared stylesheet and make Tailwind source detection explicit. Check one styled component before building the rest of the screen.
Your next page is taking shape...
Opening Your Next Page…
Loading the guide and preparing its examples for you to explore. The page will appear here automatically when it’s ready, so you can keep this view open without refreshing.
Made for Preact. Built to be yours.
Kamod UIThe Documentation
Kamod UI is a Preact UI library of components, complete blocks, and a shared design language. Explore working examples, understand the code, and shape an interface that feels like your product.
A practical home for TypeScript, Tailwind CSS and the Kamod stack. Start small. Learn each piece. Build with confidence.
Open Source Preact Native Yours to Adapt
Interactive preview
Try the controls, explore the code, or reset and start again. Theme changes stay in this preview.
Loading kitchen sink…
01Components
A good interface begins with a clear action. Use Button for the next step, Input for a value, and Dialog when a decision needs focus. Kamod gives these pieces a consistent foundation while Your Application Owns the Behavior.
Each component guide brings together Live Variants, Copyable Source and an API Reference. Try the interaction first, then inspect the props and adapt the example to your data.
The example beside this text keeps the save operation in the parent. When that operation becomes asynchronous, add pending and error feedback at the same boundary; the State Ownership Guide explains the pattern.
src/components/SaveAction.tsx
After Setting Up Your App, import a component and give it one useful job. Use type="submit" when the action submits a form.
Just a few familiar faces. Meet the whole collection
02A Shared Foundation
Give the first component a home before adding the next. Load Shared Styles and Semantic Tokens once, then let buttons, form fields and whole layouts speak the same visual language.
Use roles such as bg-background, text-foreground and border-border instead of repeating fixed colors. Pair a primary action’s background with text-primary-foreground, and let the theme supply the values.
Try a Different Palette Here. This page and its examples follow the selected preset and color scheme. The Appearance Controls Guide covers saved choices and system preferences.
03Complete Blocks
Move from individual controls to a complete screen. Start with an Application Shell, explore Sidebar Layouts, or build an entry point with Login and Signup Blocks. The detail pages connect each live preview to its Source Files, Setup Instructions and Integration Guidance.
Loading the application shell playground…
A responsive application frame with navigation, account controls and room for your feature.
Explore This BlockOpen navigation, resize the screen and follow the keyboard path. Choose a layout for its behavior as well as its appearance.
A block can include data, helpers and shared components. Use the file tree to understand the composition before copying it.
Replace example routes and content, wire your service boundaries, then follow the Block Setup Guide to verify the result.
04Forms & Feedback
Forms connect the interface to a real task. Start with A Label, a Value and a Clear Next Action. Native required and type="email" constraints are a useful first layer; useful errors and predictable submission complete the journey.
As rules grow, add a reusable schema. The Formisch Guide connects valibot schemas to field values, validation and submission while Kamod supplies the controls.
Keep Field Validation distinct from Service Feedback. Preserve entered values when a save fails and give people a way to try again. Learn more about Submission and Recovery.
Input + LabelTry an invalid address, correct it, then submit. The browser checks the field before the local success message appears.
05Practical References
The special guides explain decisions shared by every component and block. Read them when you reach that step, then return to your feature with a clearer model of Setup, Composition and Appearance.
Load the shared stylesheet and make Tailwind source detection explicit. Check one styled component before building the rest of the screen.
Pair backgrounds with foregrounds, refine your theme centrally, and keep the same interface readable in light and dark mode.
Choose a clear hierarchy of actions, consistent spacing and useful surfaces. Change the composition before adding one-off overrides.
cnCombine base styles, conditional state and consumer overrides. Learn how clsx and tailwind-merge work together in the utility.
Read the full file tree, copy supporting files, and replace example navigation and data with your application's own boundaries.
Carry the same tokens into sidebars, overlays and copied source. Check the finished screen rather than an isolated component.
06The Kamod Ecosystem
Keep the UI at the center and add the capabilities your feature needs. These companion projects cover Behavior, State, Language and Visual Communication. Each has its own source and documentation; you do not need to install the entire stack.
@kamod-ch/iconsTyped SVG components. Keep a consistent icon family and let color follow the surrounding interface.
Read the Guide@kamod-ch/hooksReusable behavior for Preact: state helpers, browser interactions and lifecycle work close to its owner.
Read the Guide@kamod-ch/signalsPersist small reactive values with explicit defaults and storage choices. Useful for preferences across visits.
Read the Guide@kamod-ch/stateTyped actions and reducers for shared domain state. Make transitions explicit as a feature grows.
Read the Guide@kamod-ch/i18nTyped messages and locale-aware formatting, with a Preact adapter for translated interfaces.
Read the Guide@kamod-ch/motionAnimation tools for Preact. Introduce movement where it clarifies an interaction and respect reduced-motion preferences.
Explore the Repository@kamod-ch/chartsData visualization for Preact. Explore the dedicated repository for chart APIs, examples and setup.
Explore the Repository@kamod-ch/preactpressDocumentation sites built with Preact—the publishing foundation behind the guide you are reading.
Explore the RepositoryFor the interface itself, @kamod-ch/ui and @kamod-ch/themes provide the core components and theme foundation. Before sharing state or persisting a value, read about Package Responsibilities and The Server and First Render. Find more projects in All Kamod Repositories.
Start with one responsibility and one clear owner. Keep temporary input close to its component, persist only the preferences that should survive a visit, and introduce shared state when multiple parts of your feature need it. The Getting Started package examples show these choices in small, working compositions. Before adding a dependency, check its Versions and Peer Dependencies, then verify the behavior in your own application—including keyboard use, light and dark themes, and the first server-rendered page.
07Your Next Step
You have the map: Components for the Interaction, Blocks for the Layout, Forms for the Task and Packages for the Supporting Behavior. Bring them together one decision at a time.
The Getting Started guide takes you from installing the foundation to your first working screen, then through integration and delivery. Keep it nearby while you build.