EngineeringShipping faster with a component registry
How we cut landing page build time from days to hours by treating sections as installable units.
A portfolio card with a full bleed image, hover zoom, and gradient title overlay for work showcases.
The import and the props worth knowing about, in one place.
import { Card6 } from "@/components/beste/component/card6";
// The whole card becomes a link when href is set.
<Card6
src="/work/nordwind.jpg"
title="Nordwind Studio"
subtitle="Brand identity"
href="/work/nordwind"
/>
<Card6
src="/work/lumen.jpg"
title="Lumen App"
subtitle="Product design"
tone="primary" // arrow seal: "light" (default) | "primary"
/>Every one of these is in the component already. They are listed because a props table cannot mention a gesture, so nothing else on this page can tell you they exist.
| Hover | The card lifts and the image scales inside its frame; `motion-reduce` turns the movement off. |
|---|
Read from the component's own type, so this cannot drift from what it accepts.
| Prop | Type | Default | Description |
|---|---|---|---|
src* | string | — | Project image URL |
title* | string | — | Project title |
subtitle | string | — | Monospace eyebrow above the title (e.g. "Brand identity") |
href | string | — | If set, the whole card links to this href |
tone | "light" | "primary" | — | Corner arrow seal: light chip (default) or primary |
className | string | — | Additional classes merged onto the root |
Orbit One
$189
EngineeringHow we cut landing page build time from days to hours by treating sections as installable units.
