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.

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.

Data Migration Split

Switching

We move it, and we say what we cannot

Every migration page promises everything comes across. Something never does, and finding out which thing after the cutover is how a switch becomes a rollback.

Records, history and attachmentsEverything with a stable id, including the timestamps, so reports still line up.
Users and their permissionsRoles are mapped, and the mapping is shown for approval before anything is written.
What does not come acrossCustom automations. The triggers have no equivalent here and a silent half-migration is worse.
Run it twiceA trial into a sandbox first, then the real one. The trial is free and does not count against anything.

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

Editorial Masthead Hero

Field notes

The interface is the argument.

Every product makes a claim about how its user should think. Most make it by accident. A short case for treating layout as a position rather than a container.

Ada Whitfield14 March 20269 min read

Read the essay

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 integration-depth-split data-migration-split hero-split hero-editorial

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 integration-depth-split data-migration-split hero-split hero-editorial
 *
 * Packages the sections need: lucide-react
 *
 * Rebuild or edit this layout: https://hoverlab5.netlify.app/builder?b=integration-depth-split,data-migration-split,hero-split,hero-editorial
 */

import * as React from 'react'
import { IntegrationDepthSplit } from '@/components/integration-depth-split'
import { DataMigrationSplit } from '@/components/data-migration-split'
import { HeroSplit } from '@/components/hero-split'
import { HeroEditorial } from '@/components/hero-editorial'

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