Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Source Fan-Out Detail Integration Block for React

An integration detail section for a tracking-plan checker connecting to Segment: what it can read and write as an accordion of three groups, and a framed figure of one source fanning out to four destinations, one of them barred.

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

An integration detail section for React with Base UI, written for Schemawick, a fictional tracking-plan checker that holds events which break the plan, and its Segment connection. The copy comes first in reading order and sits at the end on a wide screen, behind a split divider that runs from the top rule to the block's foot: the title ("Schemawick for Segment") with one sentence, the mark pair (Schemawick's own tile and Segment's neutral lettermark tile, joined by a connector) beside the Connect Segment Shine Button and a View docs link, and what it can read and write as an accordion of three groups, Sources, Tracking plans and Destinations, the first open, each opening to what it reads and a Writes line that says nothing. At the start, a framed figure: one source drawn with four hairline curves to four destination chips (Warehouse, Ads, Email, CRM), the Ads chip barred with a dashed curve and a note that three events are off plan, then the three steps of how it works and the listing's facts. On a phone the parts stack, the figure after the copy, and the curves become a spine with a tick for each chip. The block ends on content, so no rule closes it. The page's rails and top rule come from the Guides spine, so it lines up with its neighbours in a stack. It's built from Guides, Accordion, Badge, Button and Shine Button, with CSS transitions for the entrance and your theme's tokens for every colour. Segment is named in text only: no Segment logo, colour or wordmark ships with the block. The product, its groups and its facts are example data.

FAQ

Can I show Segment's logo?

The block names Segment in text, the way any integration page says what it works with, and ships no Segment logo, colour or wordmark. Segment's tile is a neutral lettermark, Sg in a muted square, sitting in an icon slot that a code comment marks: drop in the official logo only if you have the rights to use it, under the owner's brand guidelines, and never redraw it. Schemawick's own tile has an icon slot for your logo. The pair is hidden from assistive technology because the heading already names both products.

Where should Connect Segment go?

Both buttons are links (href="#"). Point Connect Segment at your own connect flow, where the buyer pastes a token, and View docs at your setup guide. Nothing connects, signs in or sends anything from the block itself. Connect Segment is a Shine Button, the block's one primary action; View docs is an outline button. Both buttons render the link they're given with render, with nativeButton={false}.

Why are there groups instead of scopes?

Segment's Public API tokens carry a workspace role (Workspace Owner or Workspace Member) rather than named scopes, so the block lists what the product reads in three groups instead of inventing scope names, and says so above the accordion. Tokens are created in the workspace settings under Access Management and Tokens. Edit GROUPS to match what your product really reads and writes; each group is a title, a Reads line and a Writes line.

How does the accordion behave?

It opens one group at a time with the first open, and closed groups stay in the page. Each trigger sits in its own heading with a Read badge (an icon and a word), so the access is never colour alone. Tab moves between the triggers, and Enter or Space opens one.

How is the figure built?

The four destinations are a real list; the drawing around them is decoration. On a wide screen the curves are one SVG of cubic strokes that keep the same line width at any size, joining the source to each row, with a dot where they leave it. The barred destination has a dashed curve, a dashed chip, a ban icon and the words "held" for a screen reader, and the caption says how many events are off plan. On a phone a spine and ticks replace the curves. Change DESTINATIONS to show your own.

How does it fit on a phone, in right-to-left layouts and with reduced motion?

Below lg the divider gives way to a rule between the copy and the figure, which stack in reading order. The drawing is a spatial diagram, so it keeps its left-to-right layout in a right-to-left page while the text around it flips. The header and the buttons fade up once on load with CSS transitions; with reduced motion they simply appear. The block has no state beyond the accordion.

  • Pro

    An integration setup section for a tracking-plan checker connecting to Segment: a source type combobox, the write key with a Copy button, and a check that prints four example calls into a dark log window and ends on a result that says it ran in this demo.

  • Pro

    An integration detail section for an onboarding-checklist tool connecting to PostHog: what it can read and write as three read scopes, and a framed figure that joins three event names to the checklist steps they tick.

  • Pro

    Slack Detail Integration

    Scopes and steps

    An integration detail section for a spend tool connecting to Slack: a header with the mark pair and Add to Slack, then what it does, the Slack scopes it reads and writes, three steps to install and the listing's facts.

  • Pro

    An integration detail section for a post-incident review tool connecting to Datadog: a header with the mark pair and Connect Datadog, a framed list of five application-key scopes with one optional write switch, and a three-step rail that rewrites itself.

  • Pro

    A tabbed integration directory for an integration hub: twelve tiles with abstract monograms, each with a connect switch, three category tabs and a live count of what is connected.

  • Pro

    Depth Table Integrations About

    Security and platform

    An integration depth table for a data-sync service: seven systems in plain type with direction, sync frequency, sign-in method and a state dot, in a framed, scrolling table.