Making it yours — KorDent AI Prompts
After the last prompt you have the KorDent site with its demo text, grey placeholder photos and a still picture where
the clinic video goes. Everything a visitor reads lives in src/content/, so most changes are edits to text files — or
a sentence to your AI tool.
| What | Where |
|---|---|
| Clinic name (the logo link’s name and the “ | KorDent” ending of the browser titles), the home page’s browser title and description, site address | src/content/site.json → site |
| Menu, the header’s “Call Now” and “Book Appointment”, contact details, the footer (its text, link columns, newsletter, copyright, disclaimer and legal links), social links | src/content/site.json (navigation, headerActions, contact, footer, socials) |
| The blocks shared by several pages: the closing call to action with the clinic video, Why Choose Us and the booking form | src/content/site.json (cta, whyChooseUs, booking) |
| The copy of each page, with its browser title and description | src/content/pages/<page>.json (home.json, about.json, …) |
| The words every service, post and legal page shares | pages/service.json, pages/post.json, pages/legal.json |
| Services, departments, dentists, outcomes, reviews, posts, legal pages, facts, advantages and reasons | src/content/collections/<name>.json |
Change the text between the quotes and keep the field names. Or ask your tool: “Change the clinic’s name to Brightside
Dental and the contact email to hello@brightside.com in site.json.” Set site.url to your domain before you publish —
the sitemap and share links are built from it.
The clinic’s name appears in more places than site.name: the footer’s copyright, the booking form’s “Kordent Service
Advantages:”, the copy of most pages, the service texts, the posts and the legal texts (which also give
privacy@kordent.com, legal@kordent.com and accessibility@kordent.com). The logo draws it too (below). Ask your tool
to search src/content/ for “kordent”, in any case, to find them all.
The demo’s figures and claims are placeholders too: the review count, rating and “Based on 1,850+ Google local business
reviews” (hero in pages/home.json, story in pages/about.json), the hero’s badges (“ADA / AACD Member”,
“Class-B Autoclave”), the facts (“10+ Years Experience”, “24/7 Emergency Care” — collections/facts.json), the call to
action’s special offer and promises (cta in site.json) and the safety banner under the services. Write only what
is true of your clinic.
In the footer’s copyright, {year} becomes the current year. The footer’s Dental Services column is a list of links of
its own (footer.services in site.json): it doesn’t follow the services collection. The social links open the
networks’ home pages: point them to your own profiles.
Some blocks appear on more than one page, and each page’s file holds its own copy: the services grid with its
department tabs and safety banner (services in home.json, list in services.json, departments in
service.json), the dentists (doctors in home.json and about.json), the reviews with the review form
(testimonials in home.json and services.json) and the review summary (Home’s hero and About). Change them in every
file that has them.
Phone numbers, address and hours
Section titled “Phone numbers, address and hours”contact in site.json holds the clinic’s details: email, address and four numbers in phones — main (the
phone), appointments (WhatsApp), call (the Appointment Hotline, also on About) and emergency (the emergency panel on
Contact). Write each number the way people should read it; the links dial its digits, and WhatsApp opens
https://wa.me/ with the appointments digits. The map on Contact is a Google Maps view of address, and “Get
Direction” asks Google Maps for the way there: change the address and both follow.
The “Call Now” buttons carry their own link, tel:+14155550145: in headerActions.call and cta.call in site.json,
and hero.call and guide.call in pages/services.json. Put your number there too.
Opening hours are in two places: the Contact page’s rows (hours.rows in pages/contact.json: days, hours, the
tag status and open, which colours it) and each dentist’s hours. The Accessibility Statement also lists business
hours in its text.
Services and departments
Section titled “Services and departments”Each service in collections/services.json has:
slug— its address (/service/dental-implants), unique;title— the card’s and the page’s title;summary— under the title, on the booking form’s treatment card and the page’s search description;category— the slug of its department incollections/categories.json, which decides under which tab it shows;icon— its line icon:shieldshows the fileshape-shield.svg(public/icons/), so a new icon is a newshape-<name>.svgfile of the same kind (a 24 grid, a 1.5 stroke);description— the card’s text (cut after five lines);price,durationandanesthetic— written as you want them shown (“$99 - $150”, “45 mins”);urgent—truedraws a red line on the card when hovered (the emergency service);labelis not shown on the site;image— the photo of its page and its share image;about,includedandprocess— the page’s three texts, as blocks (see below);doctors— the slugs of the dentists who give it (collections/doctors.json): the booking form lists only them once the treatment is chosen.
The order of the file is the order on the site: Home shows the first six that match the chosen tab and the search, the
Services page all of them, a service page six others, and the booking forms list them all. “Learn More” on a card opens
the service’s page and “Book a treatment” the same page at its booking form (#booking). To add a service, copy one,
give it a new slug and change the fields; it gets its own page and appears in the lists, the forms and the sitemap.
The departments are collections/categories.json: a slug and a name, shown as tabs after “All Services” in the
file’s order. Rename them freely; if you change a slug, change the category of its services too.
Dentists, outcomes and reviews
Section titled “Dentists, outcomes and reviews”- Dentists (
collections/doctors.json):slug,name,specialty,bio,image(a portrait), and the listshours,education,experienceandlanguages. Home and About show them all as tabs (an accordion on phones); the booking forms show them as choices. A new dentist appears in the booking form only for the services whosedoctorsname them (or every service with an empty list). - Outcomes (
collections/outcomes.json):slug,category(the chip),tab(the index’s label),title,summary,quality(three points),timeline,services(the slugs of the treatments, shown by name) and fourimages. Home shows them in the file’s order. - Reviews (
collections/testimonials.json):slug(an id),name,date,service(the slug of the treatment, shown by name),photo,rating(1–5 stars),titleandquote. Home and the Services page show them all. These are sample reviews: replace them with real ones from your patients, with their consent.
The review form’s Treatment Type lists every service by name, so it follows the services collection by itself.
Posts, legal pages and the rest
Section titled “Posts, legal pages and the rest”- Posts (
collections/posts.json):slug,title,excerpt,category(a word shown on the card),date(2026-03-12, shown as “Mar 12, 2026”),readTime,imageand the articlebodyas blocks. The Blog shows them all, Home the first three, a post page three others. Posts are listed in the file’s order, not by date: the demo keeps them newest first, so put a new post first to show it first. - Legal pages (
collections/legal.json):slug(/legal/privacy-policy),title,updated(a date) andbody. The footer links them fromfooter.legalLinksinsite.json: add a link there for a new page. - Facts (
collections/facts.json, the row under Home’s hero and on About), advantages (collections/advantages.json, with the booking form on Book and Services) and reasons (collections/features.json, Why Choose Us on About, Services and Book, each with a line icon like the services’).
Blocks are { "type": "paragraph", "text": "…" }, { "type": "heading", "level": 2, "text": "…" } (levels 2, 3 and 6),
{ "type": "list", "ordered": false, "items": [[…], …] } (a bulleted list whose items are lists of blocks) and, in the
posts, { "type": "table", "rows": […] }. In a text, **bold** is bold, label a link and \n a new line.
Ask your tool if you prefer: “Add a post about dental anxiety to posts.json, with the same fields as the others.”
Photos
Section titled “Photos”The pack uses placeholders; each shows the size its photo is designed for (for example 1920 × 1282). Put your photos
in public/images/ with the same file names and they replace the placeholders:
| Photos | Files |
|---|---|
| Home: the hero, About Our Clinic, the faces beside the rating (also on About) | home-hero.jpg, home-about.jpg, home-about-2.jpg, home-about-3.jpg, review-avatar-1.jpg … -4.jpg |
| About | about-hero.jpg, about-mission.jpg, about-mission-2.jpg |
| Services: the Patient Guide | services-guide.jpg, services-guide-2.jpg, services-guide-3.jpg |
| Services, dentists, outcomes, reviews, posts | service-<slug>.jpg, doctor-<slug>.jpg, outcome-<slug>-1.jpg … -4.jpg, testimonial-<slug>.jpg, post-<slug>.jpg |
Photos fill their frame and are cropped, so keep their proportions close to the placeholder’s. A new photo can have
any name: refer to it in the content as /images/<file>, with an alt that describes it. In a chat builder, upload the
photos and tell the tool which file names to give them.
The clinic video
Section titled “The clinic video”The call to action at the end of Home, About, the Blog and every post plays a clip of the clinic, muted and looping,
while it is on the screen (cta.video in site.json). The demo’s clip is not in the pack: until you add one, the video
shows its poster, the Home hero photo. Put an MP4 of about 1280 × 720 and a few MB at public/videos/cta.mp4, or set
src to another file or a video host’s address. poster is the picture shown before the clip loads (the frame is
wide, so a wide photo suits it better than the tall hero photo) and label the video’s description for screen readers.
Logo and icon
Section titled “Logo and icon”The logo — the KorDent tooth mark and wordmark in teal, with a lime plus — is public/images/logo.svg, 125 × 28; the
header and the dark footer both show it. Depending on your tool, the Logo component shows this file or draws the same
paths inline. Ask your tool to replace it with your own SVG: “Use public/my-logo.svg as the Logo in the header and the
footer.” Check that it reads on the white header and on the dark footer. The browser tab icon is public/icon.svg,
the home-screen icon public/apple-icon.png (180 × 180) and the share image public/opengraph-image.png (1200 × 630,
made by the last prompt): replace all three.
Colours, fonts and sizes
Section titled “Colours, fonts and sizes”Prompt 1 set up the design tokens: colours (--color-primary, --color-ink, --color-black, --color-muted,
--color-white, --color-stone, --color-page, --color-lime, --color-night and a few more), the font, text styles
and spacing. Primary (teal) is the accent — the primary buttons, the active tabs, the icons, the chips — and Lime the
second button and the icon covers, so changing that pair gives the site your brand colours: “Change –color-primary to
#2563EB and –color-lime to #FDE68A.” White text sits on Primary, so pick one dark enough. Night is the footer. Keep
the text styles’ sizes per breakpoint unless you want a different rhythm.
The font is Inter (weights 400 to 700, headings 600), with its optical size held at the text cut on every size. Another
font works the same way — ask the tool to load it and use it in --font-sans; a font without an optical-size axis
simply ignores that setting.
To remove a page, delete it and ask your tool to take it out of the menu (navigation in site.json), the footer’s
Quick Links, the sitemap and the buttons that lead to it. Book is not in the menu: every “Book Appointment” button leads
to it. To add a page, write a prompt in the style of the page prompts — list its sections and reuse the components (“a
page title, then ServiceCards in a grid”) — so it matches the rest; it sits under the same white header.
To remove a section, ask the tool to take it out of the page. The booking form on a service page is the target of the
cards’ “Book a treatment” (#booking): if you remove it, ask the tool to point those buttons at /book.