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.

Form Block

A login page with a muted background color. Connect the form's onSubmit callback to your authentication service, then adapt the fields, branding and account links. Your App Handles Authentication; the block provides the form interface. Try validation and submission feedback in the live demo, and review the source before integrating the form into your sign-in flow.


Interactive Live Preview
Try it. Make it yours.

Variant 3 of 5

Live Preview and Source

Open
Setting the scene...

Interactive preview

Add This Block

Copy this variant into your Preact project, install the dependencies you are missing and connect your own authentication service. The source stays local, so you can change its layout without introducing another application framework.

  1. Copy the Block

    Open the Showcase’s Code Tab and copy the files below relative to src/components/blocks. Keep the source folder structure so relative imports resolve. These are destination paths; the Code tab’s display labels such as app/login/page.tsx are not the installation paths. The examples below assume your importing file is src/App.tsx.

    Text ReferencePlain Text
    login/login-03/page.tsx
    login/login-03/login-form.tsx
    auth/shared/auth-utils.ts
    auth/shared/google-icon.tsx
    shared/branding/kamod-brand-link.tsx
    shared/branding/kamod-brand-sizes.ts
    shared/branding/kamod-logo.tsx
    shared/branding/kamod-logo-url.ts
    shared/branding/kamod-logo-horizontal.svg
    shared/branding/kamod-logo-horizontal-dark.svg
    Keep supporting files together

    Forms use shared validation and provider helpers. Branded and illustrated layouts also need their listed SVGs and URL helpers. Keep ?url imports in a Vite app, or adapt them to your bundler. If TypeScript cannot resolve an SVG import, include Vite’s client types (for example, import "vite/client" in an existing declaration file). Keep the repository’s license with your copied source.

  2. Install Missing Dependencies

    Install only what your app does not already have. Preact renders the block, Kamod UI provides its interactive components, and Icons supplies its icons. Themes and Signals support the shared Kamod setup.

    Install PackagesTerminal
    pnpm add @kamod-ch/ui @kamod-ch/icons preact @kamod-ch/themes @preact/signals
  3. Set Up Styles and Import

    Follow the Theme and Tailwind Setup. Import your global stylesheet and make sure Tailwind scans the copied source and Kamod components. Keep your existing setup if the app already uses Kamod.

    Import SetupTypeScript
    import { Login03 } from "./components/blocks/login/login-03/page";
    Import from your local source

    The @kamod-ch/blocks/login/login-03 path identifies source in this repository; the blocks package is private. Use the local import above rather than trying to install that path as a published package.

    Check the First Render

    The form controls, borders and page background should follow your app’s theme. If the layout appears unstyled, check the global CSS import and Tailwind source detection before changing the block’s classes. If an import fails, first compare your folder paths with the copy list; renaming only one file can break its relative imports.

Usage

Start by rendering the supplied page to check its appearance, then connect its local form to your application. Login03 takes No Props; callbacks belong to LoginForm inside the copied page. The form owns its input and feedback state, while your app owns the authenticated session and destination after success.

Render the Page or Form

Usage PatternTypeScript
import { Login03 } from "./components/blocks/login/login-03/page";

export const App = () => <Login03 />;

This renders a complete page with its own main landmark. To preserve this variant’s layout, edit the LoginForm call in your copied page.tsx. To embed the form in an existing page or dialog, import the form directly instead of nesting another full page. Its heading is an h1; adjust that level and the field IDs if your host page already has a heading or another instance of this form.

Connect Your Authentication Service

The example below wraps the form in a component that receives your service functions. Pass the same callbacks to the form in page.tsx if you keep the original layout. The imported value types describe the submitted payload; they are not configuration props on Login03. See Form Props for each callback and link destination.

Usage PatternTypeScript
import { LoginForm } from "./components/blocks/login/login-03/login-form";
import type { LoginValues, AuthProvider } from "./components/blocks/auth/shared/auth-utils";

type Props = {
  submit: (values: LoginValues) => Promise<void>;
  startProvider: (provider: AuthProvider) => Promise<void>;
};

// These functions come from your application's authentication service.
export const AccountForm = ({ submit, startProvider }: Props) => (
  <LoginForm
    onSubmit={submit}
    onSocialLogin={startProvider}
    signupHref="/signup"
    forgotPasswordHref="/forgot-password"
  />
);
Report the actual result
Return the request’s promise so loading lasts until it settles. If your service resolves with an error result rather than rejecting, handle that result explicitly; the form otherwise treats completion as success. Map useful messages to the local error/status state in login-form.tsx. A callback’s return value does not automatically populate field errors or navigate to another page.
Replace the demo before connecting users
Remove sleep(), demoRejects() and the simulated success/error messages. Without a callback, the demo can still report success. Supply real account links and implement your success destination; the block does not create a session or redirect on its own.

