You
12 Sep, 09:02The second chair from ORD-88410 arrived with a cracked base plate. I would rather fit a replacement plate myself than wait for a whole chair.
base-plate.jpg
Loading the builder…
Builder
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.
Hover a section to move, duplicate or remove it. Drag it to reorder.
TKT-11842
Sam Okafor replies within 3 h 34 min. That is a commitment, not an estimate. If it passes, the ticket escalates automatically and you do not have to ask.
The second chair from ORD-88410 arrived with a cracked base plate. I would rather fit a replacement plate myself than wait for a whole chair.
base-plate.jpg
Sorry about that. A plate is going out today and should reach you Monday — four M6 bolts under the seat pan, and the allen key in the box fits. Fitting it yourself does not affect the warranty.
Great. Can you confirm the plate is for the tall variant, not the standard one?
Everything you need to launch — auth, billing, analytics and a dashboard your customers will actually understand.
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.
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.
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.
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.
Writes each block to components/, which is where the page below imports them from.
npx hoverlab add support-ticket-thread hero-split docs-layoutThese sections import lucide-react — everything else they use is React and Tailwind.
Sets the component name and the filename. Optional.
Saves as app/composed-page.tsx
/**
* ComposedPage — composed from 3 Hoverlab blocks.
*
* Install the sections this file imports:
* npx hoverlab add support-ticket-thread hero-split docs-layout
*
* Packages the sections need: lucide-react
*
* Rebuild or edit this layout: https://hoverlab5.netlify.app/builder?b=support-ticket-thread,hero-split,docs-layout
*/
import * as React from 'react'
import { SupportTicketThread } from '@/components/support-ticket-thread'
import { HeroSplit } from '@/components/hero-split'
import { DocsLayout } from '@/components/docs-layout'
export default function ComposedPage() {
return (
<main className="min-h-screen bg-background text-foreground">
<SupportTicketThread />
<HeroSplit />
<DocsLayout />
</main>
)
}