Bento Feature Grid
Six tiles on an asymmetric 4x3 grid with per-tile spans, a hover glow and a mobile collapse that follows source order.
An integrations section that says how deep each one goes, instead of a wall of logos that all imply the same thing.
components/integration-depth-split.tsxnpx hoverlab add integration-depth-split
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
Start a page with this section — add more, order them, and leave with the page source.
Integrations
A grid of thirty logos implies thirty equivalent integrations. Usually four are deep, six are one-way, and the rest are a Zapier entry. Saying which is which costs one sentence each.
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
/**
* <IntegrationDepthSplit> — An integrations section that says how deep each one goes, instead of a wall of logos that all imply the same thing.
*
* A grid of thirty logos implies thirty equivalent integrations. Usually
* four are deep, six are one-way, and the rest are a Zapier entry. The
* layout problem is that the logo grid is the industry-standard answer and
* it is structurally incapable of saying which is which.
*
* So this replaces the wall with four tiers, each defined by what actually
* moves. The obvious wrong answer is to keep the grid and add a footnote,
* which nobody reads and which still lets the grid make the claim.
*
* The third tier is the one that earns the section's credibility:
* notifications only. Posting events into a channel is genuinely useful and
* is not a sync, so it is not listed as one — and a reader who finds one
* integration honestly downgraded believes the tier above it.
*
* The fourth tier says the API is the same one the deep integrations are
* built on. That converts "everything else" from an excuse into a
* capability, and it is only worth saying if it is true.
*
* Accessibility: the tick is an inline `<svg>` with `aria-hidden` and
* `fill="currentColor"` — decoration, inheriting the text colour, skipped by
* a screen reader rather than announced before every point. The section's
* accessible name comes from the heading via `aria-labelledby`, and the
* points are a real `<ul>` so the count is announced up front.
*
* The drawn panel replaces a screenshot for the usual reasons: no asset to
* host, no layout shift, and it is correct in both themes. Pass `media` to
* put the actual integrations directory there.
*/
import * as React from 'react'
export interface IntegrationDepthSplitPoint {
label: string
detail?: string
}
export interface IntegrationDepthSplitProps {
eyebrow?: string
heading?: string
intro?: string
points?: IntegrationDepthSplitPoint[]
/** Your own visual. Omit for the drawn panel, which needs no asset. */
media?: React.ReactNode
className?: string
}
const POINTS: IntegrationDepthSplitPoint[] = [
{ label: "Two-way sync", detail: "Changes flow both directions and conflicts are resolved, not last-write-wins." },
{ label: "One-way import", detail: "We read from them on a schedule. Nothing is written back, which is often what you want." },
{ label: "Notifications only", detail: "We post events into the channel. Honest, useful, and not a sync — so it is not listed as one." },
{ label: "Via the API", detail: "Everything else. Documented, versioned, and the same API the first row is built on." },
]
/**
* A per-instance heading id, derived rather than generated.
*
* `React.useId()` is the textbook fix for a literal id in a reusable
* component and is not available here: this block has no `'use client'`
* and does not warrant one. It renders text, and a band that hydrates on
* every page to render text is a cost with nothing on the other side of
* it. Same call, and the same reasoning, as `footer-mega`.
*
* Hashing the heading *and* the intro is deliberate. Either alone works
* until two callers happen to agree, which is exactly what a catalog hub
* rendering every page into one document arranges for; between them they
* are the two props nobody leaves at the default.
*/
function headingId(heading: string, intro: string): string {
let hash = 0
const source = `${heading}|${intro}`
for (let i = 0; i < source.length; i++) {
hash = (Math.imul(hash, 31) + source.charCodeAt(i)) | 0
}
return `integration-depth-split-heading-${(hash >>> 0).toString(36).slice(0, 4)}`
}
export function IntegrationDepthSplit({
eyebrow = "Integrations",
heading = "Not all of these mean the same thing",
intro = "A grid of thirty logos implies thirty equivalent integrations. Usually four are deep, six are one-way, and the rest are a Zapier entry. Saying which is which costs one sentence each.",
points = POINTS,
media,
className,
}: IntegrationDepthSplitProps) {
return (
<section
aria-labelledby={headingId(heading, intro)}
className={`w-full bg-background px-6 py-16 sm:py-24 ${className ?? ''}`}
>
<div className="mx-auto grid max-w-6xl items-center gap-12 lg:grid-cols-2">
<div>
<p className="text-sm font-medium text-primary">{eyebrow}</p>
<h2
id={headingId(heading, intro)}
className="mt-2 text-3xl font-semibold tracking-tight text-foreground sm:text-4xl"
>
{heading}
</h2>
<p className="mt-4 text-base text-muted-foreground">{intro}</p>
<ul className="mt-8 space-y-4">
{points.map((point) => (
<li key={point.label} className="flex gap-3">
{/*
currentColor, not a token in a raw colour function. These
are complete oklch() values, so hsl(var(--primary)) is not
a colour and the declaration is dropped silently.
*/}
<svg
aria-hidden="true"
viewBox="0 0 20 20"
className="mt-0.5 size-5 shrink-0 text-primary"
fill="currentColor"
>
<path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z" />
</svg>
<span>
<span className="block text-sm font-medium text-foreground">{point.label}</span>
{point.detail ? (
<span className="mt-0.5 block text-sm text-muted-foreground">
{point.detail}
</span>
) : null}
</span>
</li>
))}
</ul>
</div>
{/*
The drawn panel rather than an <img>. No asset to host, no layout
shift while it loads, and it themes with the rest of the page —
which a screenshot of somebody's light-mode dashboard does not.
*/}
<div className="rounded-xl border border-border bg-card p-6 shadow-sm">
{media ?? (
<div aria-hidden="true" className="space-y-3">
<div className="h-3 w-1/3 rounded bg-primary/30 border border-transparent" />
<div className="h-24 rounded-lg bg-muted border border-transparent" />
<div className="grid grid-cols-3 gap-3">
<div className="h-14 rounded-lg bg-muted border border-transparent" />
<div className="h-14 rounded-lg bg-muted border border-transparent" />
<div className="h-14 rounded-lg bg-muted border border-transparent" />
</div>
<div className="h-3 w-2/3 rounded bg-muted border border-transparent" />
<div className="h-3 w-1/2 rounded bg-muted border border-transparent" />
</div>
)}
</div>
</div>
</section>
)
}
bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.Drop it at components/integration-depth-split.tsx and import it where you need the section:
import { IntegrationDepthSplit } from '@/components/integration-depth-split'2 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.
Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.
| Prop | Type | Default |
|---|---|---|
eyebrow | string | "Integrations" |
heading | string | "Not all of these mean the same thing" |
intro | string | — |
points | IntegrationDepthSplitPoint[] | POINTS |
mediaYour own visual. Omit for the drawn panel, which needs no asset. | React.ReactNode | — |
className | string | — |
The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.
This block is interactive. The markup below is its initial state with the event handlers stripped — you will need to re-wire the behaviour in your framework.
<!--
Integration Depth Split — markup from the Hoverlab catalog.
This is the block rendered once to HTML and wrapped as a component
file. It is not a port of the React source: the Tailwind classes carry
the design, which is the part that took the work, and they are the same
in every framework.
This block is interactive in React and the handlers are NOT here.
Buttons, toggles and menus render in their initial state and do
nothing until you wire them up.
-->
<section aria-labelledby="integration-depth-split-heading-vtku" class="w-full bg-background px-6 py-16 sm:py-24 ">
<div class="mx-auto grid max-w-6xl items-center gap-12 lg:grid-cols-2">
<div>
<p class="text-sm font-medium text-primary">Integrations</p>
<h2 id="integration-depth-split-heading-vtku" class="mt-2 text-3xl font-semibold tracking-tight text-foreground sm:text-4xl">Not all of these mean the same thing</h2>
<p class="mt-4 text-base text-muted-foreground">A grid of thirty logos implies thirty equivalent integrations. Usually four are deep, six are one-way, and the rest are a Zapier entry. Saying which is which costs one sentence each.</p>
<ul class="mt-8 space-y-4">
<li class="flex gap-3">
<svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
<path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
</svg>
<span>
<span class="block text-sm font-medium text-foreground">Two-way sync</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Changes flow both directions and conflicts are resolved, not last-write-wins.</span>
</span>
</li>
<li class="flex gap-3">
<svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
<path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
</svg>
<span>
<span class="block text-sm font-medium text-foreground">One-way import</span>
<span class="mt-0.5 block text-sm text-muted-foreground">We read from them on a schedule. Nothing is written back, which is often what you want.</span>
</span>
</li>
<li class="flex gap-3">
<svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
<path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
</svg>
<span>
<span class="block text-sm font-medium text-foreground">Notifications only</span>
<span class="mt-0.5 block text-sm text-muted-foreground">We post events into the channel. Honest, useful, and not a sync — so it is not listed as one.</span>
</span>
</li>
<li class="flex gap-3">
<svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
<path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
</svg>
<span>
<span class="block text-sm font-medium text-foreground">Via the API</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Everything else. Documented, versioned, and the same API the first row is built on.</span>
</span>
</li>
</ul>
</div>
<div class="rounded-xl border border-border bg-card p-6 shadow-sm">
<div aria-hidden="true" class="space-y-3">
<div class="h-3 w-1/3 rounded bg-primary/30 border border-transparent"></div>
<div class="h-24 rounded-lg bg-muted border border-transparent"></div>
<div class="grid grid-cols-3 gap-3">
<div class="h-14 rounded-lg bg-muted border border-transparent"></div>
<div class="h-14 rounded-lg bg-muted border border-transparent"></div>
<div class="h-14 rounded-lg bg-muted border border-transparent"></div>
</div>
<div class="h-3 w-2/3 rounded bg-muted border border-transparent"></div>
<div class="h-3 w-1/2 rounded bg-muted border border-transparent"></div>
</div>
</div>
</div>
</section>
What each framework gets across the whole catalog — effects convert properly; this rung is markup.
The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Want the whole screen instead of this one section? Open a page and copy it entire.
All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.
Browse Feature SectionsCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
Six tiles on an asymmetric 4x3 grid with per-tile spans, a hover glow and a mobile collapse that follows source order.
A full row per feature with the media side flipping each time, so the eye re-enters the page instead of skimming a stack of identical blocks.
Uniform cells, no spans, no state — the grid for nine things that matter equally, where a bento would be a wall and tabs would be a filing cabinet.
What each integration actually does, not a wall of logos — with availability as a text pill rather than a tinted border, and the name as the link so the card is not one enormous one.
A "who this is for" grid: four cards naming an audience, the outcome they want and the bullets that get them there.
A feature section paired with a tabbed fake editor — real selectable code, generated line numbers and a copy button.
Features as a real tablist — arrow keys, roving focus and a drawn product panel per tab — for the section where four features would otherwise fight for one scroll.