Check the Complete Flow

  • Invalid and Valid Submissions. Check the first invalid field receives focus, correct its input, then verify a successful request and a rejected request. Local field errors are recomputed on submission, not cleared as each character is typed.
  • Pending Requests. Buttons disable while loading, but inputs remain editable. Decide whether your app should freeze those fields and prevent repeated submit events; a disabled button alone is not a complete request guard. Handle cancellation if the form can unmount while a request is pending.
  • Alternative Paths. Test every visible provider button and account link. Provider sign-in runs independently of the credential fields; a failed email form should not be mistaken for a failed provider request.
Finish the integration

The Variant Details explain this form’s payload and provider behavior. Finish with the Accessibility Checks using your real labels, errors and service responses.

Props and Data

Login03 is a ready-made demonstration page with no public props. The reference below describes the Local Form you can configure after copying the source. Definitions come directly from the implementation; descriptions explain where your application takes over. Start with the component or data shape you want to change, then follow its type link to the complete definition.

API reference
Your API, from source

The signatures below come from the copied source files. Use the Data Type Reference to inspect complete definitions and required fields. Optional callbacks do not imply that a backend is included. Select a table row’s type name to open its definition automatically. Use import type from the corresponding copied file when typing your own data or component inputs. This reference describes the shipped source; changes in your local files will not update this page.

Form Props

Each field includes its type and integration behavior. The asterisk
marks required fields. Omitted optional fields use the defaults described below. The definitions retain the actual source’s optional markers and callback return types. Read each field together with its owning type: the same name can have a different purpose on another helper. A ? means the field may be omitted, not that every optional field has a fallback value. When a field accepts an array, its required marker means you must supply the array; check the helper’s behavior before using an empty [].
Local helper props and data fields
Prop / typeDescription
onSubmit
(values: LoginValues) => void | Promise<void>LoginFormProps
Receives the validated email and password when the user submits the local login form. Return a promise for the form to await your sign-in request; a thrown error or rejection enters its error state. The copied demo still waits and rejects emails containing error before calling your handler, and it can show success without a handler. Replace those demo checks and messages, then handle session creation and navigation in your application.
onSocialLogin
(provider: AuthProvider) => void | Promise<void>LoginFormProps
Called with github or google when the corresponding provider button is pressed, independently of email/password validation. The form awaits a returned promise and displays a demo success or error message; omitting the callback does not hide the buttons. Connect your provider redirect or sign-in flow and replace the simulated delay/status copy. Although AuthProvider also includes gitlab, the current form has no GitLab button.
forgotPasswordHref
stringLoginFormProps
URL for the Forgot your password? link beside the password field; defaults to #. Point it to your recovery page, where your app can request and complete a password reset. This prop only changes the link destination; it does not send an email, validate the recovery request or open a recovery dialog. Replace the anchor in the copied form if your router requires its own link component.
signupHref
stringLoginFormProps
URL for the Sign up link below the login form; defaults to #. Supply your registration route so users can move from sign-in to account creation. Changing this value does not carry over entered credentials or configure a signup service. For client-side routing, adapt the rendered anchor to your app’s navigation conventions.
email
stringLoginValues
Email string passed to your submit callback after the form’s simple local format check. The copied form forwards the entered value without normalizing it; decide how your service handles surrounding whitespace and address casing. Passing the local check neither verifies ownership nor proves that an account exists. The demo also treats addresses containing error as a simulated failure before invoking onSubmit.
password
stringLoginValues
Password string entered in the form and forwarded to onSubmit after the local minimum-length check of eight characters. The field does not trim or hash the value, and the demo’s validation is not an authentication service. Apply your application’s actual credential rules and submit through the appropriate service; avoid placing this value in logs or URLs. It is never included in the email-only MagicLinkValues payload.

Data Type Reference

Expand a definition to copy its exact TypeScript shape. Required fields are listed below each summary for fields declared in that definition. The code header shows the file's installation path; copy the definition with the button beside it. For intersections, also inspect the referenced base type’s required fields. Local types can be imported from the same files as your copied components; they are not added to the zero-prop page wrapper.

Complete Form Signature

4 declared fields
LoginFormProps
The local form accepts optional callbacks and destination links. The exported page wrapper takes no props and does not forward these callbacks. Inspect the Complete Definition of LoginFormProps before adapting it.

Submission Values

2 declared fields
LoginValues
Passed to onSubmit after local validation. Your service remains responsible for completing the authentication flow. Inspect the Complete Definition of LoginValues before adapting it.
Required fields
email, password

Social Provider

Declaration
AuthProvider
The shared union includes gitlab, but the current forms render only GitHub and Google buttons. Adding another provider requires adding its UI and handler. Inspect the Complete Definition of AuthProvider before adapting it.

Sign-in and Provider Callbacks

The form validates an email and a password before awaiting onSubmit. GitHub and Google buttons call onSocialLogin independently. Your authentication service handles the session, provider redirect and post-login destination.

Callbacks are awaited
Return a promise from your callback so the form waits for completion. A rejection enters its error state; replace the generic demo error with appropriate application feedback. Do not log submitted passwords.
Social providers need a service
Connect onSocialLogin to your provider flow. Showing a provider button alone does not configure OAuth or create a session.
Usage PatternTypeScript
<LoginForm
  onSocialLogin={startProviderLogin}
  onSubmit={signIn}
