Assembly 2026
Talks, workshops, and the hallway conversations that stick with you. Get on the list for early-bird tickets before they open to everyone.
Speakers announced soon
An event coming-soon section with a square eyebrow, an event name and heading, a date and venue meta row with icons, a working ticket-alert email form, and a speaker avatar row.
A Polaris centered event coming-soon section with a square eyebrow, an event name and heading, a date-and-venue meta row with icons, a working ticket-alert email form that swaps to a success state, and a speaker avatar row.
Upgrade to Pro
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
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/comingsoon57?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/comingsoon57?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/comingsoon57.tsx.
The installed file exports comingsoon57Demo alongside the block: the exact props behind the preview above. Spread it to get a working ticket-alert page in one line.
import { ComingSoon57, comingsoon57Demo } from "@/components/beste/block/comingsoon57";
export default function Page() {
return <ComingSoon57 {...comingsoon57Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { ComingSoon57 } from "@/components/beste/block/comingsoon57";
export default function Page() {
return (
<ComingSoon57
brand="Assembly 2026"
label="Tickets soon"
heading="Two days for the people building what's next."
description="Talks, workshops, and the hallway conversations that stick with you. Get on the list for early-bird tickets."
speakers={[
{ src: "/people/ava.jpg", alt: "Speaker" },
{ src: "/people/theo.jpg", alt: "Speaker" },
{ src: "/people/priya.jpg", alt: "Speaker" },
]}
labels={{
dateValue: "May 14 to 15, 2026",
venue: "Barbican, London",
speakersCaption: "Speakers announced soon",
placeholder: "Enter your email",
success: "You're in. We'll email you the second tickets go live.",
}}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
brand | string | – | Event name rendered under the eyebrow |
label | string | – | Square eyebrow rendered via Badge6 |
labels | ComingSoon57Labels | {} | Date, venue, speakers caption, and form placeholder and success strings |
heading | string | – | Event heading |
description | string | – | Supporting paragraph under the meta row |
speakers | AvatarItem[] | [] | Overlapping speaker avatar stack shown below the form |
className | string | – | Extra classes for the outer <section> |
type AvatarItem = {
src: string;
alt: string;
};
type ComingSoon57Labels = {
dateValue?: string;
venue?: string;
speakersCaption?: string;
placeholder?: string;
success?: string;
};handleSubmit calls preventDefault and only flips when the trimmed email is non-empty, so there is no external callback to wire.labels.dateValue or labels.venue is set, with a Calendar icon beside the date and a MapPin icon beside the venue.max-w-3xl column, and the eyebrow, event name, heading, and description each render only when their prop is present.speakers is non-empty, as a -space-x-3 overlapping stack of plain <img> avatars over a top border, with labels.speakersCaption below when set.Wiring the form up
The form ships with local state and a success message but no backend, so submissions are not sent anywhere until you connect one. Point handleSubmit at your own route handler or email platform, or wire in a form library. For a walkthrough of the options, see React Hook Form, TanStack Form, and Formisch.