Install and run — KorDent Next.js
KorDent runs on Node.js with the usual Next.js commands: install the packages once, then start the development server and edit while the page updates by itself.
What you need
Section titled “What you need”| Node.js | 20.9 or newer (node -v). Download at https://nodejs.org — the LTS build is fine. |
| A package manager | npm comes with Node. pnpm, yarn and bun work too. |
| A code editor | VS Code is a good default; any editor works. |
| A browser | Chrome, Edge, Firefox or Safari. |
| An internet connection | The font Inter is downloaded from Google Fonts when the site builds, and the first time npm run dev runs. The site then serves it from your own domain. |
No database, no account, no paid service. Every page is pre-rendered; only the four forms run on the server.
Install
Section titled “Install”Unzip the template, open the folder in a terminal and run:
npm installThis downloads the packages listed in package.json into node_modules/. It takes a few minutes the first time.
npm run devOpen http://localhost:3000. Save a file and the page updates by itself.
The commands
Section titled “The commands”| Command | What it does |
|---|---|
npm run dev |
Development server with live reload |
npm run build |
Production build — every page is pre-rendered as HTML, and the types are checked |
npm start |
Serves the production build locally (run build first) |
npm run lint |
Checks the code with ESLint. npm run build doesn’t run it, so run it yourself before you publish. |
npx tsc --noEmit |
Checks the types without building. It reads the route types that npm run dev and npm run build generate, so run one of them once first. |
Run npm run build before publishing. It checks the types, so it catches a missing field or a typo in a content file
that the development server tolerates.
Good to know about Next.js 16
Section titled “Good to know about Next.js 16”KorDent is built on Next.js 16.4, which differs from older versions in ways you may notice:
- Turbopack is the bundler for both
npm run devandnpm run build; there is nothing to configure. next lintno longer exists:npm run lintruns ESLint directly (eslint.config.mjs), which is whynpm run builddoesn’t lint.- An
AGENTS.mdmay appear. If you work with an AI coding assistant,npm run devadds anAGENTS.md(and aCLAUDE.mdthat points to it) to the project root, telling the assistant to read the Next.js documentation bundled innode_modules/next/dist/docs/before it writes code. That is Next.js’s own behaviour: keep the files if the assistant helps you, delete them if not; the site doesn’t use them. - Server actions carry the forms, so the site needs a host that runs Node.js: it can’t be exported as plain static files (Going live).
What is in the folder
Section titled “What is in the folder”src/ app/ one folder per route; also the icons, sitemap.ts and robots.ts page.tsx Home about/ /about service/ /service (every service) and /service/<slug> (one page per service) blog/ /blog and /blog/<slug> (one page per post) contact/ /contact, with the contact form and the map book/ /book, with the booking form legal/[slug]/ /legal/<slug>, one page per legal text not-found.tsx the 404 page style-guide/ every component with examples (noindex; delete the folder to remove it) layout.tsx the font, the site's metadata, the header and the footer globals.css Tailwind and the design tokens components/ sections/ the sections pages are made of, one folder per page (home/, about/, service/, …) and the shared ones at the top (CtaSection, WhyChooseUsSection, PageHeading, FactsRow) site/ Header (with the phone menu) and Footer (with the newsletter) content/ site.ts name, title, description, domain, menu, header buttons, contact details, socials, the footer, and three shared blocks: the closing call to action, "Why Choose Us" and the booking form pages/*.ts the copy of one page each, including its title and description (home.ts also holds the review form, contact.ts the contact form) collections/*.ts services, departments, dentists, outcomes, reviews, posts, legal pages, facts, features, advantages routes.ts every URL in the site, in one place types.ts the shape of all content design-system/ tokens and reusable components — see its own README lib/ content.ts the only way pages read collections (swap this for a CMS, see cms.md) actions-booking.ts, actions-contact.ts, actions-review.ts, actions-newsletter.ts what the four forms send forms/ form providers (console, webhook, Mailchimp, Resend) and their guide meta.ts the canonical link, share image and title of a page format.ts dates, search descriptions and phone links image-size.ts reads the size of an image in public/ when the site builds (a helper; the demo's photos fill frames and don't need it) to-ui.ts turns collection items into what the components showpublic/ images/ photos, portraits and the logo as an SVG file (/images/<file>) videos/cta.mp4 the video of the closing call to action opengraph-image.png the picture shown when a link is shared.env.example the settings of the forms (copy it to .env.local)Delete src/app/style-guide/ if you don’t want the component gallery on your site; nothing else depends on it.
Editor tips
Section titled “Editor tips”- Install the Tailwind CSS IntelliSense and ESLint extensions for class name and code hints.
- The project is TypeScript: your editor tells you when a content file is missing a field, before you open the browser.
- Search across files (
Ctrl/Cmd + Shift + F) for a phrase you see on the demo site to find the file that holds it.
Updating later
Section titled “Updating later”Keep your edits in src/content/, public/ and theme.css where possible. When a new version of the template ships,
you can copy your content folder into the new release instead of re-applying changes by hand. CHANGELOG.md lists what
changed.