Skip to content
Sign inJoin waitlist

KorDent documentation — Next.js

Everything you need to take KorDent for Next.js from the downloaded folder to a published dental clinic site. Read in this order, or jump to what you need.

Guide What it covers
Install and run Requirements, install, the commands, what is in each folder
Editing the content Editing text, images, the video, services, dentists, outcomes, reviews, posts and legal pages — no CMS needed
Making it look like your brand Colours, the logo, fonts, text styles, spacing, motion, components, icons, the style guide
Pages and sections The header, the sections of every page with a map of each, adding, removing and reordering pages and sections
Forms Making the four forms (booking, contact, review, newsletter) deliver to you
Using a headless CMS The collections and their fields, for connecting Sanity, Payload, Strapi, Directus or any other headless CMS
Going live Pre-launch checklist, deploying, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers
  • 10 kinds of page, 29 addresses:
    • Home, About, Services, Blog, Contact, Book and the 404 page;
    • a page for each of the 14 services, 6 posts and 3 legal pages, built from the collections;
    • Services lives at /service, in the singular, so a service is /service/general-dentistry (Pages and sections).
  • 10 collections in src/content/collections/: services (14), departments (categories, 4), dentists (doctors, 4), posts (6), legal pages (3), patient outcomes (4), reviews (testimonials, 4), the facts row (4), the “Why Choose Us” features (8) and the booking advantages (3).
  • 4 forms: the booking form (on Book, on the Services page and on every service page), the contact form, the review form (Home and Services) and the newsletter in the footer, with a server action each and four ways to deliver them (a log, a webhook, Mailchimp, Resend).
  • Filter and search of the services by department and by name, a sticky table of contents on every service page, a sticky index of the patient outcomes and dentist tabs.
  • A video in the closing call to action, which plays muted while it is on the screen.
  • Motion from the original design (rising blocks and words, button and link hovers, accordions, tabs, the phone menu), with reduced-motion support, and a style guide of every component at /style-guide.
  • Search and sharing: a title, a description and a canonical link for every page, share cards, icons, sitemap.xml and robots.txt.
  • Placeholders: the photos in public/images/ are grey placeholders that show their sizes (the demo uses photos from Unsplash and Pexels, which can’t be sold with a template). The logo is drawn for the template.
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (KorDent design system), CHANGELOG.md and LICENSE.md.
Terminal window
npm install
npm run dev
  1. Open http://localhost:3000.
  2. Put your clinic’s name, title, description and domain in src/content/site.ts, and your menu, phone numbers, e-mail, address, footer and social links in the same file.
  3. Replace the images in public/images/ (keep the file names and you are done), including the dentists’ portraits and the reviewers’ photos, and the video public/videos/cta.mp4 (Editing the content).
  4. Replace the logo (Making it look like your brand), the browser icons in src/app/ (icon.svg, apple-icon.png) and the share image (public/opengraph-image.png).
  5. Edit the page copy in src/content/pages/, and your services, dentists, outcomes, reviews, posts and legal pages in src/content/collections/. Search for “KorDent” and “Kordent”: the demo’s clinic is named in many places.
  6. Point the four forms at your inbox: Forms.
  7. Deploy: Going live.

Nothing else is required: the site has no database, no account to create and no paid service to run.

  • Content is data. All text and every collection item live in src/content/. Pages read the collections through src/lib/content.ts, which is why swapping in a CMS later touches one file, not the whole site.
  • Design is tokens. Colours, breakpoints and easing curves are in src/design-system/theme.css; text styles and springs in src/design-system/tokens/. Change a token and every page follows (Making it look like your brand).
  • Components are shared. Every button, card, form field and section is in src/design-system/ or src/components/, and is shown at /style-guide on your own site.
  • Blocks are shared too. The closing call to action, “Why Choose Us”, the booking form and the services grid appear on several pages from one copy (Pages and sections).