Skip to content
Sign inJoin waitlist

Going live — KorDent Astro

Before the KorDent site goes public, replace the demo’s clinic with yours and point the forms at you; then build it, upload the static files to any 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.

Where
Your domain in site.url (until you change it, it is the demo’s address) src/content/site.json. 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.json; 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.json, and every typed tel: link (search for “555”)
Opening hours and the emergency panel hours and emergency in src/content/pages/contact.json
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.json
The footer: the line about the clinic, the Dental Services column, the copyright and the disclaimer footer in src/content/site.json
Logo replaced src/design-system/components/brand/logo-paths.ts and Logo.astro (Making it look like your brand)
Browser icons replaced public/icon.svg, public/apple-icon.png
Share image replaced and described public/opengraph-image.png, its description in src/lib/meta.ts
Demo photos and portraits replaced src/assets/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.json, story in about.json, facts.json, features.json
Your services with your prices, durations and dentists src/content/collections/services.json, doctors.json, categories.json
Reviews and outcomes from your own patients, with their consent testimonials.json, outcomes.json
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.json, banner in the page files, hero.badges in home.json
Legal texts of your own (the demo’s Privacy Policy, Terms of Use and Accessibility Statement are samples) src/content/collections/legal.json
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/pages/style-guide.astro
npm run check and npm run build pass, and npm run preview looks right —

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.

npm run build writes a complete static site to dist/: HTML files, one stylesheet, a few small scripts, the font file, optimised images and the video. Any host that serves files can run it, with no Node.js needed on the server (unless you chose server-mode forms).

Vercel, Netlify or Cloudflare Pages (free for most sites)

Section titled “Vercel, Netlify or Cloudflare Pages (free for most sites)”
  1. Push the project to GitHub, GitLab or Bitbucket.
  2. Import the repository. Astro is detected: build command npm run build, output folder dist.
  3. Add your form variables (PUBLIC_FORM_ENDPOINT, …) in the host’s environment settings, then deploy.
  4. Add your domain in the host’s Domains settings and follow the DNS instructions.

Pages are built as files (about.html, service/general-dentistry.html) and served at clean addresses (/about). Netlify and Cloudflare Pages do that by default. On Vercel, add a vercel.json next to package.json:

{ "cleanUrls": true }

Any other host (shared hosting, S3, a VPS)

Section titled “Any other host (shared hosting, S3, a VPS)”
Terminal window
npm run build

Upload the contents of dist/ to the web root. For clean addresses, make the server try <path>.html:

  • Apache (.htaccess):

    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME}.html -f
    RewriteRule ^(.+)$ $1.html [L]
    ErrorDocument 404 /404.html
  • nginx: try_files $uri $uri.html $uri/ =404; and error_page 404 /404.html;

If you set PUBLIC_FORM_MODE=server, add your host’s adapter first (npx astro add vercel, netlify, cloudflare or node). Only the form route runs on the server; every page stays static.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Analytics, if you want it. Add your snippet to the <head> in src/layouts/Layout.astro, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner.
  6. Keep it current. A new post is one entry in src/content/collections/posts.json (at the top of the list), a new review one entry in testimonials.json; see Editing the content, and rebuild. Connect a CMS (Using a headless CMS) if someone else will publish.

The template ships with what search engines look for:

  • static 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.txt and share cards;
  • resized, lazy-loaded images that keep their space while they load.

Keeping the site fast is mostly about images and the video. Astro resizes the photos, but export them at the size they are shown, not the size your camera produced: a 12 MB camera file still slows the build. 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.