Landing page + content site
SaaS landing, agency one-pager, indie project site. Hero, features, testimonials, FAQ, blog, and legal routes already wired.
Starter
SaaSForge Starter
The minimal Next.js 16 + Tailwind v4 site starter
The fastest way into a new Next.js project. Next.js 16 App Router, React 19, TypeScript 5.9, Tailwind v4, shadcn/ui, MDX content, next-themes dark mode, a full SEO surface (metadata, OG images, sitemap, RSS, JSON-LD), and Supabase Auth out of the box (magic-link email + Google OAuth, protected /dashboard, sign-out). Bring your own database schema and billing when your product calls for them.
$59$99
Launch pricing · One-time purchase · Full source codeSecure checkout by Polar (Merchant of Record) · Taxes calculated at checkout · Refund Policy
What buyers check before picking a minimal Next.js 16 starter
- Next.js App Router
- TypeScript strict
- Tailwind v4 oklch
- shadcn/ui + Radix
- MDX content
- Vercel-ready
Next.js 16
App Router + React 19
9 MDX docs
Setup, theme, content, SEO, deploy
Under 6k LOC
Small, readable, no lock-in
What you'll build
Three concrete products you can ship on this template without touching the plumbing.
Personal portfolio with blog
Portfolio, blog with MDX, and docs to showcase your work. Custom theme in oklch, dark mode, fast SEO.
Documentation site
OSS project or internal tool docs. Drop MDX files in content/docs/, register in config, and ship.
Why buyers pick this minimal Next.js 16 starter
Landing page, MDX blog, MDX docs, oklch theme tokens, shadcn/ui, dark mode, and SEO are wired in without the lock-in of a prescribed auth, database, or billing stack. Ship day one with a polished shell you can rebrand in an afternoon.
A polished landing page on day one
Hero, features grid, process, integrations band, testimonials, FAQ, and CTA are all driven by typed config. Rebrand the whole site in one afternoon, not one week. No half-finished marketing sections pretending to be filler.
Get instant accessIncluded in this template
- Hero with stats, CTA buttons, and trust logos band
- Features grid with icon tiles and call-to-action footer
- How-it-works process, integrations, testimonials, FAQ, CTA
- Typed section configs: TypeScript catches broken fields
- Dark mode and responsive layouts out of the box
- Three-locale ready via the existing next-intl patterns in sibling products
MDX blog + MDX docs with SEO baked in
Content is just `.mdx` files in `content/blogs/` and `content/docs/`. The renderer handles breadcrumbs, JSON-LD schemas, canonical URLs, RSS, and sitemap entries. No CMS, no vendor coupling, git-versioned like code.
Browse documentationIncluded in this template
- Blog post MDX with frontmatter: GFM tables, code blocks, JSX
- Docs tree with typed categories and auto-generated sidebar
- Per-page OG metadata, canonical URLs, BlogPosting / TechArticle schemas
- Ships 9 example docs you can delete, keep, or edit in place
- RSS 2.0 feed at /rss.xml and full sitemap.xml
- JSON-LD: Organization, WebSite, BlogPosting, TechArticle, BreadcrumbList
Theme system built on oklch + CSS variables
Every color, font, radius, and shadow lives as a CSS custom property in globals.css. Change --primary once and every button, badge, and focus ring updates. Dark mode is a `.dark {}` override, not a pile of JS theme objects to maintain.
Read the theme system docsIncluded in this template
- oklch tokens for perceptually uniform color
- Semantic scales: primary, secondary, accent, muted, destructive, success, warning, info
- Light + dark palettes defined in one file each
- Typography: Montserrat / Merriweather / Source Code Pro via next/font
- 8px spacing grid and six shadow tiers
- next-themes wired with system / light / dark toggle
Config-first: rebrand without grepping
Product name, emails, social links, nav items, footer groups, and per-section copy all live in typed config files under src/config/. TypeScript errors if you break a field. No chasing literals across 40 components.
Read the customization docsIncluded in this template
- src/config/brand.ts: product name, company, emails, socials
- src/config/marketing-copy.ts: SEO titles, descriptions, OG copy
- src/config/ui/*.ts: per-section copy (hero, features, FAQ, CTA, ...)
- src/config/routes.ts: centralized URL constants
- src/config/seo.ts: per-route SEO metadata
- All configs strictly typed so rebrand edits are refactor-safe
Deploys on Vercel in under 5 minutes
Zero-config Vercel deploy. One required env (`NEXT_PUBLIC_APP_URL`), fully static where possible, ISR on blog and docs (1-hour revalidation). Static export mode is one line in next.config.ts if you need S3 or Cloudflare Pages.
Read the deployment guideIncluded in this template
- One-command git push → Vercel auto-detects Next.js and deploys
- Pre-rendered home, blog list, docs list, and legal pages
- ISR on blog posts and doc pages: update MDX without full rebuilds
- next/font preloads + font-display: swap to prevent FOIT
- Edge-runtime OG image via next/og, lazy-loaded where possible
- Optional: flip output: 'export' for fully static hosting
Zero lock-in: bring your own auth, DB, and billing
The starter has no opinions on auth or billing. Supabase, Clerk, Auth.js all drop in cleanly. Postgres, SQLite, Prisma, Drizzle: pick one. Stripe, Polar, Lemon Squeezy: wire when you launch. When you need an opinionated full stack, upgrade to SaaSForge Core.
Buy template (one-time license)Included in this template
- Nothing vendor-locked; every integration layer is your choice
- Cleanly upgradeable to SaaSForge Core (same design system, with auth + billing)
- Under 6k LOC of app code, auditable in an afternoon
- Pairs with a free minimal starter as a top-of-funnel lead magnet
- Small enough to read end-to-end before you commit
- Big enough to ship a polished site the day you clone it
FAQ
Questions we get before someone buys a template
Not quite right?
Ready for auth, workspaces, and Stripe billing? Upgrade to SaaSForge Core for the same design system and a full multi-tenant stack.
Ready to Ship?
Start Building with SaaSForge Starter Today
Get the complete source code and launch your landing page, blog, and docs in minutes, not weeks.