Onboarding screen with a grid of selectable interest tags and chips for personalizing content recommendations. Perfect for content platforms, newsletters, and social apps.
Onboarding screen that groups selectable interest tags under category headings and tracks how many are picked against a configurable minimum, unlocking the primary CTA only once that minimum is met.
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/onboarding16?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/onboarding16?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/onboarding16.tsx and the badge and button shadcn/ui primitives it depends on.
The installed file exports onboarding16Demo alongside the block: the exact props behind the preview above. Spread it to get a working interest picker in one line.
import { Onboarding16, onboarding16Demo } from "@/components/beste/block/onboarding16";
export default function OnboardingPage() {
return <Onboarding16 {...onboarding16Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Onboarding16 } from "@/components/beste/block/onboarding16";
export default function OnboardingPage() {
return (
<Onboarding16
badge={{ label: "Interests", variant: "secondary" }}
heading="What topics interest you?"
description="Pick at least 2 topics so we can personalize your feed."
minSelection={2}
groups={[
{
title: "Technology",
topics: [
{ id: "ai", label: "AI & Machine Learning" },
{ id: "web", label: "Web Development" },
],
},
{
title: "Design",
topics: [
{ id: "ux", label: "UX Design" },
{ id: "branding", label: "Branding" },
],
},
]}
primaryButton={{ label: "Continue", href: "/onboarding/step-3" }}
secondaryButton={{ label: "Skip for now", href: "/dashboard" }}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
badge | { label: string; variant?: "default" | "secondary" | "outline" } | – | Small badge above the heading |
heading | string | – | Main headline |
description | string | – | Supporting copy below the heading |
groups | TopicGroup[] | [] | Categorized groups of selectable topics |
minSelection | number | 3 | Minimum topics required before the primary CTA unlocks |
primaryButton | { label: string; href: string } | – | Primary CTA, disabled until minSelection is met |
secondaryButton | { label: string; href: string } | – | Secondary CTA link |
labels | { stepOf?: string; selectionHint?: string } | – | Template strings for the step counter and selection-count hint |
currentStep | number | 1 | Current step number, used only to fill the step-of label |
totalSteps | number | 4 | Total step count, used only to fill the step-of label |
className | string | – | Extra classes for the outer <section> |
type Topic = { id: string; label: string };
type TopicGroup = { title: string; topics: Topic[] };useState<Set<string>> always starts empty regardless of props, so nothing is pre-selected even if a topic conceptually should look "already chosen"; clicking a chip toggles its id in and out of that set.primaryButton renders as a real <Button disabled> while selected.size < minSelection; once the threshold is met it becomes clickable, but it navigates with a manual window.location.href = primaryButton.href inside onClick, not through asChild/Link the way secondaryButton does.text-primary the moment hasEnough becomes true, giving a visual confirmation independent of the button's own disabled styling.minSelection only gates the primary button and colors the hint text; there is no per-group minimum, the count is a flat sum across every group's topics combined.onboarding20
Onboarding screen with a grid of starter templates to choose from, each with a preview thumbnail, title, and description. Perfect for project creation flows in design tools and project management apps.
onboarding25
Onboarding screen for choosing theme mode (light, dark, system) and accent color. Perfect for apps that offer visual customization as part of the onboarding experience.
onboarding27
Onboarding screen with a quick survey asking how the user discovered the product, with selectable options and an optional text input. Perfect for marketing attribution during signup.
onboarding13
Onboarding screen where users select their role or persona to personalize their experience. Each role card shows an icon, title, and description with a selectable highlight state.
onboarding17
Onboarding screen where users pick their primary goal to receive a tailored onboarding path. Each goal card shows a recommended feature set. Perfect for multi-purpose platforms.
onboarding29
Onboarding screen for collecting company information including name, team size selector chips, and industry dropdown. Perfect for B2B SaaS apps that need organizational context during setup.