Skip to content
Launch price · $99 instead of $129
Shadcn Pages

Documentation

Short chapters, from the first install to updates.

01 / 07

Getting started

Open a template, install, run.

Each template is a standalone Next.js project in its own folder. Nothing is shared between them, so you can copy one folder out of the pack and it keeps working.

Requirements

  • Node.js 20.9 or newer
  • pnpm (recommended), npm, yarn or bun
  • Any editor; an AI coding assistant is optional

Install and run

From the template's folder, install the dependencies and start the development server on http://localhost:3000.

pnpm install
pnpm dev

Before you deploy, run the type check and a production build. Both must finish without errors.

bash
pnpm typecheck   # tsc --noEmit
pnpm build       # production build
pnpm start       # serve the build
Start with the template's README.md: it lists every route of that site and where its pieces live.

02 / 07

Project structure

Where pages, components and content live.

Every template follows the same layout, so once you know one you know them all.

text
app/
  layout.tsx           fonts, root metadata, the theme script
  globals.css          every design token, light and dark
  (site)/              pages inside the header and footer
  (auth)/              /login and /signup in a minimal shell
  not-found.tsx        the designed 404
  sitemap.ts  robots.ts  opengraph-image.tsx  icon.svg
components/
  ui/                  small primitives: button, field, tabs, prose…
  site/                header, mobile menu, footer, logo, CTA band
  <page>/              pieces used by one page (home/, pricing/, blog/…)
content/               every word and number, as typed TypeScript
lib/                   cn(), formatters, validation
ai/                    the AI customisation kit
AGENTS.md  CLAUDE.md   entry points for coding agents
README.md  LICENSE.md  vercel.json

Pages are Server Components. Only the interactive leaves (demos, filters, forms, menus) are client components, and they receive their data from content/ as props.

03 / 07

Theming

Colours, fonts, radii and the dark theme.

Every colour, font, radius, shadow and easing is a token in app/globals.css, declared inside @theme and used as a Tailwind utility (bg-ink, font-display, rounded-card). Components contain no hex values, so changing a token changes the whole site.

app/globals.css
@theme {
  --color-bg: #f7f8f6;      /* page */
  --color-ink: #0e1a16;     /* text, solid buttons */
  --color-accent: #1e5b45;  /* links, focus, positive values */
}

.dark {
  --color-bg: #0c1512;
  --color-ink: #e8efea;
  --color-accent: #5fbf98;
}

Dark mode

The dark theme is class-based: an inline script in app/layout.tsx puts .dark on <html> before the first paint, following the system setting until the visitor picks a theme with the toggle. Change a token in both places to keep the themes in step.

Fonts

Fonts are local woff2 files in app/fonts, loaded with next/font/local, with their licence next to them. To swap one, drop the new file in app/fonts, point the loader in app/layout.tsx at it and keep the CSS variable name.

04 / 07

Content

Change the words without touching the layout.

Copy and data live in content/ as typed modules: navigation, plans, posts, customers, FAQs, team, legal clauses. TypeScript tells you when a field is missing, and every list on the site renders from these files.

FileWhat it holds
content/site.tsName, URL, navigation, footer, the template credit, SEO keywords
content/pricing.tsPlans, comparison rows, add-ons, pricing questions
content/posts.ts or journal.tsLong-form articles as typed blocks
content/legal.tsNumbered clauses and their plain-language summaries

site.url drives canonical URLs, the sitemap, Open Graph images and the AI summary links. Set it to your domain first.

content/site.ts
export const site = {
  name: "Your company",
  url: "https://example.com",
  template: null, // removes "A Shadcn Pages template" from the footer
};

Long-form pages (articles, case studies, legal) are arrays of blocks such as p, h2, list, quote, figure, table and callout, rendered by one component. No MDX dependency.

05 / 07

Deployment on Vercel

One project per template folder.

  1. Push the template folder to a Git repository, alone or next to other templates.
  2. On Vercel, import the repository and set Root Directory to the template's folder (landing-pages/<name> in the pack).
  3. Keep the detected framework (Next.js) and the default build command.
  4. Add your domain, then set the same address as site.url in content/site.ts.

Each template ships this vercel.json. Its ignoreCommand skips the build when nothing changed inside that folder since the last deployment, so templates sharing one repository do not rebuild each other.

vercel.json
{
  "$schema": "https://openapi.vercel.sh/vercel.json",
  "ignoreCommand": "P=\"$VERCEL_GIT_PREVIOUS_SHA\"; [ -n \"$P\" ] || exit 1; git cat-file -e \"$P^{commit}\" 2>/dev/null || git fetch -q --depth=1 origin \"$P\" 2>/dev/null || exit 1; git diff --quiet \"$P\" HEAD -- ."
}
Every route is static by default. Any host that runs Next.js works too: Netlify, Cloudflare, a Node server with pnpm build && pnpm start.

06 / 07

The AI customisation kit

Re-brand a template with your coding assistant.

Every template has an ai/ folder written after the code, from the code. Your assistant reads it to understand the template before it changes anything.

FileWhat it is
ai/README.mdHow to use the kit
ai/CUSTOMIZE.mdThe playbook: brand questions first, ordered steps with file paths, final checks
ai/CONTENT-MAP.mdRoute → page file → content files → main components
ai/DESIGN-SYSTEM.mdTokens, type roles, the owned visual idea, motion, voice, component props
ai/PROMPTS.mdReady prompts: re-brand, colours, fonts, pricing, pages, forms, auth, launch
  1. Open the template in Claude Code, Cursor, Copilot or a similar assistant.
  2. Ask it to read AGENTS.md and ai/CUSTOMIZE.md.
  3. Paste a prompt from ai/PROMPTS.md and answer its questions.
text
Read AGENTS.md and ai/CUSTOMIZE.md. Then re-brand this site for my company:
name, one-line pitch, audience and colours below. Keep the art direction,
change tokens in app/globals.css for both themes, and run pnpm typecheck
and pnpm build when you are done.

CLAUDE.md contains one line, @AGENTS.md, so Claude Code loads the brief automatically.

07 / 07

Updates

What changes and how to bring it in.

Updates are free for life, and so are the templates added to the pack later. Every release is listed on the changelog, template by template, with the files it touches.

  • Keep your edits in content/ and in the tokens where you can: those files rarely change in an update.
  • Commit the template as you received it before customising it, so an update is a diff you can read.
  • Framework upgrades note the commands to run and anything you need to check.

A step missing? Tell us and it goes into the next release.