Content Site
The article at a real measure
A publication that happens to belong to a company: blog index, article, careers and a 404. The site for when the writing is the product — or the marketing.
Landing page, pricing page, 404. The smallest thing you can put in front of a product and have it look deliberate.
app/globals.cssapp/layout.tsxapp/not-found.tsxapp/page.tsxapp/pricing/page.tsxGETTING-STARTED.mdnpx hoverlab init marketing-site ./my-app
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
/No component library to adopt, no design system to negotiate, no runtime to ship.
Trusted by teams shipping every day
The parts you would otherwise rebuild on every project.
No runtime, no hydration cost, no waterfall. What you paste is what the browser paints.
Copied code lives in your repo. Nothing phones home and nothing breaks when we ship.
Nothing to audit.
Every piece works alone or nested inside the next one up.
Keyboard paths, focus rings and reduced-motion fallbacks included.
Priya R., Staff Engineer
Whichever seat you are in, the work starts further along.
Ship polish without the busywork
Close the gap between the mock and the build
Make an MVP feel like a funded product
Read patterns that are actually in production
No install step, no configuration file, no build plugin.
import { PricingTiers } from '@/components/pricing-tiers'import { FaqAccordion } from '@/components/faq-accordion' export default function Page() { return ( <main> <PricingTiers /> <FaqAccordion /> </main> )}From teams that ship on a deadline.
“We replaced a week of design polish with an afternoon. The parts that used to get cut for time are just there now.”
“Dropped it in on a Friday and shipped Monday. No dependency argument with my team for once.”
“The thing I did not expect: it made our junior engineers faster, because the patterns are readable. They learn from what they paste.”
“Our marketing site went from three weeks to four days. Same designer, same headcount.”
“I stopped keeping a personal snippets file. That file had been following me between jobs for six years.”
Start free. Upgrade when it starts paying for itself.
Everything you need to try it properly.
For working developers shipping real products.
Shared access and billing for a whole team.
Every line, side by side.
| Feature | Free | ProPopular | Team |
|---|---|---|---|
| Projects | 3 | Unlimited | Unlimited |
| Commercial license | Not included | Included | Included |
| Full component library | Not included | Included | Included |
| Figma source files | Not included | Included | Included |
| Seats | 1 | 1 | Up to 10 |
| SSO and audit log | Not included | Not included | Included |
| Support | Community | Priority email | Dedicated |
Everything people ask before getting started.
Yes. Everything here is yours to ship in client work and paid products, with no attribution required.
No. The markup is plain HTML and the styling is utility classes, so it drops into any stack that can render an element.
Copied code is yours — nothing reaches back into your project. Pull a newer version whenever you want it.
There is. A large part of the catalog is free forever; the paid plan unlocks the rest and removes usage limits.
Most of what ships started as someone asking for it.
Start free and stay free until it is worth paying for. Every plan includes the full library — the tiers differ on scale and support, never on quality.
Everything you need to try it properly.
For working developers shipping real products.
Shared access and billing for a whole team.
Every line, side by side.
| Feature | Free | ProPopular | Team |
|---|---|---|---|
| Projects | 3 | Unlimited | Unlimited |
| Commercial license | Not included | Included | Included |
| Full component library | Not included | Included | Included |
| Figma source files | Not included | Included | Included |
| Seats | 1 | 1 | Up to 10 |
| SSO and audit log | Not included | Not included | Included |
| Support | Community | Priority email | Dedicated |
The questions people ask right before they buy.
Any time, in both directions. Upgrades take effect immediately and are prorated; downgrades apply at the end of the current period so you keep what you paid for.
Nothing breaks. We email you at 80% and again at 100%, and usage above the limit is billed at the listed overage rate rather than being cut off mid-request.
Within 30 days, in full, no questions asked. After that we will prorate the unused portion of an annual plan if you ask.
Two months free — that is the 20% you see on the toggle. Annual plans are invoiced and can be paid by bank transfer.
Yes to both. Email us with a sentence about what you are building and we will sort it out — we have never said no to a nonprofit.
Start on Free. You will know within a week whether you need more, and upgrading takes one click with no migration.
Create a free accountThe link may be out of date, or the page may have moved. Here are a few ways forward.
Live components in your current theme — switch routes, or the phone icon to check the mobile layout. Colours are this template’s Vermilion palette, which ships in app/globals.css. Orange-red on warm white. The one palette here loud enough to be a launch — which is the whole brief for three routes and a pricing table.
then
cd marketing-site npm install npm run dev
The archive contains the whole project — routes, blocks, theme tokens, Tailwind and PostCSS config, tsconfig and a .gitignore. One runtime dependency, and no Hoverlab dependency at all: it is your code from the moment it unzips.
The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
| Path | Page | File |
|---|---|---|
| / | SaaS Landing Page | app/page.tsx |
| /pricing | Pricing Page | app/pricing/page.tsx |
| 404 | 404 Page | app/not-found.tsx |
Every file is listed. The 13 files in components/ are the blocks the pages import — each one has its own page if you want to read it on its own.
Everything except the blocks. Opens on app/globals.css — the file that makes the rest look right, since every block styles itself with bg-card and text-muted-foreground rather than literal colours.
@tailwind base;
@tailwind components;
@tailwind utilities;
/**
* Design tokens — the Vermilion palette.
*
* Orange-red on warm white. The one palette here loud enough to be a launch — which is the whole brief for three routes and a pricing table.
*
* This file is the reason a pasted block looks right. Every block and page
* styles itself with semantic classes — `bg-card`, `text-muted-foreground`,
* `border-border` — rather than literal colours, so they inherit whatever
* you define here instead of fighting it. Change a value below and every
* section in the project moves with it. Change the hue on `--primary` and
* `--ring` together and you have rebranded the site.
*
* Values are bare HSL channels, not `hsl(...)` calls. That is what lets
* Tailwind compose them with an alpha suffix: `bg-primary/10` expands to
* `hsl(var(--primary) / 0.1)`, which is impossible if the variable already
* carries its own function wrapper.
*
* Every foreground/background pair below clears WCAG AA (4.5:1) in both
* themes. If you retune one, check the pair rather than trusting the eye —
* mid-lightness accents are the ones that fail.
*/
@layer base {
:root {
--background: 14 40% 99%;
--foreground: 14 32% 10%;
--card: 0 0% 100%;
--card-foreground: 14 32% 10%;
--popover: 0 0% 100%;
--popover-foreground: 14 32% 10%;
--primary: 10 75% 40%;
--primary-foreground: 0 0% 100%;
--secondary: 14 34% 95%;
--secondary-foreground: 14 34% 20%;
--muted: 14 24% 95%;
--muted-foreground: 14 12% 40%;
--accent: 32 55% 92%;
--accent-foreground: 28 50% 20%;
--destructive: 352 78% 40%;
--destructive-foreground: 0 0% 100%;
--border: 14 22% 89%;
--input: 14 22% 89%;
--ring: 10 75% 40%;
--radius: 0.75rem;
}
.dark {
--background: 14 30% 5%;
--foreground: 14 15% 97%;
--card: 14 24% 8%;
--card-foreground: 14 15% 97%;
--popover: 14 24% 8%;
--popover-foreground: 14 15% 97%;
--primary: 10 85% 65%;
--primary-foreground: 14 42% 7%;
--secondary: 14 20% 15%;
--secondary-foreground: 14 15% 97%;
--muted: 14 22% 15%;
--muted-foreground: 14 10% 68%;
--accent: 32 26% 18%;
--accent-foreground: 32 50% 86%;
--destructive: 352 70% 46%;
--destructive-foreground: 0 0% 100%;
--border: 14 18% 19%;
--input: 14 18% 19%;
--ring: 10 85% 65%;
}
}
@layer base {
* {
@apply border-border;
}
body {
@apply bg-background text-foreground antialiased;
}
/**
* Global motion opt-out.
*
* Blocks guard their own animations with Tailwind's `motion-safe:`, but
* third-party CSS and anything you add later will not. This is the
* backstop: it neutralises every animation and transition on the page
* for users who have asked the OS for reduced motion, rather than
* relying on each author to remember.
*/
@media (prefers-reduced-motion: reduce) {
*,
*::before,
*::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
}
The article at a real measure
A publication that happens to belong to a company: blog index, article, careers and a 404. The site for when the writing is the product — or the marketing.
The three-column docs frame
The three-column docs frame — sidebar, article, on-this-page rail — plus a changelog and a 404. The part of the product a search for an error message should find.
Search that answers before the ticket
The support surface, as four routes that agree with each other: searchable answers, the docs, what changed, and a status page carrying the same incident the help page announces.
The terminal that introduces you
An engineer’s site rather than a designer’s: a terminal hero, thirty legible lines of real code on the home page, the projects, the writing and a CV that prints.
A CV that prints properly
A minimal personal site whose home page is the CV itself — printable, indexable, and therefore the copy that actually gets maintained. Five routes, warm paper, square corners.
The live price rail
A regulated exchange, front to back: a moving price rail, a public markets screen, the custody facts, the fee schedule and the risk warning as a section rather than as small print.
The agenda across three tracks
An event site built around a date: the ticket price step-up above the hero, a two-day programme across three tracks, speakers, venue and a code of conduct.
The menu, typeset as a bill of fare
A dining room’s whole site: hours and phone above the fold, the menu typeset as a bill of fare, a real reservation flow, the room and the way to find it.
Map and results, scrolling apart
Property search with results already in it, a listing page that puts tenure and EPC above the prose, the agents, and a valuation route for the other half of the business.
Salary on every row, grouped by craft
A two-sided board where candidates get the whole site and employers get one section and a price. Listings grouped by craft, each with a real salary range and the interview process published.
The install command, before anything else
A project site for a library: install command above the hero, the API in twenty lines, docs, changelog, roadmap, community, and who funds it said plainly.
Facets that are not categories
A faceted index with a listing page that compares each entry against its alternatives, a paid submission route, and a published removal rate.
The watch screen, on the marketing page
A subscription video service: catalogue rails, a real watch screen with chapters and a transcript, one plan at one price, and the account behind it.