Onboarding screen with a form card for setting up user profile including avatar, display name, bio, and timezone. Perfect for the personal details step in any SaaS onboarding flow.
Onboarding screen with a form-shaped card for avatar, display name, bio, and timezone. The avatar control and text inputs are visual placeholders rather than a wired-up form: nothing typed or selected is captured in component state.
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/onboarding19?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/onboarding19?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/onboarding19.tsx and the badge, button, input, and select shadcn/ui primitives it depends on.
The installed file exports onboarding19Demo alongside the block: the exact props behind the preview above. Spread it to get a working profile setup step in one line.
import { Onboarding19, onboarding19Demo } from "@/components/beste/block/onboarding19";
export default function OnboardingPage() {
return <Onboarding19 {...onboarding19Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Onboarding19 } from "@/components/beste/block/onboarding19";
export default function OnboardingPage() {
return (
<Onboarding19
badge={{ label: "Profile", variant: "secondary" }}
heading="Set up your profile"
description="Tell us a little about yourself."
timezones={[
{ value: "utc-5", label: "Eastern Time (UTC-5)" },
{ value: "utc+0", label: "London (UTC+0)" },
{ value: "utc+3", label: "Istanbul (UTC+3)" },
{ value: "utc+9", label: "Tokyo (UTC+9)" },
]}
primaryButton={{ label: "Save & 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 |
timezones | TimezoneOption[] | [] | Options listed in the timezone select |
primaryButton | { label: string; href: string } | – | Primary CTA link |
secondaryButton | { label: string; href: string } | – | Secondary CTA link |
labels | { stepOf?: string; avatar?: string; avatarHint?: string; displayName?: string; displayNamePlaceholder?: string; bio?: string; bioPlaceholder?: string; timezone?: string; timezonePlaceholder?: string } | – | Field labels, placeholders, and the step counter template |
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 TimezoneOption = { value: string; label: string };<button> that only flips a local hasAvatar boolean between a Camera icon and a User icon; there is no file input, no image upload, and no preview of an actual picture.Input fields for display name and bio are uncontrolled with only a placeholder, no value/onChange, so anything the user types is never read back into component state.Select is likewise uncontrolled (no value/onValueChange); it only renders timezones as options, nothing chosen there is captured either.primaryButton ("Save & Continue" in the demo) and secondaryButton are always-enabled plain links; there is no client-side validation and no onSubmit/onSave callback, so this block is a static visual shell for a profile step rather than a working form.labels.avatar is declared in the props type but never rendered; only labels.avatarHint ("Click to upload") appears under the avatar control.Wiring the form up
This block ships the form markup only; state, validation, and submit are yours to add. Our guide wires the shadcn Field primitives to React Hook Form, TanStack Form, and Formisch on one field system.
onboarding23
Onboarding screen for configuring account security including two-factor authentication, recovery email, and backup codes. Perfect for apps that prioritize security during onboarding.
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.
onboarding14
Combined onboarding card for creating a workspace with name and URL slug, plus a team invite section with email inputs. Perfect for SaaS apps that require team collaboration setup.
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.
onboarding22
Onboarding screen showing current plan details with visual usage bars for storage, seats, and API calls. Perfect for SaaS post-signup flows that introduce plan limits and upgrade paths.
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.