Skip to content
Sign inJoin waitlist

Editing without touching HTML — KorDent

KorDent’s HTML edition has no admin panel: services, posts, dentists and every other text are written into the pages, and you edit files (Editing the site).

When someone who doesn’t write HTML needs to publish, the options are the same for every Framebrick template: keep editing the files (GitHub’s web editor works too), a visual editor such as CloudCannon, or an edition built for a CMS. They are explained in Edit HTML templates without touching HTML. This page lists what is specific to KorDent, for whoever sets that up.

For a CMS, the KorDent Astro or KorDent Next.js edition is the shorter road: the same design, with every collection below in data files and a documented path to Sanity, Payload, Strapi, Directus or any headless CMS.

The repeated content of the site, and the fields each item shows:

Collection In the demo Fields Pages
Service 14 title, department, summary, description, price, duration, anesthetic, urgent (a red hover line), icon, photo, three texts (About Services, Services Included, Treatment Process; rich text), dentists service/<slug>.html, the grids of Home, Services and the service pages, the booking and review forms, the footer’s Dental Services column (the first four)
Department 4 name The tabs over the services grids
Dentist 4 name, specialty, bio, portrait, office hours, education, experience, languages (lists) Home, About, the booking forms
Post 6 title, excerpt, category, date, read time, photo, text (rich text) blog/<slug>.html, the Blog, “Expert Dental Tips”, “Other Post”
Legal page 3 title, update date, text (rich text) legal/<slug>.html, the footer
Outcome 4 category, index label, title, summary, quality points, timeline, treatments, four photos Home
Review 4 name, date, treatment, photo, rating, title, quote Home, Services
Fact 4 text Home (under the hero), About
Feature 8 title, text, icon “Why Choose Us” on About, Services, Book
Advantage 3 title, text The panel beside the booking form (Book, Services)

In the HTML each place holds a copy; in a CMS these become references:

  • a service belongs to one department: the data-category of its cards is the department’s slug, which the tabs filter on;
  • a service names the dentists who give it: data-booking-service on its card in the booking forms lists their slugs, and the form shows only those dentists;
  • an outcome names its treatments and a review its treatment, shown as the services’ titles;
  • the review form’s treatments and the booking forms’ treatments and dentists are the full lists;
  • “Other Post” lists three other posts, the newest first; a service page shows the other services in the order of the grid;
  • lists follow the order of the HTML, not the dates: the demo’s posts are newest first.

A service’s three texts, post texts and legal texts use a small set of HTML: paragraphs, headings (<h6> at the top of each service text, <h3> in posts, <h2> and <h3> on legal pages), bulleted lists whose items hold paragraphs, <strong> for bold, links and, in three posts, a table whose first row holds header cells. There is no italic. Many rich-text editors have no table by default: check that yours can hold one before moving the posts that carry one.

Every photo sits in a frame and is cropped to fill it, so a photo of other proportions works; use images at least as large as the layout needs:

Image Size
A service’s photo (the wide photo and the share image) 1920 × 1280 (3 : 2)
A post’s photo (the card and the wide cover) 1920 × 1280 (3 : 2)
A dentist’s portrait 600 × 750
An outcome’s photos 600 × 400 each
A reviewer’s photo 160 × 160 (shown round)