Product Card Grid
Responsive product cards with sale badges, ratings and a wishlist button layered above the card link so it stays clickable.
The editorial header above a collection grid, carrying the four facts that decide a considered purchase.
components/collection-story-split.tsxnpx hoverlab add collection-story-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.
The collection
A grid of forty products with a one-line title is a search result. For anything considered, the reason the collection exists is what does the selling, and it belongs above the grid rather than on a linked story page nobody opens.
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
/**
* <CollectionStorySplit> — The editorial header above a collection grid, carrying the four facts that decide a considered purchase.
*
* A grid of forty products under a one-line title is a search result. For
* anything considered — furniture, tools, clothing meant to last — the
* reason the collection exists is what does the selling, and the layout
* problem is where that reasoning goes.
*
* The obvious wrong answer is a linked story page. It is the standard
* pattern and almost nobody opens it, which means the argument for the
* price is one click away from every person deciding on the price.
*
* So four points sit above the grid, and each is a checkable fact rather
* than a mood: a named city and a family-run factory, repairs charged at
* cost, deadstock as the reason sizes vanish, and one price all year.
*
* That third point is the one that converts a limitation into a reason.
* "Sizes run out and do not come back" is bad news stated plainly, and it
* is also the honest explanation for scarcity that a countdown timer fakes.
*
* The fourth is a commitment with teeth — no seasonal markdown means
* nobody who bought in March is punished in July — and it should only be on
* the page if the merchandising calendar actually honours it.
*
* Accessibility: the tick `<svg>` is `aria-hidden` with `currentColor`, so
* it is decoration rather than four announcements; the heading gives the
* section its accessible name via `aria-labelledby`; the points are a real
* `<ul>`. The drawn panel is a placeholder — this is the one block in the
* wave where `media` should almost certainly be a real photograph, and it
* is a prop rather than a hard-coded `<img>` for exactly that reason.
*/
import * as React from 'react'
export interface CollectionStorySplitPoint {
label: string
detail?: string
}
export interface CollectionStorySplitProps {
eyebrow?: string
heading?: string
intro?: string
points?: CollectionStorySplitPoint[]
/** Your own visual. Omit for the drawn panel, which needs no asset. */
media?: React.ReactNode
className?: string
}
const POINTS: CollectionStorySplitPoint[] = [
{ label: "One factory, named", detail: "Porto, family-run, thirty years. The address is on the about page rather than implied by a photograph." },
{ label: "Repairs, not warranties", detail: "Send it back at any age. Repair is charged at cost and typically beats replacing it." },
{ label: "Deadstock and offcuts", detail: "Which is why sizes run out and do not come back. The stock list says which." },
{ label: "Priced once", detail: "No seasonal markdown, so nobody who bought in March is punished for it in July." },
]
/**
* 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 `collection-story-split-heading-${(hash >>> 0).toString(36).slice(0, 4)}`
}
export function CollectionStorySplit({
eyebrow = "The collection",
heading = "Made to be repaired, not replaced",
intro = "A grid of forty products with a one-line title is a search result. For anything considered, the reason the collection exists is what does the selling, and it belongs above the grid rather than on a linked story page nobody opens.",
points = POINTS,
media,
className,
}: CollectionStorySplitProps) {
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/collection-story-split.tsx and import it where you need the section:
import { CollectionStorySplit } from '@/components/collection-story-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 | "The collection" |
heading | string | "Made to be repaired, not replaced" |
intro | string | — |
points | CollectionStorySplitPoint[] | 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.
<!--
Collection Story 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="collection-story-split-heading-hunr" 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">The collection</p>
<h2 id="collection-story-split-heading-hunr" class="mt-2 text-3xl font-semibold tracking-tight text-foreground sm:text-4xl">Made to be repaired, not replaced</h2>
<p class="mt-4 text-base text-muted-foreground">A grid of forty products with a one-line title is a search result. For anything considered, the reason the collection exists is what does the selling, and it belongs above the grid rather than on a linked story page nobody opens.</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">One factory, named</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Porto, family-run, thirty years. The address is on the about page rather than implied by a photograph.</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">Repairs, not warranties</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Send it back at any age. Repair is charged at cost and typically beats replacing it.</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">Deadstock and offcuts</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Which is why sizes run out and do not come back. The stock list says which.</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">Priced once</span>
<span class="mt-0.5 block text-sm text-muted-foreground">No seasonal markdown, so nobody who bought in March is punished for it in July.</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 Product ListingsCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
Responsive product cards with sale badges, ratings and a wishlist button layered above the card link so it stays clickable.
Category, size, colour and price facets as proper fieldsets, with colour swatches that carry their name as well as their hue.
Result count, sort and density switch — with the count in an aria-live region, since it is the only feedback a filter change gives some users.
A "you might also like" row on native scroll-snap — touch swiping, momentum and keyboard support for free, with no carousel library.
Three products side by side with the row labels pinned through a horizontal scroll, an "only show differences" toggle that says how many rows it hid, and "best" marked only where better means something.
Availability per variant stated before the cart, because discovering it at checkout is where the basket gets abandoned.
Results on one side, a drawn map on the other, scrolling independently. The map is explicitly decorative and out of the tab order — the list is the content, not its companion.
A restaurant menu typeset as a bill of fare rather than a product grid — dotted leaders to the price, dietary marks as abbreviations with a key, and prices as strings so “market price” still fits.