Builder

Compose a page out of real sections.

Pick sections from 307 blocks, drag them into order, and theme the lot in one go. What renders below is the actual component, not a picture of it — the same one the 126 pages in the catalog are built from. When it looks right, run it or take the source.

The layout and the theme both live in the address bar, so this page is shareable as a link and needs no account. Every edit is a normal navigation, which makes the back button an undo.

The catalog default. Every section reads its colours from tokens.

Outline

4 / 30

Start overDrag a row, or use the arrows

Canvas

Hover a section to move, duplicate or remove it. Drag it to reorder.

CSV Column Mapper

customers-export.csv

1,284 rows · 6 columns found

Step 2 of 3

Full Name

Ada Lovelace · Grace Hopper

Work Email

ada@analytical.co · grace@navy.mil

One address per row

Company

Analytical Engines · US Navy

Phone

+44 20 7946 0958 · +1 202 555 0114

Signed Up

2026-03-14 · 2026-04-02

Internal Notes

do not contact

Split Hero with Product Panel

Now in public beta

Ship your next idea before the weekend.

Everything you need to launch — auth, billing, analytics and a dashboard your customers will actually understand.

Start building Book a demo

No credit card required
Free for 14 days
Cancel anytime

Integration Depth Split

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.

Grounding Split

Grounding

Every claim points at something

The interesting half of a retrieval system is not what it does when it finds the answer. It is what it does when it does not.

Citations on the sentenceNot a source list at the bottom. The claim and its evidence are next to each other or the citation is decoration.
Quoted, not paraphrasedThe retrieved passage is shown as written, so you can see whether it says what the answer claims.
It says when it does not knowNo passage above the relevance floor produces "I could not find this", not a fluent guess.
Stale sources are flaggedAge travels with the passage. A confident answer from a two-year-old document is the failure nobody catches.

Add a section

Every block in the catalog, filtered by what it is. Click to append to the end of the page, or drag one into the outline to place it.

307 sections

Take it with you

1. Install the sections

Writes each block to components/, which is where the page below imports them from.

npx hoverlab add csv-import-mapper hero-split integration-depth-split grounding-split

These sections import lucide-react — everything else they use is React and Tailwind.

2. Name the page

Sets the component name and the filename. Optional.

Saves as app/composed-page.tsx

3. Take the source

/**
 * ComposedPage — composed from 4 Hoverlab blocks.
 *
 * Install the sections this file imports:
 *   npx hoverlab add csv-import-mapper hero-split integration-depth-split grounding-split
 *
 * Packages the sections need: lucide-react
 *
 * Rebuild or edit this layout: https://hoverlab5.netlify.app/builder?b=csv-import-mapper,hero-split,integration-depth-split,grounding-split
 */

import * as React from 'react'
import { CsvImportMapper } from '@/components/csv-import-mapper'
import { HeroSplit } from '@/components/hero-split'
import { IntegrationDepthSplit } from '@/components/integration-depth-split'
import { GroundingSplit } from '@/components/grounding-split'

export default function ComposedPage() {
  return (
    <main className="min-h-screen bg-background text-foreground">
      <CsvImportMapper />
      <HeroSplit />
      <IntegrationDepthSplit />
      <GroundingSplit />
    </main>
  )
}