Next.jsReactStarter

nextjs-boilerplate — Next.js Starter Template

By savantly-net

Savantly Next.js boilerplate project, based on Next.js 14 App Router, React 18, TypeScript, and Tailwind CSS 3, with built-in slug routing, component directory, Jest, ESLint, Prettier, Husky, and other development tooling, and recommends using Flowbite React components.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

2 previews
Desktop homepage1 / 2
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 2

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-14View source

What stands out

A quick read of the recorded project description.

01

Based on Next.js 14 App Router, React 18, TypeScript, and Tailwind CSS 3

02

Built-in slug-style routing; visiting /some-page loads src/app/[slug]/page.tsx and passes the slug as a prop

03

UI components are located in src/components, and using Flowbite React components is recommended

04

Integrates Jest, ESLint (including automatic import sorting), Prettier, Husky, and Lint Staged

05

Uses the Conventional Commits specification and is configured with Release Please and GitHub Actions

06

Provides Open Graph helper functions and automatic generation of sitemap.xml

Template Details

This template is a Next.js project starter boilerplate. The README states that it encourages using pnpm to install dependencies so that Husky hooks work properly. During development, run pnpm dev and open http://localhost:3000 in the browser. You can edit src/pages/index.tsx to start modifying pages, and the page will update automatically after the file is saved. The template is configured with simple slug-style routing; for example, visiting /some-page loads src/app/[slug]/page.tsx and passes the slug value as a prop. UI components are located in the src/components directory. The README recommends using Flowbite React components as much as possible and encourages contributing reusable components to the nexus-ui-components library. Commit messages must follow the Conventional Commits specification.

The features listed in the README include: Next.js 14 with App Router, React 18, TypeScript, Tailwind CSS 3 (extending the primary color via CSS variables), prebuilt components, Jest unit testing, absolute imports and path aliases (with the @/ prefix), ESLint (including automatic import sorting), Prettier, Husky and Lint Staged, Conventional Commit Lint, Release Please, GitHub Actions code checks, automatic branch and issue linking, a collection of code snippets, Open Graph helper functions, automatic generation of sitemap.xml, and an extension pack that can install commonly used libraries and configurations. The template was initially bootstrapped from ts-nextjs-tailwind-starter.

The README does not provide specific instructions on deployment steps, environment variables, databases, or backend integration; the preview screenshots only prove that actual page screenshots exist, not that the pages function.

Next.jsStarter

Is it right for your project?

Use Cases

  • Quickly starting a new project that uses Next.js 14 App Router and TypeScript
  • Wanting the project to come with code standard tools such as ESLint, Prettier, Husky, and Conventional Commits
  • Needing a simple routing structure that dynamically loads different pages or components based on slugs
  • Planning to build the interface using the Flowbite React component library
  • Wanting to contribute reusable UI components to the nexus-ui-components library

Suitable For

  • Front-end developers familiar with Next.js, TypeScript, and Tailwind CSS
  • Teams that need to standardize commit messages and code checking processes
  • Projects that want to use pnpm as the package manager
  • Developers who need to start building a project from an existing boilerplate rather than configuring from scratch

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    It is recommended to use pnpm to install dependencies so that Husky hooks work properly: pnpm install

  2. 2

    Run pnpm dev to start the development server; the default address is http://localhost:3000

  3. 3

    You can edit src/pages/index.tsx to start modifying pages, and it updates automatically after saving

  4. 4

    Commit messages must follow the Conventional Commits specification

  5. 5

    The README does not provide specific instructions on deployment steps, environment variables, or backend integration

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version under the Apache-2.0 license in the public repository; the free scope is the code of that version and does not mean that external services or third-party materials are free.

Must comply with when using

  • Free use, modification, commercial use, and distribution are permitted; when distributing, the Apache-2.0 license must be included.
  • Modified files must be prominently marked as changed, and relevant copyright, patent, trademark, and attribution notices must be retained.
  • If the original project includes a NOTICE file, applicable attribution notices in it must be retained when distributing derivative works.
  • The license includes an applicable contributor patent grant; initiating patent litigation as described in the license terminates that patent grant, and no trademark use rights are granted.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • Demo images, fonts, icons, and other third-party materials must be checked against their respective licenses and cannot be judged solely by the code's Apache-2.0 license.
  • External services such as domains, hosting, databases, payments, or AI may incur additional charges.
  • It is recommended to use pnpm to install dependencies so that Husky hooks work properly; using other package managers may cause the hooks to fail to run properly.
  • When committing changes, the Conventional Commits specification must be followed; this is a mandatory requirement.
  • It is recommended to use Flowbite React components for development as much as possible.
  • Contributing reusable UI components to the nexus-ui-components library is encouraged.
