Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Bento With Compliance Cells Logos Block for React

A bento of proof for a secrets-management tool: one tall customer story beside four compliance cells, each a check, a standard written as text and a context line, in cells that share their hairlines.

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 compliance bento for React with Base UI. A centred header, "Four standards, 0 findings" and one sentence, sits over a grid that runs from rail to rail of the page column, its top rule meeting the rails at + marks. At the start, one tall cell tells a customer's story: a flagship mark and name, an industry badge, a zero-findings figure, a one-line quote and who said it. Beside it, four cells name the standards the product is audited to (SOC 2 Type II, ISO 27001, HIPAA and GDPR), each with a check, the standard written out as text and a line of context. All the cells share their hairlines, and the bento ends the block, so the next section's top rule closes it. On a phone the story comes first and the four cells sit two by two under it; from lg the story is a third of the width and the cells fill the other two thirds. It's built from Guides, Badge and Avatar, with a CSS transition for the entrance and your theme's tokens for every colour. For security and infrastructure products selling to buyers whose first question is about audits.

FAQ

How do I change the standards?

Edit STANDARDS at the top of the file: each entry is a name and a context line. The grid is drawn for four, two by two beside the story; a different count needs the grid's rows changed, and an odd count leaves an empty cell showing the hairline colour. List only a standard you actually hold, and keep the context line to one short sentence.

Why are the standards text, not certification logos?

The marks of an audit body or a standards organisation are trademarked and licensed, so the block writes each standard's name in text with a check beside it. If you hold a licence to show a mark, put it where the check is. The names read the same to everyone, including screen readers.

How do I change the customer story?

Edit STORY: the customer's name, its industry badge, the figure and its label, the quote and who said it. Keep the quote to one sentence: on a phone the story has to end early enough that the four cells appear on the first screen. The figure is wrapped in a bdi element so a sign or a unit stays in reading order in a right-to-left layout.

Is the block accessible?

Yes. The header is an h2, the quote is a blockquote in a figure with a figcaption, and the standards are a list named "Compliance standards" with each standard as an h3. The checks, the flagship mark and the initials are hidden from assistive technology, because the text says the same thing. Nothing in the block is focusable.

What moves, and what happens with reduced motion?

The header and the bento fade up once when the page loads, with CSS transitions. With reduced motion the transitions are off and the section simply appears.

How does it fit on a phone?

One column: the story first, then the four standards two by two with tighter padding. Nothing scrolls sideways at 320 pixels.

  • Pro

    A bento for an on-call alert router: one tall customer story with a big result, a quote and a link, beside four customers that each carry an industry pill and a retention figure, in cells that share their hairlines.

  • Pro

    A hub of proof for an endpoint-security tool: a flagship customer in a framed card, a connector down to six supporting wordmarks, and a closing band of four compliance cells with a line of detail each.

  • Pro

    A wall of twelve law-firm wordmarks for a legal-document tool in cells that share their hairlines, closed by one centred line of four outline chips naming the standards it is audited to.

  • Pro

    Exactly five cells for a usage-billing API: one featured customer story as tall as two rows and four single customer cells, each outlined by lines that run past its corners, with one Shine Button in the header.

  • Pro

    Six customer results for an invoice-financing product in two bands of cells, each with the customer's wordmark, a figure at display size, what it counts and a chip with the change since last year.

  • Pro

    A bento of five customers for a payments product: a flagship story across two columns beside four cells that alternate between a quote and a big figure, each led by the customer's wordmark.