Side Navigation Wizard

Onboarding11: Side Navigation Wizard

Desktop-oriented wizard with a persistent vertical step list (icons, titles, and descriptions) next to a content panel, collapsing to a dot-based progress row on mobile. This is the most functionally complete wizard in the onboarding family: it exposes real onStepComplete and onFinish callback props and enforces which steps can be jumped to.

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/onboarding11?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

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

This installs the block to components/beste/block/onboarding11.tsx and the badge and button shadcn/ui primitives it depends on.

Quick start

The installed file exports onboarding11Demo alongside the block: the exact props behind the preview above. Spread it to get a working four-step wizard in one line.

import { Onboarding11, onboarding11Demo } from "@/components/beste/block/onboarding11";

export default function OnboardingPage() {
  return <Onboarding11 {...onboarding11Demo} />;
}

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

import { Onboarding11 } from "@/components/beste/block/onboarding11";
import { Input } from "@/components/ui/input";

export default function OnboardingPage() {
  return (
    <Onboarding11
      badge={{ label: "Setup", variant: "secondary" }}
      heading="Account Setup"
      steps={[
        {
          id: "1",
          title: "Profile",
          description: "Basic info",
          content: <Input type="text" placeholder="Your name" />,
        },
        {
          id: "2",
          title: "Workspace",
          description: "Team settings",
          content: <Input type="text" placeholder="My Team" />,
        },
      ]}
      labels={{ next: "Continue", back: "Back", finish: "Get Started" }}
      onStepComplete={(stepIndex, stepId) => console.log("completed step", stepIndex, stepId)}
      onFinish={() => console.log("wizard finished")}
    />
  );
}

Props

type NavStep = {
  id: string;
  title: string;
  description?: string;
  icon?: LucideIcon;
  content: React.ReactNode;
};

Behavior notes

• Navigation is genuinely stateful and wired to callbacks: handleNext calls onStepComplete(currentStep, stepId), adds the current index to a completedSteps Set, then either advances currentStep or calls onFinish() if it's the last step.
• Step navigation is constrained: clicking a step in the desktop side nav or the mobile dot row (handleStepClick) only works if that step is already completed or is at/behind the current step (index <= currentStep || completedSteps.has(index)), so users can't skip ahead to steps they haven't reached yet.
• initialStep only seeds the starting currentStep and pre-marks every index below it as completed in the initial completedSteps set; it is not re-synced if the prop changes after mount.
• Layout branches by breakpoint: below md, a dot-based progress row with a truncated current-step title and a "Step X of Y" readout replaces the full navigation; at md and above, a persistent side nav with icons, titles, and descriptions takes over. Both share the same handleStepClick logic.
• steps[].icon renders in the desktop side nav (overriding the numbered fallback for any step that isn't yet completed) but has no equivalent in the compact mobile dot row.
• If steps is empty the component returns null rather than rendering an empty shell.