Staaarter

Tabbed Features

A centered header sits above a horizontal, pill-style top-tab bar. Each workstream tab swaps in its own copy panel, benefit checklist, and screenshot rendered inside a plain browser-chrome frame, laid out side by side.

By Staaarter Team
Feature
Docs
Live preview

Docs

Installation

A real shadcn registry command, not a copy-paste stand-in: it fetches this block plus its media-slot dependencies and any missing npm packages, and installs them straight into your project.

npx shadcn add https://staaarter.com/r/tabbed-features.json

Prefer not to use the CLI? Copy the source from the Code toggle above into src/components/blocks/feature/feature56.tsx instead.

Usage

The file also exports feature56Demo, the exact props behind the preview above. Spread it to get a working section in one line, then replace it with your own data.

import { Feature56, feature56Demo } from "@/components/blocks/feature/feature56";

export default function Page() {
  return <Feature56 {...feature56Demo} />;
}

Props

PropTypeDefaultDescription
eyebrowstringnoneSmall label above the heading.
headingReactNodenoneSection heading.
descriptionstringnoneSupporting copy under the heading.
workstreamsWorkstreamPanel[]noneTab panels, rendered in array order in the top tab bar and switched by click.
classNamestringnoneExtra classes for the outer section element.

Types

type WorkstreamPanel = {
  label: string;
  title: string;
  description: string;
  checklist: string[];
  screenshot?: { src: string; alt: string };
};

Behavior notes

  • Real client-side state: clicking a top tab switches the active workstream; the first workstream (index 0) is active by default on mount.
  • Deliberately differentiated from Feature Tabs Explorer (feature55): tabs run horizontally across the top in a pill segmented control instead of a vertical rail, and the preview uses a plain three-dot browser-chrome frame instead of a phone frame.
  • Each tab's icon comes from a fixed, hardcoded set indexed by tab position rather than a per-tab icon prop, since a "use client" component can't accept a component reference from a server parent.
  • aria-selected on each tab button and role="tablist"/role="tab" wire the tab bar for screen readers.
  • Demo props live in a sibling feature56.demo.tsx (no "use client" directive) per the client-block demo-file-split rule.