Accordion Steps with Expandable Actions

Setup Guide

Complete your setup

Expand each step to learn more and complete the action.

1 of 4 completed

Start by adding your name, profile picture, and a short bio. This helps others recognize you and understand your role.

About this block

Accordion Steps with Expandable ActionsPRO

Interactive accordion layout where each step expands to reveal detailed instructions and action buttons. Perfect for setup guides that let users complete tasks at their own pace.

Onboarding10: Accordion Steps with Expandable Actions

Accordion-style setup guide: each step is a collapsible panel with its own indicator, title, description, and caller-supplied action content, with the first step expanded by default. Completion status and expand/collapse state are two entirely separate mechanisms.

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.

Upgrade Now

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

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

Base UI flavor

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

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

Quick start

The installed file exports onboarding10Demo alongside the block: the exact props behind the preview above. Spread it to get a working accordion guide in one line.

tsx
import { Onboarding10, onboarding10Demo } from "@/components/beste/block/onboarding10";

export default function OnboardingPage() {
  return <Onboarding10 {...onboarding10Demo} />;
}

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

tsx
import { Onboarding10 } from "@/components/beste/block/onboarding10";
import { Button } from "@/components/ui/button";

export default function OnboardingPage() {
  return (
    <Onboarding10
      badge={{ label: "Setup Guide", variant: "secondary" }}
      heading="Complete your setup"
      description="Expand each step to learn more and complete the action."
      steps={[
        {
          id: "1",
          title: "Create your profile",
          description: "Add your personal information",
          content: <Button size="sm">Edit Profile</Button>,
        },
        {
          id: "2",
          title: "Connect your calendar",
          description: "Sync your schedule",
          content: <Button size="sm">Connect Calendar</Button>,
        },
      ]}
      completedSteps={["1"]}
      primaryButton={{ label: "Continue to Dashboard", href: "/dashboard" }}
    />
  );
}

Props

PropTypeDefaultDescription
badge{ label: string; variant?: "default" | "secondary" | "outline" }Small badge above the heading
headingstringMain headline
descriptionstringSupporting copy below the heading
stepsAccordionStep[][]Ordered accordion panels
completedStepsstring[][]Ids of steps to mark as completed
primaryButton{ label: string; href: string }CTA below the accordion
classNamestringExtra classes for the outer <section>
ts
type AccordionStep = {
  id: string;
  title: string;
  description?: string;
  content: React.ReactNode;
};

Behavior notes

  • Only one piece of interactive state exists: openSteps, initialized to [steps[0]?.id ?? ""] so the first step starts expanded. Toggling a step (toggleStep) purely opens or closes its panel; nothing about "completed" status is touched by this interaction.
  • completedSteps is a plain array of step ids supplied via props; there is no click handler that adds an id to it, so marking a step done requires the parent to update the prop, for example after the user finishes whatever action button lives inside that step's content.
  • The "X of Y completed" count in the header is derived directly from completedSteps.length versus steps.length, independent of which panels are currently expanded.
  • Each step's action button (e.g. "Edit Profile", "Connect Calendar") lives inside the caller-supplied content node and is purely decorative in the shipped demo; there's no prop wiring those buttons back into the component's own state.
  • primaryButton renders as a plain <a> tag wrapped in Button asChild, unlike the next/link Link used for CTAs in most other blocks in this family.
  • If steps is empty the component returns null rather than rendering an empty shell.

More Onboarding blocks

View all Onboarding
PRO

onboarding6

Vertical Timeline Steps

Vertical timeline layout with step indicators, descriptions, and a connecting progress line. Perfect for workspace setup flows with detailed step explanations.

PRO

onboarding8

Multi-Step Form Wizard

Interactive form wizard with segmented progress bar, form fields, and back/next navigation. Perfect for account registration flows collecting user and company information.

FREE

onboarding9

Step Cards with Numbered Indicators

Animated step wizard with square numbered indicators and content cards for each step. Perfect for product walkthroughs that guide users through key features.

PRO

onboarding5

Horizontal Steps with Progress Line

Multi-step progress indicator with numbered circles connected by a progress line. Perfect for account setup wizards that show users their completion status.

PRO

onboarding31

Three Step Getting Started

A getting-started section with an eyebrow over a hairline rule, a two-column heading, three monospace-numbered steps under their own hairlines, and an accent button.

PRO

onboarding33

Interactive Setup Checklist

A setup panel pairing a soft progress column, where an oversized percentage and accent bar react to what is ticked, with hairline checklist rows that each carry a description and a jump-in link.