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

2 / 30

1
Guest CheckoutCart & Checkout
Move Guest Checkout down Duplicate Guest Checkout Remove Guest Checkout
2
Three-Column Docs FrameContent & Blog
Move Three-Column Docs Frame up Duplicate Three-Column Docs Frame Remove Three-Column Docs Frame

Start overDrag a row, or use the arrows

Canvas

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

Guest Checkout

Checkout

Checking out as a guest. Sign in instead to use saved addresses and cards.

3 items£722.00

Three-Column Docs Frame

Docs navigation

Authentication

Every request to the Acme API is authenticated with a bearer token. This page covers creating a key, storing it safely, and rotating it without downtime.

Acme issues two kinds of keys. Secret keys (prefixed sk_live_) can read and write everything in your project and must only ever live on a server. Publishable keys (prefixed pk_live_) are safe to ship in a browser bundle and can only create client sessions.

Keys are scoped to a project, not to your account. Deleting a project revokes its keys immediately; removing a teammate does not, so treat offboarding as a reason to rotate.

Creating an API key

Create a key from the dashboard under Settings → API keys, then pass it as a bearer token on every request:

curl https://api.acme.dev/v1/projects \
  -H "Authorization: Bearer $ACME_API_KEY"

Note: the full secret is shown once, at creation. Acme stores only a hash, so a lost key cannot be recovered — it can only be rotated.

Rotating keys

Rotation is overlap, not replacement: create the new key, deploy it everywhere, and only then revoke the old one. Both keys stay valid during the window, so a slow rollout never turns into an outage.

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 guest-checkout-form docs-layout

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 2 Hoverlab blocks.
 *
 * Install the sections this file imports:
 *   npx hoverlab add guest-checkout-form docs-layout
 *
 * Packages the sections need: lucide-react
 *
 * Rebuild or edit this layout: https://hoverlab5.netlify.app/builder?b=guest-checkout-form,docs-layout
 */

import * as React from 'react'
import { GuestCheckoutForm } from '@/components/guest-checkout-form'
import { DocsLayout } from '@/components/docs-layout'

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