Skip to content
Sign inJoin waitlist

KorDent documentation — HTML

Everything you need to go from the downloaded folder to a published dental clinic site. Read in this order, or jump to what you need.

Guide What it covers
Editing the site Opening the site, editing text, links and images, the blocks that repeat, the video, adding and removing services, posts and pages
Pages and sections Every kind of page, its sections with a map of each, and how the pages link to each other
Making it look like your brand Colours, the logo, the font, the Tailwind classes, rebuilding the stylesheet, the style guide, motion
Forms Making the four forms (booking, contact, review, newsletter) deliver to you
Editing without touching HTML Your options when someone else needs to edit the site without touching HTML
Going live Pre-launch checklist, uploading, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers
  • 10 kinds of page, 29 addresses: Home, About, Services (service.html), Blog, Contact, Book and the 404 page; a page for each of the 14 services (service/), 6 posts (blog/) and 3 legal texts (legal/).
  • 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, posting to the form service or webhook you choose.
  • Filter and search of the services by department and by name, a table of contents on every service page, an index of the patient outcomes, dentist tabs and accordions.
  • A video in the closing call to action, which plays muted while it is on the screen.
  • Motion from the original design, with reduced-motion support, and a style guide of every component in style-guide.html.
  • 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 assets/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 part of the template.
  1. Open index.html in your browser. That is the whole site: no install, no build.
  2. Open the folder in a code editor (VS Code is a good free one).
  3. Replace the contact details, the phone numbers, the social links and the demo domain across all files with your editor’s find and replace in files (Editing the site), then search for “KorDent” and “Kordent” to put your clinic’s name in the copy.
  4. Replace the photos in assets/images/: keep the file names and every page picks them up (Editing the site). Replace the video assets/videos/cta.mp4 too (Editing the site).
  5. Replace the logo (Making it look like your brand), the icons and the share image in the root folder (icon.svg, apple-icon.png, opengraph-image.png).
  6. Put your form endpoint in assets/js/config.js (Forms).
  7. Upload the folder to your host (Going live).
  • One HTML file per page. about.html is /about.html; each service, post and legal text has its own file in service/, blog/ and legal/ (Pages and sections).
  • One stylesheet. assets/css/style.css, built from src/css/style.css with Tailwind CSS. You only rebuild it when you use a class that isn’t in the site yet, or change the theme (Making it look like your brand).
  • One script. assets/js/main.js runs the phone menu, the blocks and titles that rise into view, the accordions, the tabs, the service filter and search, the booking form’s dentist list, the star rating, the video and the forms. You rarely need to touch it: your settings go in assets/js/config.js.
  • Copies, not references. A block that shows on several pages (the services grid, the reviews, the dentists, the closing call to action, “Why Choose Us”, the booking form, the footer) is written into each of them. Change every copy, or use find and replace in files (Editing the site).
  • No framework, no dependencies at runtime. The pages work from any static host, and even straight from disk.

If you will add services or posts every week, choose the KorDent Astro or KorDent Next.js edition instead: a new item is one entry in a data file, and every page, list and sitemap line follows (Editing without touching HTML).