You can ship a landing page in 10 minutes with shadcn/ui if your Next.js project already runs Tailwind CSS. The clock covers the page itself: sections, theme and build. A fresh project adds 10 to 15 minutes for create-next-app, shadcn init and dependencies, so budget 20 to 25 minutes from zero.
The part most tutorials skip: shadcn/ui does not ship marketing sections. Its official Blocks page features application screens — dashboard, sidebar, login, signup — and its 66 Base UI components are bricks, not ready-made hero or pricing blocks. For a landing page you either compose sections with Button, Card, Badge, Accordion, Input and Separator, or start from a block catalog built on shadcn/ui. Both fit in 10 minutes; the catalog saves design time, not thinking time.
Versions checked on November 6, 2026: shadcn CLI 4.23.0, Next.js 16.4.5, Tailwind CSS 4.3.5 and React 19.3.1. Prices were checked in November 2026.
What a shadcn/ui block is in 2026#
A shadcn/ui component is a file copied into your repository. npx shadcn@latest add card writes components/ui/card.tsx, with its dependencies and styles. You then import Card from your own code, not from a package that decides its API. A block is a composition of those components: a hero section, a feature grid, a pricing card, an FAQ. The block is not a package: it is code you can delete, reorder or edit.
The official Blocks page says “Free forever. Open Source.” and highlights four families: dashboard, sidebar, login and signup. That is useful for an admin app, less so for a landing page. The components cover 66 bricks in the Base UI variant, including Button, Card, Badge, Accordion, Separator and Input. That is enough for a short sales page.
Since July 2026, new projects use Base UI by default; Radix remains supported and React Aria is available. In practice, npx shadcn@latest init offers Base UI, -b radix keeps Radix and --base aria selects React Aria. The switch does not change your page code: imports stay @/components/ui/....
If you do not want to draw every section, block catalogs built on shadcn/ui exist. Blockforge, from the same publisher as this blog, lists 170+ blocks (hero, pricing, FAQ, footer and more) with a Solo license at $99 (list price $159) and a Team license at $299 (list price $449), as a one-time payment. It is one option: the base components stay free, and a six-section landing is easy to compose by hand.
The 10-minute plan#
The plan below starts from a Next.js 16 project with Tailwind 4 and shadcn/ui already initialized. If you start from zero, keep the same steps and add dependency installation.
| Step | Time | What you do |
|---|---|---|
| 1. Verify the project | 1 min | Node 20.18.1+, components.json, Tailwind 4 |
| 2. Add components | 2 min | button, card, badge, accordion, separator, input |
| 3. Write the hero | 2 min | headline, promise, two buttons, proof card |
| 4. Add sections | 3 min | features, pricing, FAQ |
| 5. CTA and footer | 1 min | form, links, legal |
| 6. Build | 1 min | npm run build |
The table is a budget, not a promise. On a slow connection, npx shadcn@latest add can take more than two minutes; the page code itself does not change.
Step 1: start from a clean project#
For a new project, the commands below create the app, initialize shadcn/ui and add the six components used later.
npx create-next-app@latest my-landing --yes
cd my-landing
npx shadcn@latest init
npx shadcn@latest add button card badge accordion separator input
npm run dev--yes accepts the Next.js 16 defaults: TypeScript, Tailwind CSS, ESLint, App Router, the @/* alias and no src directory. npx shadcn@latest init installs dependencies, creates components.json, adds the cn helper and the CSS variables. Pick Base UI, the default, unless your project already runs Radix.
If the project already exists, skip create-next-app. Check that components.json is present and Tailwind 4 is configured. npx shadcn@latest info prints the base, style and installed components: it is the fastest way to know whether the project is ready.
The 4.23.0 CLI requires Node.js 20.18.1 or newer. Next.js 16.4.5 requires Node.js 20.9.0. If npx fails with a version error, update Node before going further.
Step 2: compose the page#
Create app/page.tsx and paste the code below. It uses six components and one local data set. Replace the copy with your product; the structure stays.
import {
Accordion,
AccordionContent,
AccordionItem,
AccordionTrigger,
} from "@/components/ui/accordion"
import { Badge } from "@/components/ui/badge"
import { Button, buttonVariants } from "@/components/ui/button"
import {
Card,
CardAction,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card"
import { Input } from "@/components/ui/input"
import { Separator } from "@/components/ui/separator"
const features = [
{
title: "Import",
description: "Drop a CSV export or connect your bank account.",
detail: "The file stays in your browser during the analysis.",
},
{
title: "Categorize",
description: "Every expense gets a category and a receipt.",
detail: "Rules are fixed in one click and apply to the next month.",
},
{
title: "File",
description: "Sales tax is calculated and ready to copy into your form.",
detail: "The summary exports as PDF and CSV.",
},
]
const plans = [
{
name: "Solo",
price: "$9",
period: "/ month",
description: "For a freelancer who wants to leave the spreadsheet behind.",
features: ["1 user", "Unlimited imports", "PDF and CSV export"],
featured: false,
},
{
name: "Studio",
price: "$29",
period: "/ month",
description: "For a small team that shares receipts and approvals.",
features: ["5 users", "Roles and approvals", "Support within 24 h"],
featured: true,
},
]
export default function Home() {
return (
<main className="mx-auto flex max-w-6xl flex-col gap-24 px-6 py-16">
<header className="flex items-center justify-between">
<a href="/" className="font-semibold tracking-tight">
Acme
</a>
<nav className="hidden gap-6 text-sm text-muted-foreground sm:flex">
<a href="#features">Features</a>
<a href="#pricing">Pricing</a>
<a href="#faq">FAQ</a>
</nav>
<a className={buttonVariants({ size: "sm" })} href="#pricing">
Try it
</a>
</header>
<section className="grid items-center gap-10 lg:grid-cols-[1.2fr_1fr]">
<div className="flex flex-col items-start gap-6">
<Badge variant="secondary">New: CSV import</Badge>
<h1 className="text-4xl font-semibold tracking-tight sm:text-6xl">
Invoices sorted before coffee.
</h1>
<p className="max-w-xl text-lg text-muted-foreground">
Acme reads your bank exports, categorizes every expense and prepares
your sales tax return. No spreadsheet, no copy-paste.
</p>
<div className="flex flex-wrap gap-3">
<a className={buttonVariants({ size: "lg" })} href="#pricing">
See plans
</a>
<a
className={buttonVariants({ variant: "outline", size: "lg" })}
href="#features"
>
How it works
</a>
</div>
<p className="text-sm text-muted-foreground">
14-day trial. No credit card.
</p>
</div>
<Card>
<CardHeader>
<CardTitle>September 2026</CardTitle>
<CardDescription>Your sales tax, ready to file.</CardDescription>
</CardHeader>
<CardContent className="flex flex-col gap-3 text-sm">
<div className="flex items-center justify-between">
<span className="text-muted-foreground">Revenue</span>
<span className="font-mono tabular-nums">$12,480.00</span>
</div>
<div className="flex items-center justify-between">
<span className="text-muted-foreground">Expenses</span>
<span className="font-mono tabular-nums">$4,120.50</span>
</div>
<Separator />
<div className="flex items-center justify-between font-medium">
<span>Sales tax due</span>
<span className="font-mono tabular-nums">$1,408.00</span>
</div>
</CardContent>
<CardFooter className="text-xs text-muted-foreground">
Example data. Your numbers stay with you.
</CardFooter>
</Card>
</section>
<section id="features" className="flex flex-col gap-8">
<div className="max-w-2xl">
<h2 className="text-3xl font-semibold tracking-tight">
Three steps, not a spreadsheet
</h2>
<p className="mt-3 text-muted-foreground">
The flow fits in three screens. Each block below is a component you
can delete or reorder.
</p>
</div>
<div className="grid gap-4 md:grid-cols-3">
{features.map((feature) => (
<Card key={feature.title}>
<CardHeader>
<CardTitle>{feature.title}</CardTitle>
<CardDescription>{feature.description}</CardDescription>
</CardHeader>
<CardContent className="text-sm text-muted-foreground">
{feature.detail}
</CardContent>
</Card>
))}
</div>
</section>
<section id="pricing" className="flex flex-col gap-8">
<div className="max-w-2xl">
<h2 className="text-3xl font-semibold tracking-tight">
One price, not a quote
</h2>
<p className="mt-3 text-muted-foreground">
Two plans, no hidden fees. The button opens your checkout page.
</p>
</div>
<div className="grid gap-4 md:grid-cols-2">
{plans.map((plan) => (
<Card
key={plan.name}
className={plan.featured ? "ring-2 ring-primary" : undefined}
>
<CardHeader>
<CardTitle>{plan.name}</CardTitle>
<CardDescription>{plan.description}</CardDescription>
{plan.featured && (
<CardAction>
<Badge>Popular</Badge>
</CardAction>
)}
</CardHeader>
<CardContent className="flex flex-col gap-3">
<p className="text-4xl font-semibold tracking-tight">
{plan.price}
<span className="text-base font-normal text-muted-foreground">
{plan.period}
</span>
</p>
<ul className="flex flex-col gap-2 text-sm text-muted-foreground">
{plan.features.map((item) => (
<li key={item} className="flex gap-2">
<span aria-hidden className="text-foreground">
✓
</span>
{item}
</li>
))}
</ul>
</CardContent>
<CardFooter>
<a
className={buttonVariants({
variant: plan.featured ? "default" : "outline",
})}
href="#contact"
>
Choose {plan.name}
</a>
</CardFooter>
</Card>
))}
</div>
</section>
<section id="faq" className="grid gap-8 lg:grid-cols-[0.8fr_1.2fr]">
<div>
<h2 className="text-3xl font-semibold tracking-tight">
The questions that block the sale
</h2>
<p className="mt-3 text-muted-foreground">
A short answer, then a link to the documentation.
</p>
</div>
<Accordion defaultValue={["faq-1"]}>
<AccordionItem value="faq-1">
<AccordionTrigger>
Does my data go through your servers?
</AccordionTrigger>
<AccordionContent>
Processing happens in your browser. The server only receives your
email address if you create an account.
</AccordionContent>
</AccordionItem>
<AccordionItem value="faq-2">
<AccordionTrigger>Can I cancel anytime?</AccordionTrigger>
<AccordionContent>
Yes. The subscription stops at the end of the current month, with
no cancellation fee.
</AccordionContent>
</AccordionItem>
<AccordionItem value="faq-3">
<AccordionTrigger>Which export formats do you accept?</AccordionTrigger>
<AccordionContent>
CSV, OFX and PDF. The generic CSV path covers most banks.
</AccordionContent>
</AccordionItem>
</Accordion>
</section>
<section
id="contact"
className="rounded-2xl border bg-card px-6 py-12 text-center"
>
<h2 className="text-3xl font-semibold tracking-tight">
Try it on your own exports
</h2>
<p className="mx-auto mt-3 max-w-xl text-muted-foreground">
Leave your email and we send a login link. No password.
</p>
<form className="mx-auto mt-6 flex max-w-md flex-col gap-3 sm:flex-row">
<Input
type="email"
required
placeholder="[email protected]"
aria-label="Email address"
/>
<Button type="submit">Get the link</Button>
</form>
</section>
<footer className="flex flex-col gap-3 border-t pt-6 text-sm text-muted-foreground sm:flex-row sm:items-center sm:justify-between">
<p>Acme — sample landing page.</p>
<p>Legal · Privacy</p>
</footer>
</main>
)
}What this code does:
- The
headerandfooterare native HTML: a short landing page does not need a component for them. - The hero uses
Badgefor the announcement, twobuttonVariantsfor the actions and aCardfor the proof. - Features and pricing are
Cardcomponents in a CSS grid.CardActionplaces the “Popular” badge without absolute positioning. - The FAQ uses
Accordion, an interactive component; the rest of the page can stay a Server Component. - The form uses
InputandButton. Connectactionto your endpoint or email provider before going live.
The code depends on no images. A landing page without visuals works when the headline and the proof are concrete; add a screenshot later, when the product has a screen worth showing.
Step 3: change the theme, not the components#
Components read semantic tokens: background, foreground, primary, muted, border, ring. These tokens live in app/globals.css, under :root and .dark. Change --primary and --radius, and every button, badge and card follows. That is the strength of the model: you do not override each component.
:root {
--primary: oklch(0.52 0.17 255);
--primary-foreground: oklch(0.985 0 0);
--radius: 0.75rem;
}For a full theme, shadcn/create generates a visual preset (colors, radius, fonts, icons) and an init command. You can also apply an existing preset with npx shadcn@latest apply <code>, or only the theme with --only theme. npx shadcn@latest preset resolve prints the current project preset.
Dark mode is not automatic: it needs a .dark class on <html>. The Dark Mode documentation provides the provider and the toggle. For a landing page, one button in the header is enough; do not block the first paint with a flash of the light theme.
One detail matters: shadcn/ui components are copied into your repository. There is no npm update for them. When you edit button.tsx, the change stays. When the upstream registry changes, you decide whether to reapply it. That is the trade of the model, and it belongs in the budget.
Step 4: add social proof and logos#
A landing page without proof looks like a poster. Add either a logo row or a testimonial, not both. If you have customers, their logos are enough. If you do not, use a quote from a tester, a verifiable number or a screenshot of a result.
For logos, Logoforge offers 1,019 SVG logos of developer tools, free and open source, as SVGs, React components or a shadcn registry. This command writes a typed component into components/logos:
npx shadcn@latest add @logoforge/vercelimport { VercelLogo } from "@/components/logos/vercel"
export function LogoRow() {
return (
<div className="flex flex-wrap items-center justify-center gap-8 opacity-70">
<VercelLogo variant="mono" className="h-6 w-auto" />
</div>
)
}Check trademark rules before displaying a customer logo. A logo in a “trusted by” row implies a real relationship; do not use a logo found on a website as proof.
If you prefer a ready-made block, shadcn/ui block catalogs often include a “logos” or “testimonials” section. That is where the time saving is real: layout, responsiveness and dark mode are already handled. Check the license and the target version before buying.
Step 5: FAQ, form and footer#
The FAQ answers objections, not questions nobody asks. Three to five questions are enough: price, data, timing, cancellation. The Accordion component keeps answers in the HTML, so search engines can read them without a click.
The closing form must make a precise promise: “Get the login link”, “Download the checklist”, “Book a call”. Avoid “Learn more”. One email field and one button are enough to start. Add confirmation, duplicate handling and unsubscribe next.
The footer holds legal links, contact information and one sentence that says what the product does. No 30-link column on a six-section landing page. Add a blog, a pricing page and a security page when the product has them.
Test and deploy#
Before deploying, run the production build:
npm run build
npm run startOpen http://localhost:3000 and test with the keyboard: the hero button, both pricing cards, the accordion and the email field. Check the layout at 360 px, 768 px and 1440 px. A landing page broken on mobile loses more conversions than an average headline.
For hosting, Vercel is the shortest path for a static Next.js page. If you already run a VPS, our step-by-step Coolify tutorial covers the Dockerfile, the domain and HTTPS. Our Vercel vs Cloudflare vs Coolify comparison puts numbers on the three options. A landing page without a database deploys well as a static site, but forms need an endpoint or an email service.
Then measure: one event on the main button click, another on form submission. Without measurement, you will not know whether the 10 minutes did anything.
Pitfalls that cost an evening#
- Tailwind 3 instead of 4. Current shadcn/ui targets Tailwind 4. A Tailwind 3 project needs a migration or an older set of components. Check
package.jsonbeforeinit. - A
components.jsonin the wrong folder. The CLI reads that file to know where to write. In a monorepo, run the command from the workspace or pass-c apps/web. - A
Buttonused as a link. The Base UI documentation advises against<Button render={<a />}>: thebuttonrole overrides the link role. UsebuttonVariantson an<a>tag. - An accordion without a
value. EveryAccordionItemneeds a unique value. Without it, the component cannot tell which panel to open. - A theme edited inside a component. If you change
button.tsxfor a color, you will repeat the edit on every update. Change the--primarytoken inglobals.css. - A 4 MB image in the hero. A fast landing page is a landing page that loads. Compress to WebP and use
next/image.
Should you buy blocks?#
For a six-section page, no. The code above fits in one file and you understand it. For a 10-page marketing site with hero, bento, pricing, testimonials, blog, contact and footer, a catalog can save a day of layout work. Compare the price with your billable time: $99 for 170+ blocks is less than two hours at $50/h, but only if the blocks match your design and your shadcn/ui version.
Check three things before buying: the license (commercial projects, number of seats), the target shadcn/ui and Tailwind version, and how easy customization is. A block that forces you to override 40 classes does not save time. A block that uses the same tokens as your project does.
If you are choosing between shadcn/ui and a full component library, our shadcn/ui vs Mantine vs Chakra UI comparison covers the three models. For a landing page, shadcn/ui remains the right choice when you already use Tailwind and want to keep control of the code.
Frequently asked questions#
Frequently asked questions
Can you really build a landing page in 10 minutes?
Yes, for the page itself, if Next.js, Tailwind and shadcn/ui are already installed. create-next-app, shadcn init and dependency installation take another 10 to 15 minutes depending on your connection. From zero, budget 20 to 25 minutes.
Do I need Tailwind CSS to use shadcn/ui?
Yes. The installation requires Tailwind CSS and an import alias. Components use Tailwind classes and CSS variables for theming. If you do not want Tailwind, a library such as Mantine is more direct because it works with CSS Modules and a PostCSS preset.
Does shadcn/ui ship landing page blocks?
Not directly. The official Blocks page highlights application screens: dashboard, sidebar, login and signup. For a landing page you compose sections from components (Button, Card, Badge, Accordion, Input, Separator) or use a third-party catalog built on shadcn/ui.
Are shadcn/ui blocks free?
The official components and blocks are free and open source; the Blocks page says “Free forever. Open Source.” Third-party catalogs may be paid: Blockforge lists $99 for the Solo license (list price $159) and $299 for the Team license (list price $449), as a one-time payment. Always check the license before buying.
How do I change colors and dark mode?
Edit the tokens in app/globals.css, under :root and .dark. --primary, --background, --foreground, --border and --radius cover most of the work. For dark mode, add the .dark class on <html> with the provider from the Dark Mode documentation. Avoid editing each component: you would lose the point of the tokens.
What if npx shadcn@latest init fails?
npx shadcn@latest init fails?Check Node.js first: the 4.23.0 CLI requires version 20.18.1 or newer. Then check that components.json is not already present in another folder and that Tailwind 4 is configured. In a monorepo, run the command from the right workspace or pass -c apps/web. npx shadcn@latest info prints the detected configuration.
Sources#
Official pages, repositories and npm registries checked on November 6, 2026. Versions and prices were checked in November 2026; prices are in US dollars before tax where stated.
- shadcn/ui — introduction
- shadcn/ui — Next.js installation
- shadcn/ui — CLI
- shadcn/ui — Blocks
- shadcn/ui — components
- shadcn/ui — theming and tokens
- shadcn/ui — Button
- shadcn/ui — Card
- shadcn/ui — Badge
- shadcn/ui — Accordion
- shadcn/ui — Separator
- shadcn/ui — Input
- shadcn/ui — Base UI as the default (July 2026)
- GitHub repository shadcn-ui/ui
- npm — shadcn 4.23.0
- npm — next 16.4.5
- npm — tailwindcss 4.3.5
- npm — react 19.3.1
- Next.js — installation and create-next-app
- Blockforge — pricing
- Blockforge — shadcn/ui and Tailwind blocks
- Logoforge — SVG logos and shadcn registry



Comments
Loading comments…