Skip to content
Sign inJoin waitlist

Editing the content — KorDent Astro

All the words and images of this Astro template live in src/content/ and src/assets/images/, in plain JSON files you edit while npm run dev shows the result.

No CMS is needed: text goes between double quotes, entries are separated by commas, and the last entry of a list or object has no comma after it. If you would rather manage content in Sanity, Payload, Strapi or Directus, see Using a headless CMS.

src/content/
site.json name, title, description, domain, menu, header buttons, contact details, socials, footer,
and the shared blocks (closing call to action, "Why Choose Us", booking form)
pages/home.json the copy of the home page
pages/about.json …and of every other page
collections/*.json services, departments, dentists, outcomes, reviews, posts, legal pages, facts, features, advantages
routes.ts the URL of every page
schemas.ts the fields each kind of item has

Not sure which file holds a piece of text? The page maps label every section of every page with its file.

src/content/site.json holds what appears on every page:

Key Shown where
site.name The browser title suffix (“Contact Us | KorDent”), share cards
site.title The browser title of any page without its own title
site.description Search results and share cards of the home page, and of any page without its own description (the 404 page). It describes the template: write yours.
site.url Set this to your domain before publishing. astro.config.mjs reads it: canonical links, share links, sitemap.xml and robots.txt are built from it.
navigation The menu in the header (and the phone menu): Home, About, Services, Blog, Contact
headerActions The header’s two buttons, “Call Now” (a tel: link) and “Book Appointment” (/book); the names screen readers hear for the logo and the phone menu button
contact The e-mail, the address and four phone numbers (main, appointments, call, emergency): the Contact page, and the e-mail, address and call number on the About photo
socials The footer’s Facebook, Instagram and X buttons
footer The line about the clinic (about), the Quick Links and Dental Services columns (their titles and links), the newsletter box (newsletter: title, text, placeholder, button and its messages), the copyright ({year} becomes the current year), the disclaimer and the legal links
cta The closing call to action of most pages: eyebrow, title, lead, the two buttons, the three promises and the video (the video)
whyChooseUs The title block of “Why Choose Us” (About, Services, Book); its cards are the features collection
booking The booking form: the advantages panel’s title, the three steps’ titles and fields, the button and its messages, the title of each submission (Forms)

The demo’s e-mail, phone numbers and address are made up: replace all of them. The phone numbers appear in two ways: the Contact page builds its links from contact.phones (+1 (415) 555-0123 calls tel:+14155550123), but several buttons carry a typed tel: link: “Call Now” in the header (headerActions.call), in the call to action (cta.call), on the Services page (hero.call, guide.call, list.banner.primary in pages/services.json) and “Need Urgent Help?” on the safety banner (banner.secondary in pages/home.json, pages/services.json and pages/service.json). Search src/content/ for “555” to find them all.

The footer’s Dental Services column is typed in footer.services, not read from the collection: update it when you rename or remove a service. The social links open the networks’ home pages: point them at your own profiles.

The clinic’s name appears in many places: site.name, the footer, the copy of every page, the services’ texts, the posts and the legal texts. The logo draws it too (Making it look like your brand). Search src/content/ for “KorDent” and “Kordent” (the footer, the call to action and the booking panel write it that way) to find them all.

There is one file per page in src/content/pages/. Most hold the sections of that page and a meta entry:

{
"meta": {
"title": "About Our Clinic",
"description": "Meet KorDent: experienced dentists…"
},
"hero": {
"title": "About Our Clinic.",
…
}
}

meta.title is the browser tab (“About Our Clinic | KorDent”) and meta.description the text of search results and share cards (80–160 characters). Change the text between the quotes, keeping the keys: the sections read them by name. Apostrophes are safe inside double quotes, and the demo uses the typographic ’. A double quote inside a text needs a backslash before it (\").

File Page
home.json Home: the hero (eyebrow, the title in two runs — the second in the accent colour —, lead, buttons, the review strip, the photo with its caption and two badges), the services grid (services: title block, filter and search labels, limit, the card’s labels, the safety banner), “About Our Clinic” (three photos, two paragraphs, the four reasons), the outcomes’ headings, the dentists’ headings, the reviews’ headings and the review form, “Expert Dental Tips”. Its browser title is meta.title; its description is site.description.
about.json About: the title, the lead, the wide photo and its paragraph, “About Us” (the review strip, two photos and the Mission, Vision and Story cards), the dentists’ headings
services.json Services (/service): the title and buttons, the services grid (list), the Patient Guide (three photos, four steps, “Still Have Questions?”), the booking band’s title and the reviews’ headings with the review form
service.json The words shared by every service page: the table of contents, “Instant Booking” and “Our Clinical Departments” (the other services)
blog.json Blog: title and lead
post.json The labels under a post’s title (Category, Publish Date, Read Time) and “Other Post”
contact.json Contact: the title, the labels of the contact details, the opening hours, the emergency panel, the contact form (Forms) and the map’s labels
book.json Book: the title and lead (the form is booking in site.json)
legal.json “Last Updated : “ on the legal pages
not-found.json The 404 page: its browser title, the title, the text and the button

Some blocks repeat between pages with their own copy in each file: the dentists’ headings are in home.json and about.json, the services grid in home.json, services.json and service.json, the reviews and the review form in home.json and services.json. Change both when you want the same words in both places (Pages and sections).

src/content/collections/ holds the lists the site builds pages and sections from. Each file is a JSON array; the schemas in src/content/schemas.ts check every entry when the site builds.

File What it feeds
services.json One page per service; the services grid on Home (the first six that match the filter), on the Services page (all of them) and at the end of a service page (the first six others); the treatments of the booking form and of the review form; the treatment names on the outcomes and the reviews
categories.json The departments: the filter tabs over the services grid. Each service names one by its slug.
doctors.json The dentist tabs on Home and About; the dentists of the booking form (a service names its own by slug)
outcomes.json “Real Patient Outcomes” on Home: one card each, numbered in the index on the left
testimonials.json The review cards on Home and on the Services page
posts.json The Blog, one page per post, “Expert Dental Tips” on Home (the first three) and “Other Post” under a post (the first three others)
legal.json One page per legal text: /legal/privacy-policy, /legal/terms-of-use, /legal/accessibility-statement
facts.json The four tinted boxes under the Home hero and under the About photo
features.json The eight cards of “Why Choose Us” (About, Services, Book)
advantages.json The advantages panel beside the booking form (Book, Services)

The order of the items in the file is the order on the site. The Blog doesn’t sort posts by date: the demo lists them newest first, so put a new post first to show it first.

Copy an existing entry, paste it after it (mind the comma between entries), and change the values:

{
"slug": "gum-treatment",
"title": "Gum Treatment",
"category": "preventive-care",
"summary": "Deep cleaning and…",
"description": "Our periodontal care…",
"price": "$150 - $300",
"duration": "60 mins",
"anesthetic": "Local / Pain-Free",
"urgent": false,
"icon": "shield",
"label": null,
"image": { "src": "/images/service-gum-treatment.jpg", "alt": "…" },
"about": [],
"included": [],
"process": [],
"doctors": ["emily-carter"]
}
Field What it is
slug The URL: /service/gum-treatment
title The card, the page title, the booking form, the review form’s choices
category A slug of categories.json: the filter tab it falls under
summary The card, the booking form’s treatment card, the page’s search description
description The card’s details and the lead under the page title
price, duration, anesthetic “Est. Price” and the two facts on the card
urgent true: a red line on the card’s left edge on hover (emergency care)
icon One of the service icons (serviceIcons in schemas.ts)
label Kept from the original CMS (“Urgent Care”); not shown
image The wide photo and the share image
about, included, process “About Services”, “Services Included” and “Treatment Process”, in rich text (below); an empty process leaves that block and its contents entry out
doctors Slugs of doctors.json: the dentists the booking form offers for it

A service page shows its title, description and photo, a table of contents beside its three texts, and the booking form with the service already chosen and its own dentists, then the other services. The demo starts each text with a small heading (level 6).

Adding a post, dentist, outcome, review or legal page

Section titled “Adding a post, dentist, outcome, review or legal page”
Add Fields
Post slug, title, excerpt (under the title, the card text and the search description), category (any words, shown on the card and under the title), date ("2026-03-12", shown as “Mar 12, 2026”), readTime ("5 min"), image ({ "src", "alt" }: the card and the wide cover), body (rich text, below)
Dentist (doctors.json) slug, name, specialty, bio, image ({ "src", "alt" }: the portrait), and four lists shown on the card: hours, education, experience, languages
Outcome slug, category (the card’s label), tab (its name in the index), title, summary, quality (the points under “Quality Standards & Durability:”), timeline, services (slugs of services.json, shown as their titles) and images (four photos)
Review (testimonials.json) slug (an id), name, date ("2026-04-07"), service (a slug of services.json, shown as its title), photo ({ "src", "alt" }, shown round), rating (1 to 5 stars), title (the quote in bold) and quote (the text)
Legal page slug, title, updated ("2026-07-14", shown as “Last Updated : Jul 14, 2026”) and body (rich text). The footer links the three demo pages from footer.legalLinks in site.json: add a link there for a new page.
Department (categories.json) slug and name: a new filter tab. Services join it through their category.
Fact, feature, advantage A fact is text; a feature title, text and icon (one of the “Why Choose Us” icons, featureIcons in schemas.ts); an advantage title and text

A new service, post or legal page gets its own page, and its entry in sitemap.xml, on the next build. Dentists, outcomes, reviews and the rest have no pages.

Most lists take any number of items. A few blocks are laid out for a fixed number, so keep it:

Where How many
The facts row (Home, About) four facts: each position has its own icon and tint (blue, the accent, green, red)
An outcome four images
Home, “About Our Clinic”; the Services page’s Patient Guide three photos (one tall, two short)
About, “About Us” two photos and three cards
The review strips (Home hero, About) four avatars

Delete the entry (and the comma before it, if it was the last one). Its page and its sitemap entry disappear on the next build. Places that name the item as text stay as they are: the footer’s Dental Services column and legal links. A slug that no longer exists is shown as the slug itself on a review or an outcome, and a dentist that no longer exists is simply left out of the booking form.

src/content/schemas.ts is the reference: it lists every field and a comment for the ones that are not obvious. npm run check and npm run build name any entry that lacks a field or has one of the wrong type.

A service’s three texts, a post body and a legal text are a list of blocks:

[
{ "type": "heading", "level": 3, "text": "1. Brush Twice a Day" },
{ "type": "paragraph", "text": "Plain text with a **bold** run and a [link](/book)." },
{ "type": "paragraph", "text": "First line\nSecond line" },
{ "type": "list", "ordered": false, "items": [
[{ "type": "paragraph", "text": "First item" }],
[{ "type": "paragraph", "text": "Second item" }]
] },
{ "type": "table", "rows": [
[{ "header": true, "text": "Feature" }, { "header": true, "text": "Veneers" }],
[{ "header": false, "text": "Duration" }, { "header": false, "text": "10–15 years" }]
] }
]
  • Headings take the text style of their level (level 2 to 6): the posts use 3, the legal pages 2 and 3, the service texts 6 (one demo service, Traditional Orthodontics, also uses 2 and 3).
  • Inline marks: **bold**, text links (a tel: link keeps only its digits) and \n for a line break. There is no italic.
  • Lists: ordered: true for numbers; each item is itself a list of blocks, so an item can hold a nested list.
  • Tables: rows of cells; a cell with header: true is a header cell (a tinted background). A table wider than a phone scrolls sideways inside its frame. Three demo posts carry a comparison table.

The closing call to action (cta in src/content/site.json) ends with a video that plays muted and in a loop while it is on the screen, and stays still for visitors who prefer reduced motion:

"video": { "src": "/videos/cta.mp4", "poster": "/images/home-hero.jpg", "label": "A dental treatment unit in a bright clinic" }
  • src is a file in public/videos/ or a web address. Keep the clip short and small (a few MB, about 1280 × 720 or 1140 × 601, the frame’s shape), because it loops; a larger file belongs on a video host or a CDN. It is only fetched when the call to action comes into view.
  • poster is the picture shown until the clip plays, an image of src/assets/images/: the demo reuses the Home hero photo.
  • label is what screen readers hear.

The demo’s clip is a stock video: replace it with footage of your own clinic before you launch. To remove the video, delete the <video> in src/components/sections/CtaSection.astro.

  1. Put the file in src/assets/images/.
  2. Refer to it in the content as /images/<file>.

Astro resizes and compresses every photo when the site builds and serves each device a size that fits. The download’s placeholders show the size each photo was designed for; use photos at least as large:

Photos Demo size
The Home hero photo 1000 × 1500, portrait
“About Our Clinic” (Home) and the Patient Guide (Services) one 1300 × 1947 and two 700 × 467
The wide photo of About 1920 × 1280 (3 : 2, at least 550 px tall)
The two photos of “About Us” (About) 800 × 1200
A service’s image (the wide photo and the share image) 1920 × 1280 (3 : 2)
A post’s image (the card and the wide cover) 1920 × 1280 (3 : 2)
A dentist’s portrait 600 × 750
An outcome’s four photos 600 × 400
The reviewers’ photos 160 × 160 (shown round)
The four avatars of the review strips 120 × 120 (shown round, 42 px)

Photos in a fixed frame are cropped to fill it, so a photo of other proportions works, but you lose the edges the frame cuts. Frames that follow the screen change shape between phone, tablet and desktop, so keep the subject away from the edges.

Every photo written as { "src", "alt" } has an alt: a short description for screen readers and search engines. Write one for each photo you change; an empty "alt": "" marks a photo as decoration (the demo’s review avatars).

Three files sit in public/ because browsers and social networks ask for them by name:

File What it is
public/icon.svg, public/apple-icon.png The icon in the browser tab and on a phone’s home screen (180 × 180)
public/opengraph-image.png The picture shown when someone shares a link (2400 × 1260; 1200 × 630 or larger)

The share image’s description for screen readers is shareImage.alt in src/lib/meta.ts, next to its size: change width and height there if your image has another size, and write a description of your own. Every page uses this image when shared, except the service and post pages, which share their own photo.

Almost every word is content, including the forms’ messages. The few interface words that never change per site live in the code:

  • “Main” (the menu’s name for screen readers) in src/components/site/Header.astro;
  • the date format of posts, reviews and legal pages (“Mar 12, 2026”) in src/lib/format.ts;
  • the page’s language, lang="en", and og:locale in src/layouts/Layout.astro;
  • the forms’ fallback labels (“Submit”, “Thank you”, “Something went wrong”) in the design system, used only when the copy gives none.

Search for the word and you will find it.

Terminal window
npm run check
npm run build

A clean check and build mean every content file has the fields it needs and every page still renders; the build also stops when an image is missing. It doesn’t check that links written as text ("/book") lead somewhere: click through the site once with npm run preview after big changes. See Going live for the rest of the checklist.