Product Image Gallery
Main image with a thumbnail strip built as a real tablist, so arrow keys work and the ratio is fixed to stop the buy box shifting.
The specification table beside the product image, with the two or three figures that decide the purchase pulled out of it.
components/product-spec-split.tsxnpx hoverlab add product-spec-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.
Specification
A forty-row spec table is a place to hide the three figures someone is actually comparing. These are pulled out; the full table is still below for the person who wants it.
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
/**
* <ProductSpecSplit> — The specification table beside the product image, with the two or three figures that decide the purchase pulled out of it.
*
* A forty-row specification table is a good place to hide the three figures
* someone is comparing. The layout problem is that the full table has to
* stay — the person who wants row thirty-one is real — while the three that
* decide the purchase are pulled in front of it.
*
* The obvious wrong answer is to shorten the table. That serves neither
* reader: the comparer still has to scan, and the specialist goes to a
* competitor's page to find the port layout.
*
* So this block is the pulled-out set and it links to the full table rather
* than replacing it. Four points, because a fifth stops being a shortlist.
*
* Each detail names the measurement condition, which is where specification
* sheets are usually dishonest. "18 hours" is meaningless; "18 hours of
* mixed use, measured at 150 nits rather than at minimum brightness" is a
* figure a reader can compare against another one. The weight is quoted with
* the battery in, for the same reason — it is the only way anyone carries
* it.
*
* The repairability row is there because it is increasingly the deciding
* figure and is almost never in the pulled-out set. If it does not apply,
* cut the row rather than replacing it with a marketing line.
*
* Accessibility: the tick <svg> is `aria-hidden` with `fill="currentColor"`,
* so it is decoration that inherits the text colour and is not announced
* four times; the section takes its accessible name from the heading through
* `aria-labelledby`; and the points are a genuine <ul> so their number is
* announced before they are read.
*
* The panel on the right is drawn rather than an image — nothing to host,
* no layout shift, and it follows the theme. Pass `media` to put a real
* product photograph there, which is the one place in this block where a
* photograph is the right answer.
*/
import * as React from 'react'
export interface ProductSpecSplitPoint {
label: string
detail?: string
}
export interface ProductSpecSplitProps {
eyebrow?: string
heading?: string
intro?: string
points?: ProductSpecSplitPoint[]
/** Your own visual. Omit for the drawn panel, which needs no asset. */
media?: React.ReactNode
className?: string
}
const POINTS: ProductSpecSplitPoint[] = [
{ label: "Weight", detail: "1.24 kg with the battery, which is the only way anyone carries it." },
{ label: "Battery", detail: "18 hours of mixed use, measured at 150 nits rather than at minimum brightness." },
{ label: "Ports", detail: "Two USB-C, one HDMI, one headphone. No dongle in the box and none needed." },
{ label: "Repairability", detail: "Battery and SSD are user-replaceable. Parts and the manual are public." },
]
/*
Per-instance id, hashed from the heading.
The literal id this replaced collided the moment a second page used this
block: `aria-labelledby` pointing at a duplicated id resolves to whichever
element is first in the document, so the second copy of the section was
announced with the first copy's heading. Server component, so there is no
`useId` available -- hashing the heading gives each instance its own target
without a hook, a prop or a counter, and stays stable across server and
client renders in a way a counter would not.
*/
function instanceId(...parts: (string | undefined)[]): string {
const text = parts.filter(Boolean).join('|')
let hash = 0
for (let i = 0; i < text.length; i++) hash = (Math.imul(hash, 31) + text.charCodeAt(i)) | 0
return (hash >>> 0).toString(36).slice(0, 6)
}
export function ProductSpecSplit({
eyebrow = "Specification",
heading = "The numbers that decide it",
intro = "A forty-row spec table is a place to hide the three figures someone is actually comparing. These are pulled out; the full table is still below for the person who wants it.",
points = POINTS,
media,
className,
}: ProductSpecSplitProps) {
const headingId = `product-spec-split-heading-${instanceId(heading, eyebrow)}`
return (
<section
aria-labelledby={headingId}
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}
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/product-spec-split.tsx and import it where you need the section:
import { ProductSpecSplit } from '@/components/product-spec-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 | "Specification" |
heading | string | "The numbers that decide it" |
intro | string | — |
points | ProductSpecSplitPoint[] | 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.
<!--
Product Spec 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 has no interactive behaviour, so nothing is missing.
-->
<section aria-labelledby="product-spec-split-heading-l9wgwm" 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">Specification</p>
<h2 id="product-spec-split-heading-l9wgwm" class="mt-2 text-3xl font-semibold tracking-tight text-foreground sm:text-4xl">The numbers that decide it</h2>
<p class="mt-4 text-base text-muted-foreground">A forty-row spec table is a place to hide the three figures someone is actually comparing. These are pulled out; the full table is still below for the person who wants it.</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">Weight</span>
<span class="mt-0.5 block text-sm text-muted-foreground">1.24 kg with the battery, which is the only way anyone carries 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">Battery</span>
<span class="mt-0.5 block text-sm text-muted-foreground">18 hours of mixed use, measured at 150 nits rather than at minimum brightness.</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">Ports</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Two USB-C, one HDMI, one headphone. No dongle in the box and none needed.</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">Repairability</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Battery and SSD are user-replaceable. Parts and the manual are public.</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 DetailCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
Main image with a thumbnail strip built as a real tablist, so arrow keys work and the ratio is fixed to stop the buy box shifting.
Price, variant radiogroup, quantity stepper and add-to-bag — with sold-out sizes disabled and visible rather than hidden.
Description, materials, delivery and returns in named <details> elements — no JavaScript, and the copy stays indexable while collapsed.
Average rating with a clickable histogram — because a 4.3 of forties and fives is a different product from a 4.3 of ones and fives.
The panel that decides whether the parcel comes back: what the model is wearing and what previous buyers did, above a table whose inches are converted rather than maintained twice.
The capture that replaces a dead sold-out button, with the honest caveat that a notification is not a reservation.