/>
Connect your service

The callback names above represent functions supplied by your app. Keep server-side validation and credential handling in your authentication service. Adapt the form’s demo messages to that service’s actual result.

About This Block

The page provides the setting; the form owns the interaction. This composition combines Input, Label, Button and Alert into a complete sign-in interface. Your application supplies the authentication service and real destinations; a successful preview interaction does not create a session.

Composition and Customization

Edit page.tsx for centering, surfaces, branding and any cover image. Edit login-form.tsx for fields and submission. The full-page wrapper takes no configuration props; pass callbacks to LoginForm inside that page. See Render the Page or Form for both entry points.

Shared auth/shared helpers supply validation and provider artwork; optional branding lives in shared/branding. Keep imported helpers when reusing the form elsewhere. Its values are local component state: there is no public value or initialValues prop. To add a field or prefill values, update state, validation and the payload type together.

Wait for the actual sign-in result. The LoginValues payload contains email and password. Return your service promise so pending feedback lasts until the operation completes.

This line in the Submission Handler is the handoff to your application, after local validation:

Usage PatternTypeScript
await onSubmit?.(values);

The optional callback means the demo can show success without a connected service. A rejected promise enters the form’s error state; a resolved error object does not do so automatically. Follow Connect Your Authentication Service to map your service’s result and replace the demo messages.

Responsive Behavior

A centered card sits on a muted page background with a brand link above. Its maximum width keeps fields readable, while outer padding reduces on smaller screens. Use the Card surface for grouping, and keep essential instructions inside the form.

Let the page grow when feedback appears. The full-page wrappers use min-h-svh, not a fixed content height. Keep labels, legal links and errors able to wrap, and test with the on-screen keyboard open. When embedding the form in a Dialog, preserve its scroll area and keep the submit button reachable.

Pair bg-background with text-foreground and card surfaces with their matching foreground token. The block theming guide explains how to keep fields, errors and loading states legible in both modes. Review replacement images at each breakpoint; decorative art should not carry instructions or duplicate the form’s text alternative.

Accessibility

Preserve the field’s complete identity
Keep the Label associated with its control’s id, retain aria-invalid and link help/errors through aria-describedby. A placeholder is secondary guidance, not a label. If you render two instances, give labels, inputs and messages distinct ID prefixes.
Make failure recoverable
Local validation calls focusFirstError before sending data. Include new inputs in that logic and keep messages beside the field they explain. Server failures need a clear retry path without exposing sensitive account details; review the input accessibility guidance when extending feedback.
Keep pending and completion states connected
loading disables submission controls, while role="status" and aria-live="polite" announce messages. Preserve these cues when changing button copy. If the next step navigates away, your application should also manage focus in the destination page.
Check the full flow

Invalid input → correction → pending request → success or a recoverable failure. Repeat at 320px, 768px, 1024px and 1440px, with keyboard-only input, 200% zoom and both color modes. Use Check the Complete Flow for the integration checklist.

Replace the Demo Behavior

Replace simulation before connecting real users. Remove sleep()and demoRejects(), rewrite the success/error messages and provide real account and legal URLs. Check Form Props for the destinations this variant exposes. Branded layouts also need a real home destination on KamodBrandLink, whose fallback is #.

Connect onSocialLogin separately from onSubmit. Provider buttons start their own flow; displaying GitHub or Google does not configure an OAuth service. The variant behavior notes explain these callback boundaries.

Keep server validation, sessions and recovery in your application’s service layer. Reuse the form’s visual structure while adapting its messages and next steps to your actual product. Finish with the whole-journey review, including a slow request and a failed one.

Source and Customization

Use the Checked-in Kamod Implementation as your reference when adapting this variant. The Showcase’s Code Tab includes its supporting files, and the Setup Instructions explain where to place them and how to keep their imports intact. Before changing a helper, trace where it is used in the composition and check its inputs in the Props and Data Reference. This helps you adapt one part of the block without overlooking the files or behavior it depends on.

Keep your local copy focused on the layout and interactions your app actually uses. Start with the data and content, then adjust composition and styling using the same semantic theme tokens.

Ready to integrate? Follow Add This Block and the Local Usage Example.

Design Reference

This variant follows the corresponding login design in the shadcn/ui collection. Use the reference to compare the contrast between a compact sign-in surface and a muted surrounding page, with branding above. Adapt the branding, copy and destinations to your product, then follow the Usage Example to connect the form’s callbacks to your authentication service.

This version uses Kamod’s Preact form components and theme tokens. Kamod places the form in an explicit core Card and uses semantic theme colors. Treat the reference as guidance for spacing and hierarchy, not a requirement to reproduce every field or provider option.

Inspect the Original Variant’s Source for the reference composition. The Variant Details above describe this implementation’s behavior and integration boundaries.

Use the original as a design reference. To install the Preact version shown here, follow Add This Block and use this page’s Code tab. Its files and imports are prepared for Kamod.

Take the Next Useful Step

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 Bring a Complete Layout into Your App 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.