View Original Text Basis

no-charge, royalty-free, irrevocable copyright license

Original License Text

It is encouraged to use **pnpm** so the husky hooks can work properly.

Original README

This starter is using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), it is mandatory to use it to commit changes.

Original README

Use the Flowbite React components when possible.

Original README

If you feel compelled, please contribute your reusable components to the nexus-ui-components library.

Original README
https://github.com/savantly-net/nextjs-boilerplate/blob/main/LICENSEhttps://github.com/savantly-net/nextjs-boilerplate/blob/main/README.md

Compiled by DeepSeek based on repository license and README ·2026-10-14. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
Partly documented · 68 / 100
Technologies
Next.js · React
Website type
Starter
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2024-04-12
Screenshot last checked
2026-10-14

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Next.js as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Review declaration: codex-user-requested-batch-review-20261015 · 2026-10-15

Inspect the recorded source material

SHA-256: 6f4192deb21db22de17984b58c1c248d2d3e4cb182d158639496c177388f72fe

2026-10-14T00:07:55.207Z

Source file / repository
# Savantly Next JS Boilerplate

## Quick start

### 1. Install dependencies

It is encouraged to use **pnpm** so the husky hooks can work properly.

```bash
pnpm install
```

### 2. Run the development server

You can start the server using this command:

```bash
pnpm dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result. You can start editing the page by modifying `src/pages/index.tsx`.

The page will automatically update as you edit the file.

Use the Flowbite React components when possible.

[https://www.flowbite-react.com/](https://www.flowbite-react.com/)

A simple `slug` style routing is configured so you can easily load different components/pages based on the slug value in the url.

For example -  
`http://localhost:3000/some-page` will load the `src/app/[slug]/page.tsx` file, with the slug value available as a prop.

### 3. Commit Message Convention

This starter is using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), it is mandatory to use it to commit changes.

### 4. Contribute to UI Components

The UI components are located in the `src/components` directory.  
If you feel compelled, please contribute your reusable components to the nexus-ui-components library.

https://nexus-ui-components.vercel.app/

### Originally bootrapped from ...

ts-nextjs-tailwind-starter

#### Features

This repository is 🔋 battery packed with:

- ⚡️ Next.js 14 with App Router
- ⚛️ React 18
- ✨ TypeScript
- 💨 Tailwind CSS 3 — Configured with CSS Variables to extend the **primary** color
- 💎 Pre-built Components — Components that will **automatically adapt** with your brand color, [check here for the demo](https://tsnext-tw.thcl.dev/components)
- 🃏 Jest — Configured for unit testing
- 📈 Absolute Import and Path Alias — Import components using `@/` prefix
- 📏 ESLint — Find and fix problems in your code, also will **auto sort** your imports
- 💖 Prettier — Format your code consistently
- 🐶 Husky & Lint Staged — Run scripts on your staged files before they are committed
- 🤖 Conventional Commit Lint — Make sure you & your teammates follow conventional commit
- ⏰ Release Please — Generate your changelog by activating the `release-please` workflow
- 👷 Github Actions — Lint your code on PR
- 🚘 Automatic Branch and Issue Autolink — Branch will be automatically created on issue **assign**, and auto linked on PR
- 🔥 Snippets — A collection of useful snippets
- 👀 Open Graph Helper Function — Awesome open graph generated using [og](https://github.com/theodorusclarence/og), fork it and deploy!
- 🗺 Site Map — Automatically generate sitemap.xml
- 📦 Expansion Pack — Easily install common libraries, additional components, and configs.

See the 👉 [feature details and changelog](https://github.com/theodorusclarence/ts-nextjs-tailwind-starter/blob/main/CHANGELOG.md) 👈 for more.
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.