How many features should a landing page show?

Three to six, ranked. Beyond that you are writing documentation on a sales page — link to it instead, which converts better than scrolling past twelve equal boxes.

Do bento grids reflow sensibly on mobile?

These do — the grid collapses to a single column in a defined order rather than letting the browser choose. A bento that reads correctly only at desktop width is a desktop-only section.

Are these feature sections free to use?

All 8 are free to copy and use in your own projects, including commercial ones. A Pro licence exists for redistribution — shipping them inside a product other people buy — and the full terms are on the licence page.

How do I add one to my project?

Install it with the CLI: `npx hoverlab add bento-features` writes the component and its dependencies into your project. Every artifact here also has a copy button for the raw source, and an "Open in sandbox" link if you would rather try it first.

8 Feature sections — copy-paste

Everything, in one place

The parts you would otherwise rebuild on every project.

Fast by default

No runtime, no hydration cost, no waterfall. What you paste is what the browser paints.

Yours to keep

Copied code lives in your repo. Nothing phones home and nothing breaks when we ship.

Zero dependencies

Nothing to audit.

Composable

Every piece works alone or nested inside the next one up.

Accessible

Keyboard paths, focus rings and reduced-motion fallbacks included.

"It replaced our design system backlog."

Priya R., Staff Engineer

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.

Feature Sections114 lines1 dep

Paste it. Ship it.

No install step, no configuration file, no build plugin.

Copy the section straight into your project
Restyle it with your own tokens, not our overrides
Delete what you do not need — it is your code now

1import { PricingTiers } from '@/components/pricing-tiers'2import { FaqAccordion } from '@/components/faq-accordion'3 4export default function Page() {5  return (6    <main>7      <PricingTiers />8      <FaqAccordion />9    </main>10  )11}

Editor Window Showcase

A feature section paired with a tabbed fake editor — real selectable code, generated line numbers and a copy button.

Feature Sections164 lines1 dep2 Sept

Tabbed Feature Showcase

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.

Feature Sections217 lines1 dep2 Sept

How it works

Three steps, none of which involve an account.

Browse

Find it without an account

Every component is readable, customisable and copyable before you sign in for anything. Nothing sits behind an email gate, because a gate at the browse step costs more visitors than it captures.

No login to copy
Public REST API, no key
Live preview on every page

Customise

Tune it in the browser, not after pasting

Colour, timing and sizing are editable where you found the component, and what you copy is what you configured — not a default you then have to hunt through and change.

Brand colours applied across the catalog
Copy reflects your edits

Ship

The code lands in your repo and stops being ours

No runtime dependency, no package that phones home, no version to keep in step. You own the file the moment it is pasted, and updates reach you only when you go and get them.

Plain TSX and utility classes
No attribution required

Alternating Feature Rows

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.

Feature Sections161 lines1 dep

Everything in the box

No tiers on the reading, no account on the copying.

Copy without an account
Every artifact is readable and copyable signed out. The wall is on commercial use, not on looking.
Your colours, applied
Set a brand palette once and the whole catalog previews in it, so what you copy already matches.
Plain TSX and utilities
No runtime package, no wrapper components, nothing to keep in step with a version of ours.
A CLI that scaffolds
Install a component, a page or a whole template into an existing project from the terminal.
Agent-installable
An MCP server your editor can call, so the component arrives without anyone opening a browser.
A public API with no key
The catalog is a plain unauthenticated REST surface. Read it, script it, mirror it.
Accessible by default
Real semantics, real focus states, and decorative motion gated behind prefers-reduced-motion.
No layout shift
Panels are drawn rather than fetched, so nothing reflows while a remote asset decides to arrive.
One ladder, four rungs
Effects build blocks, blocks build pages, pages build templates — one system rather than four products.

Icon Feature Grid

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.

Feature Sections150 lines1 dep

Works with what you already use

What each one actually does, rather than a wall of logos.

Figma
Design
Available
Match a frame against the catalog and get back the components that already look like it.
VS Code
Editor
Available
Install a component from the editor over MCP, without opening a browser.
Next.js
Framework
Available
App Router by default — every block is a server component unless it needs not to be.
Tailwind CSS
Styling
Available
Utility classes and CSS variables, so a copied block inherits your theme rather than fighting it.
shadcn/ui
Registry
Available
A registry the CLI can install from, including a base preset carrying tokens and fonts.
Storybook
Tooling
Beta
Generated stories per artifact, so a copied block lands with its states already documented.
Vue
Framework
Planned
The effects already work anywhere. Blocks and pages as single-file components are in progress.
Sanity
CMS
Planned
Content-driven pages with the copy lifted out into a schema you can edit.

Integration Directory Grid

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.

Feature Sections208 linesNo deps

Built for everyone who ships UI

Whichever seat you are in, the work starts further along.

Frontend developers

Ship polish without the busywork

Stop rewriting the same hover and focus states
Drop a whole section in instead of assembling one
No runtime means no bundle-size regression

Designers

Close the gap between the mock and the build

Show stakeholders something live, not a screenshot
Tune spacing, colour and motion against real markup
Hand over a link instead of a spec document

Founders

Make an MVP feel like a funded product

A credible landing page in an afternoon
No design hire required to launch
Commercial use covered — ship it and charge for it

Learners

Read patterns that are actually in production

Every source is commented and idiomatic
Learn layout and motion by working example
Fork a piece and break it — nothing to set up

Audience Persona Cards

A "who this is for" grid: four cards naming an audience, the outcome they want and the bullets that get them there.

Feature Sections145 lines1 dep10 Sept

Integrations

Not all of these mean 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. Saying which is which costs one sentence each.

Two-way syncChanges flow both directions and conflicts are resolved, not last-write-wins.
One-way importWe read from them on a schedule. Nothing is written back, which is often what you want.
Notifications onlyWe post events into the channel. Honest, useful, and not a sync — so it is not listed as one.
Via the APIEverything else. Documented, versioned, and the same API the first row is built on.

Integration Depth Split

An integrations section that says how deep each one goes, instead of a wall of logos that all imply the same thing.

Feature Sections157 linesNo deps13 Sept

Feature sections

Blocks8

Questions about feature sections

Related collections