Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Org Chart Showcase Hero Block for React

A showcase hero for a people platform: centred copy and a Shine Button above a full-width tinted band that holds a three-level org chart.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

A showcase hero with a three-level org chart, for React with Base UI, between solid rails. Centred above, an announcement pill, a headline, a sentence and two calls to action: a ShineButton and an outline Button, both links. Below them a full-width band, ruled at its top with + marks on the rails and tinted, closes the block: a CEO, three VPs and two reports under each, every person a small card with initials, a name and a role. The chart is a real nested list, and its connectors are drawn in CSS on the list items, so they always meet the cards, at any width and in right-to-left layouts. Each level settles in after the one above it with a CSS transition that stays still under reduced motion. It's built from Announcement, Status, Shine Button, Button, Guides and Avatar with Lucide icons and Tailwind CSS. Made for HR platforms, people operations tools, team directories and company wikis.

FAQ

How do I change the people in the chart?

Edit ORG. It's one person, the top of the tree, and each person has initials, a name, a role and their direct reports, a list of people in the same shape (empty for the last level). The chart draws whatever you put there: add a fourth VP or a third report and the connectors follow, since they're drawn by each list item, not at fixed coordinates.

How are the connecting lines drawn?

In CSS, with no SVG. Each team's list draws a short line down from its manager (before: on the ul), and each person draws a stub up to the team's rail (before: on the li) and their part of the rail itself (after:), which starts at the first person's centre and ends at the last one's. The insets are logical (start-1/2, first:after:start-1/2, last:after:end-1/2), so the chart mirrors in right-to-left layouts, and the lines can never miss a card the way fixed coordinates do. The VPs' row is a grid that each VP joins through a subgrid (grid-rows-subgrid), so the VP cards share one height and their teams start on one line, however the names wrap.

Can I show more levels or a whole company?

Nest another ul with the TEAM class under a report, with REPORT on its items, and give its cards their own style in CARD and LABEL. Three levels is about what fits under a hero headline, though; for a whole company, draw the top two levels here and link to the full directory.

How do screen readers read the chart?

As what it is: nested lists, labelled "Org chart". A screen reader announces the CEO, then a list of three VPs, each with a list of two reports, by name and role; the initials are hidden, since the name follows them. The headline is the block's one h1, and nothing in the chart takes focus.

How does the chart fit on a phone?

The copy comes first and the band under it, so the Shine Button is on the first screen. Below sm, the VP cards stack the avatar over the name, and the reports shrink to their initials, with their names and roles still in the page for screen readers (sr-only sm:not-sr-only); from sm up, every card shows its name and role. The chart fits without scrolling down to 320px.

When should I use the org chart instead of an avatar grid?

Use the org chart when structure is the point: who reports to whom, as in HR tools, people platforms and team directories. Use an avatar grid when you just want to show the team, or how many people use the product.

  • Pro

    Split Avatar Grid Hero

    Logos and social proof

    A compact split team hero: a headline, a Shine Button, a second action and a line of team facts beside a two-by-two grid of large avatars with names and roles in cells that share hairlines.

  • Pro

    A reverse split hero for an infrastructure platform: a service topology on a tinted canvas flush with the start rail, six icon nodes, a travelling request and an inspector, beside a headline, a Shine Button and three ticks.

  • Pro

    A split hero for a metrics pipeline: the headline and a Shine Button beside a divider and a flow diagram in a hairline frame, with a closing band of three proof cells.

  • Pro

    A reverse split hero for a sprint planner: a wide board window that runs flush to the start rail and fades at its foot, with a card mid-drag over a drop slot, then a divider and the copy with a Shine Button.

  • Pro

    A split hero for a database tool: the headline, a Shine Button and three ticks beside a wide schema editor that runs flush to the page's end rail, with a model sidebar and a diagram whose foreign keys link to the rows they reference.

  • Pro

    A split hero for an AI assistant: a headline, a Shine Button and a second action beside a chat app sketched in skeleton bars that runs off a tinted panel, closed by a band of three feature cells.