Going live — KorDent Next.js
Before the KorDent site goes public, replace the demo’s clinic with yours and point the forms at you; then deploy it to any Next.js host and check it again.
Replacing the demo’s clinic means its name, contact details, figures, dentists, prices, photos and video; pointing the forms at you means giving all four a destination. Once the site is deployed, click through the live address once more.
Before you deploy
Section titled “Before you deploy”| Where | |
|---|---|
Your domain in site.url (until you change it, it is the demo’s address) |
src/content/site.ts. Share links, sitemap.xml and robots.txt are built from it. |
| Name, title and description (they describe the template: write yours) | site in src/content/site.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| Your clinic’s name instead of “KorDent” / “Kordent”: the copy, the footer, the services’ texts, the posts and the legal texts | Search src/content/ for both spellings (Editing the content) |
| Contact details: the e-mail, the address and the four phone numbers are made up | contact in src/content/site.ts, and every typed tel: link (search for “555”) |
| Opening hours and the emergency panel | hours and emergency in src/content/pages/contact.ts |
| The map and “Get Direction” show your address | built from contact.address: check the map on Contact |
| Social links (they open the networks’ home pages) | socials in src/content/site.ts |
| The footer: the line about the clinic, the Dental Services column, the copyright and the disclaimer | footer in src/content/site.ts |
| Logo replaced | src/design-system/components/brand/Logo.tsx (Making it look like your brand) |
| Browser icons replaced | src/app/icon.svg, src/app/apple-icon.png |
| Share image replaced and described | public/opengraph-image.png, its description in src/lib/meta.ts |
| Demo photos and portraits replaced | public/images/ |
| The call-to-action video replaced (or removed) | public/videos/cta.mp4 (Editing the content) |
| Your own figures: the review count and rating, the facts, the badges and certifications | hero in home.ts, story in about.ts, facts.ts, features.ts |
| Your services with your prices, durations and dentists | src/content/collections/services.ts, doctors.ts, categories.ts |
| Reviews and outcomes from your own patients, with their consent | testimonials.ts, outcomes.ts |
| Claims that must be true for your clinic: the call to action’s special offer and promises, the safety banner, the memberships | cta in site.ts, banner in the page files, hero.badges in home.ts |
| Legal texts of your own (the demo’s Privacy Policy, Terms of Use and Accessibility Statement are samples) | src/content/collections/legal.ts |
| Page titles and descriptions written for your clinic | The meta of each file in src/content/pages/ |
| The four forms deliver to you | Forms |
| Style guide kept or deleted | src/app/style-guide/ |
npm run lint and npm run build pass |
— |
The demo content is there to be replaced. Leaving “KorDent”, the sample phone numbers, the prices, the dentists, the reviews, the legal texts or the stock video on a live site is the most common mistake — and on a clinic’s site, a made-up review or certification is more than a mistake.
Deploy
Section titled “Deploy”The site is a normal Next.js app: it builds to pre-rendered pages and runs on Node.js, which also handles the four forms, so any host that supports Next.js works. It can’t be published as plain static files, because the forms need the server.
Vercel (made by the Next.js team, free for personal sites)
Section titled “Vercel (made by the Next.js team, free for personal sites)”- Push the project to GitHub, GitLab or Bitbucket.
- https://vercel.com/new → import the repository → Deploy. The framework, build command and output are detected.
- Add your form variables under Settings → Environment Variables, then redeploy.
- Settings → Domains → add your domain and follow the DNS instructions.
Netlify
Section titled “Netlify”Import the repository, keep the detected settings (npm run build), add the environment variables, deploy.
Cloudflare
Section titled “Cloudflare”Cloudflare runs Next.js through the OpenNext adapter (@opennextjs/cloudflare); follow Cloudflare’s Next.js guide to
build and deploy with Wrangler.
Your own server
Section titled “Your own server”npm cinpm run buildnpm start # listens on port 3000Run it under a process manager (pm2, systemd) behind nginx or Caddy for TLS, or in a container: an LTS Node image such
as node:24-alpine, copy the project, build, CMD ["npm", "start"].
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the menu, the phone menu and the header’s two buttons (does “Call Now” dial your number?);
- the department tabs and the search over the services, a service page with its contents and its booking form;
- the outcomes’ index on desktop, the dentist tabs, the accordions;
- the video of the call to action;
- the Contact page’s map and links.
- Send yourself one of each form on the live site — a booking, a contact message, a review, a newsletter sign-up — and reply to one.
- Verify the share card. Paste the URL of the home page and of a service into https://www.opengraph.xyz or a chat window, and confirm the image and title.
- Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. A clinic also gains from a Google Business Profile with the same name, address and phone as the site. - Analytics, if you want it. Add your snippet to
src/app/layout.tsx, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. A new post is one entry in
src/content/collections/posts.ts(at the top of the list), a new review one entry intestimonials.ts; see Editing the content. Connect a CMS (Using a headless CMS) if someone else will publish.
Performance and SEO
Section titled “Performance and SEO”The template ships with what search engines look for:
- pre-rendered HTML, with links in it to every page;
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; - sized, lazy-loaded images that keep their space while they load.
Keeping the site fast is mostly about images and the video. Export photos at the size they are shown, not the size your
camera produced; the placeholders show the size each one was designed for. Keep the video short and small: it is only
fetched when the call to action scrolls into view (preload="none"), then loops while it is on the screen.