Plain Contact

Booking32: Plain Contact

A plain contact section: a heading that settles in word by word over a ruled list of contact lines, beside a name, email and message form that ends on a pill and a one-line privacy note.

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

Radix flavor

npx shadcn add "https://ui.beste.co/r/booking32?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

npx shadcn add "https://ui.beste.co/r-base/booking32?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/booking32.tsx, the shadcn input, label, and textarea primitives the form is built on, and the button22 sliding-marker pill and the text1 word stagger it uses.

Quick start

The installed file exports booking32Demo alongside the block: the exact props behind the preview above. Spread it to get a working contact form in one line.

import { Booking32, booking32Demo } from "@/components/beste/block/booking32";

export default function Page() {
  return <Booking32 {...booking32Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

import { Booking32 } from "@/components/beste/block/booking32";

export default function Page() {
  return (
    <Booking32
      eyebrow="Get in touch"
      heading="Write as much or as little as you like."
      description="Every message is read by a practitioner, not a form robot."
      contacts={[
        { label: "Email", value: "hello@beste.co", href: "mailto:hello@beste.co" },
        { label: "Phone", value: "+351 21 000 0000" },
      ]}
      form={{
        name: "Your name",
        email: "Email",
        message: "What would you like to say?",
        button: "Send the message",
        note: "We never share your details with anyone.",
      }}
    />
  );
}

Props

type ContactLine = {
  label: string;
  value: string;
  href?: string;
};

type Booking32Form = {
  name: string;
  email: string;
  message: string;
  button: string;
  note: string;
};

Behavior notes

• href on a contact line is what makes it clickable, so an email or a phone number can carry mailto: or tel: while an address stays plain text in the same list.
• Those links are plain a elements rather than the router Link, which is correct for mailto: and tel: targets that should never be handled by client-side navigation.
• Contact lines are a dl on a three-column grid with the value spanning two, so a long address wraps under itself instead of pushing its label out of line.
• Field ids come from useId, so two of these on one page keep each Label pointing at its own input.
• Name and email share a two-column row from sm, while the message keeps the full width, which is the shape a message form wants: short answers side by side, the long one on its own.
• Dropping form leaves a usable contact section on its own, with just the heading and the ruled lines.
• The form only calls preventDefault() on submit; no state is collected and nothing is sent until you wire it up.