# Contact Section (Lumen Halo): prompt.md (v1.0.0)

- id: `lumen-contact-section` · version 1.0.0 · block · pro (Pro)
- category: Marketing
- build: Base UI (one set of files; its dependencies follow the build)
- install (this build): `npx shadcn@latest add @beautiful-ui-pro/lumen-contact-section`
- npm dependencies: none
- registry dependencies: utils, @beautiful-ui/lumen-button, @beautiful-ui/lumen-field, @beautiful-ui/lumen-input, @beautiful-ui/lumen-textarea, https://beautiful-ui.dev/r/lumen-foundation.json
- docs: https://beautiful-ui.dev/components/lumen-contact-section
- The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand.

A short contact form beside the other ways to reach you. Fields check themselves when you leave them and again on send; once sent, the form turns into a confirmation in place with the address you'll reply to and a way to send another.

## Build it
- Stack: React 19 (`ref` is a plain prop), TypeScript, Tailwind CSS v4 utilities, a shadcn-initialised project with the `@/*` alias.
- Packages: none beyond React.
- Files: `components/ui/lumen/blocks/contact-section.tsx`.
- Registry dependencies, installed with it automatically: shadcn `utils` (cn), `lumen-button`, `lumen-field`, `lumen-input`, `lumen-textarea`, `lumen-foundation`.
- Builds: one set of files for both, but its dependencies come in Base UI and Radix builds. Install the one that matches the project (see Install): a free item's bare URL installs the Base UI build of it and its dependencies.
- Exports to keep: `ContactSection`, and every exported type.
- CSS: the install merges this item's rules (the registry `css` field) into your global stylesheet, in `@layer components`, and adds the lumen foundation (tokens, keyframes, motion levels) once. Nothing to import by hand.
- Re-running `add` (or `--overwrite`) re-applies those rules: put overrides in your own CSS, never in the installed rules.
- Tokens: retheme with the `--lumen-*` custom properties (`--lumen-accent`, `--lumen-accent-foreground`, `--lumen-accent-text`, `--lumen-bad`, `--lumen-bad-text`, `--lumen-chart-accent`, `--lumen-chart-accent-foreground`, `--lumen-chart-accent-text`, `--lumen-focus`, `--lumen-good`, `--lumen-good-text`, `--lumen-hairline`, `--lumen-ink`, `--lumen-muted-ink`, `--lumen-series-1`, `--lumen-series-2`, `--lumen-series-3`, `--lumen-series-4`, `--lumen-series-5`, `--lumen-series-6`, `--lumen-warn`, `--lumen-warn-text`); this item's CSS also reads `--lumen-font-mono`, `--lumen-font-sans`, `--lumen-radius-k`. Never add Tailwind colour classes inside the component.

```tsx
import { ContactSection } from "@/components/ui/lumen/blocks/contact-section";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `ContactSection` | `contact-section` | The intro, channels and the form (then the confirmation). |

Style a part with `[data-slot="<slot>"]` selectors or its `className`; keep the attributes when editing.

## Sound
- Keep every `data-slot` and `data-sound` attribute: the sound layer reads them.
- Installing this item adds no audio. Nothing plays until the app mounts `GlassSoundProvider` once (install: `npx shadcn@latest add https://beautiful-ui.dev/r/glass-sound.json`, import from `@/components/beautiful-ui/glass-sound`); `GlassSoundToggle` is its mute control. Without a provider the audio engine never loads.

## Match the original
- Read `components/ui/lumen/blocks/contact-section.tsx` as the reference implementation before changing or recreating anything, and match it: sizes, colours per theme, motion timings, copy and behaviour.
- If you deviate (a prop you can't honour, a style you changed, a dependency you swapped), say so in your reply, part by part.
- Keep the accessibility contract, the keyboard map and the motion levels listed below.

## Use it when
- contact form, contact us, contact sales, get in touch, support form, demo request
- A Contact or Talk to sales page
- A support request form inside an app

### Not when
- Sign-up or sign-in: use Auth
- A one-field email capture: use a newsletter or waitlist form

## Mistakes
- Validate again on the server; the form's checks are for people, not security
- Add your own spam protection (a challenge or a honeypot) in onSubmit's endpoint

## Usage

```tsx
"use client";
import { ContactSection } from "@/components/ui/lumen/blocks/contact-section";

export function ContactPage() {
  return (
    <ContactSection
      channels={[
        { id: "email", label: "Email", detail: "hello@example.com", href: "mailto:hello@example.com" },
        { id: "hours", label: "Support hours", detail: "Mon–Fri, 9:00–18:00 CET" },
      ]}
      onSubmit={async (input) => {
        const res = await fetch("/api/contact", { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify(input) });
        if (!res.ok) throw new Error("Couldn't send it. Try again, or email us directly.");
      }}
    />
  );
}
```

## Props

| Prop | Type | Default | What it does |
|---|---|---|---|
| `onSubmit` | `({ name, email, topic, message }) => Promise<void>` |  | Send it (your API, a form service). Throw to show the error above the button. |
| `topics` | `string[]` | `["Sales", "Support", "Partnerships", "Something else"]` | The choices for What's it about? |
| `channels` | `{ id, label, detail, href? }[]` |  | Other ways to reach you, listed beside the form (an email address, a phone number, office hours). |
| `labels` | `Partial<ContactLabels>` |  | Every word, for i18n: the titles, fields, errors and the confirmation sentBody(email). |

Full docs: https://beautiful-ui.dev/components/lumen-contact-section

## Customising
- Colours: set the `--lumen-*` tokens on `:root`, or on a container with the `lumen-scope` class to retheme one area. Add the `lumen-inherit` class to follow your shadcn palette instead (`--chart-N`, `--destructive`).
- Dark mode follows the `.dark` class on an ancestor (the shadcn and next-themes convention).
- Update later by re-running the install with `--overwrite` (review the diff if you edited it). Changelog: https://beautiful-ui.dev/r/changelog.json

## Keyboard

| Keys | Action |
|---|---|
| Tab | Through the fields, the topics and Send |
| ← / → | Change the topic |
| Enter | Send |

## Performance

- A plain form; nothing runs until you type

## Responsive

- Words and channels sit beside the form and move above it under 720px; the name and email fields stack under 460px

## Motion inventory

| Interaction | What moves |
|---|---|
| Sent | The form gives way to the confirmation, whose check draws itself |

## Accessibility contract (preserve when editing)
- Every field has a visible label; errors appear after you leave a field (not while typing), are tied to it with aria-describedby and aria-invalid, and send moves focus to the first problem
- Topics are a real radio group in a fieldset with a legend
- The confirmation is a status region and takes focus, so screen readers hear it
- A failed send is announced (role alert)

## Install

```bash
npx shadcn@latest add @beautiful-ui-pro/lumen-contact-section
```

Pro item: needs the `@beautiful-ui-pro` registry in `components.json` and `BEAUTIFUL_UI_TOKEN` in `.env.local` (https://beautiful-ui.dev/account). Setup: https://beautiful-ui.dev/docs/pro. Your components.json `style` picks the build: radix-*, new-york and default get Radix, base-* gets Base UI.

The lumen foundation (the tokens listed above, keyframes and motion levels) installs once with the first component; its CSS is public at https://beautiful-ui.dev/r/lumen-foundation.json.