Free And Open Source
The Next.js landing page starter
with a robust foundation to build on.
A free landing page starter on Next.js 16, shadcn/ui and Base UI. Static pages, complete SEO, accessible sections, preset theming and a full test suite come set up, so you start on the words, not the plumbing.
git clone https://github.com/7ovr/Built on the stack you already use
- Next.js
- React
- TypeScript
- Tailwind CSS
- shadcn/ui
- Base UI
- Vercel
- Vitest
- Playwright
- Lighthouse
- pnpm
- Node.js
- Oxc
- Lefthook
- Lucide
Everything Already Wired
Everything A Landing Page Needs, Already Done
Speed, search, accessibility, design and tests are handled from the first commit, and CI keeps each of them true after you make the site your own.
Static And Fast By Default
Every route prerenders to static HTML at build time. A dynamic API anywhere fails the build, and Lighthouse budgets in CI keep every page fast.
Complete SEO On Every Page
One helper writes the title, canonical and Open Graph card of every page, with JSON-LD and a sitemap beside it, so no page ships half a head.
Tested On Every Push
Vitest, Playwright and Lighthouse run in CI beside lint, format and type checks, so what works today keeps working.
Accessible By Default
One h1 per page, a skip link, visible focus and reduced motion, and every section stays readable with JavaScript off.
Every Word In One Place
All the copy lives in typed files under
src/content/, one per section, so a new headline never means touching a component.One Preset Restyles It All
Colors, radius and fonts come from shadcn theme tokens, so
shadcn applyrestyles every section, in light and dark.
Share Cards For Every Page
Open Graph images drawn at build time in your theme's colors.
Dark Mode Without A Flash
Light, dark and system themes, set before the first paint.
Guarded Commits
Git hooks format and lint staged files on every commit.
Clone-Safe URLs
A fresh deploy points its canonicals at its own domain.
From Clone To Indexed
Make It Yours In Four Steps
The starter does the plumbing once, so a new site is a config file, a content folder and a deploy. Any of the 540+ 7Ovr blocks installs straight into it.
Clone The Starter
Use the GitHub template or clone the repository, then run
pnpm install.Make It Yours
Set the name and links in
src/config/site.ts, and the copy insrc/content/, one file per section.Restyle With A Preset
Build a preset on ui.shadcn.com/create and apply its code. Every section follows the new tokens.
Deploy And Get Found
Deploy to Vercel. The site URL resolves from the deployment, so canonicals, the sitemap and JSON-LD point at your domain.
Built For Coding Agents
Your Agent Already Knows The Rules
Claude Code, Codex and Cursor read the same conventions, so a page they add is prerendered, complete and tested like the rest.
One Rulebook
CLAUDE.mdholds every convention, from content files to motion, andAGENTS.mdpoints every other agent to it.Checks That Catch Drift
Lint and format run on every commit and the full suite on every push, so a slip fails fast.
The Same Gate In CI
Every pull request runs the full suite before it can merge, whoever or whatever wrote it.
Also From 7Ovr, The Vite Starter
Building The App Behind Your Landing Page?
Give it a modern frontend from the 7Ovr Vite Starter: a free React starter on the same shadcn/ui and Base UI stack, with TanStack Router, Query, Form and Table and strict TypeScript already wired.
- One preset styles the app and its landing page alike
- Routing, data, forms and tables wired and tested
- Free, MIT licensed and ready for any backend
Before You Clone It
Questions & Answers
What ships in the starter, what it costs, and how it fits your stack.
Still have a question?
Ask On GitHubA free, open-source Next.js 16 starter for landing pages, built on shadcn/ui and Base UI. Every page is prerendered, and every promise it makes, from SEO to accessibility, is covered by a test.
Yes. It is MIT licensed, so you can use it for client work and commercial products, and you owe nothing back. The Pro blocks and templates on 7Ovr are optional and separate.
Node 24 or newer and pnpm 12 or newer. There is no global CLI to install and no account to create.
Each promise has a test: metadata and JSON-LD on every route, one h1 and working landmarks, readable HTML with JavaScript off, Lighthouse budgets, and noindex on preview deploys. CI runs them on every push, beside lint, format and type checks.
Yes. Every section and every FAQ answer is in the server-rendered HTML. JavaScript only adds the theme toggle, the mobile menu, the copy button and the FAQ accordion.
Site-wide details live in src/config/site.ts, and the copy lives in src/content/, one file per section. The sections only render what they are given.
No. It is a marketing site with no server code of its own. For an app, pair it with the 7Ovr Vite Starter; for a form or analytics, add your own.
Build a preset on ui.shadcn.com/create and run pnpm exec shadcn apply <code>. Colors, radius and fonts all come from shadcn theme tokens, so every section follows.
Yes. It is a standard shadcn/ui project, so all 540+ blocks install straight into it, source included: free ones with pnpm exec shadcn add @7ovr/<name>, Pro ones from @7ovr-pro with a license key.
Yes. CLAUDE.md holds every convention and AGENTS.md points to it, so Claude Code, Codex and Cursor keep new pages and sections on the same patterns.
Vercel works with no setup. It is a standard Next.js app, so any host that runs next start works too; there, set SITE_URL and SITE_ENV=production before you build, so canonicals and indexing are right.
It is source you own, so nothing updates behind your back. Renovate keeps the dependencies current, and you pull in the upstream changes you want.
Open Source, MIT Licensed
Start On The Words, Not The Setup
Clone the starter, make the words yours and deploy. Speed, SEO, accessibility and theming are already done, and the tests keep them that way.