Troubleshooting — KorDent Astro
Most problems with this Astro template come from a content file with a typo, a missing image, or a setting that was not rebuilt into the site. Those answers come first.
Then come the questions buyers ask most.
Errors you may hit
Section titled “Errors you may hit”npm install fails, or the site behaves oddly after an update.
Delete node_modules/ and package-lock.json, then npm install again. Check that node -v is 22.12 or newer.
Port 4321 is already in use.
npm run dev -- --port 4322, or stop whatever holds the port.
The build stops with InvalidContentEntryDataError.
A collection item lacks a field that src/content/schemas.ts requires, or a field has the wrong type (a number where
text is expected, an icon name that isn’t in the list). The message names the collection, the item and the field.
npm run check finds the same thing faster.
The build stops with “key must be a string at line 3 column 25”, or “Unable to load your Astro config”.
A JSON file has a typo: a comma after the last entry of a list, a missing comma or quote, or a comment, which JSON
doesn’t allow. The message gives the line and the column but not always the file, so look in the file you changed last.
When it says it can’t load the config, the file is src/content/site.json (astro.config.mjs reads it).
The terminal shows [file-loader] Error reading data from src/content/collections/….json.
The same kind of typo, in a collection file. Astro can’t read that file, so your changes to it are missing from the
site. Fix the file before you publish.
Image /images/… not found: add it to src/assets/images.
The file must be in src/assets/images/ and the content must refer to it as /images/<file>: same spelling, same
extension. The build also names the page it was rendering.
A photo is cropped in the wrong place. Every photo sits in a frame and is cropped to fill it from the centre, and the frames change shape between phone, tablet and desktop. Crop the photo to the shape you want and keep the subject away from the edges (Editing the content).
The build fails but npm run dev was fine.
The build is stricter: it renders every page and processes every image. Read the first error, not the last; it names the
file or the page. Run npm run check too: it checks the types and the content, which the development server doesn’t.
/about works on my laptop but shows “404” on the host.
The pages are files (about.html). Your host needs clean URLs: see Going live.
A form says “Something went wrong”.
Static mode: the endpoint answered with an error; open the browser’s console for the reason, and check
PUBLIC_FORM_ENDPOINT. Server mode: the reason is in your host’s function logs, after
[forms] New appointment request could not be delivered (or “New contact message”, “New patient review”, “New
newsletter subscriber”); check that the environment variables are set for the environment you deployed to and that
FORM_PROVIDER names a provider that exists. The PUBLIC_ variables are written into the pages when the site builds,
so rebuild (or redeploy) after changing any of them (Forms).
A form says “Thank you” but nothing arrives.
With no PUBLIC_FORM_ENDPOINT and no PUBLIC_FORM_MODE, the forms run in demo mode: they log the fields in the browser
console and send nothing. In server mode, FORM_PROVIDER=console (the default, also when the variable is missing)
writes submissions only to the server log: set a provider (Forms). If you added a field named fax,
rename it: that name is the hidden spam trap, and a submission that fills it is dropped.
The build stops with NoAdapterInstalled.
PUBLIC_FORM_MODE=server adds a route that runs on a server, which needs your host’s adapter: npx astro add vercel
(or netlify, node, cloudflare). To stay fully static, leave PUBLIC_FORM_MODE empty (Forms).
The booking form lists no dentist for a treatment.
The dentists of a treatment are the slugs in the service’s doctors list in src/content/collections/services.json;
each must match a slug in doctors.json. Until a treatment is chosen, the form lists every dentist.
A new service doesn’t show on the Services page.
The page shows at most list.limit services (14, the demo’s count) in src/content/pages/services.json: raise it. Home
shows the first six that match the chosen tab (services.limit in home.json).
A service doesn’t appear under its department tab.
Its category must be the slug of a department in categories.json ("preventive-care", not “Preventive Care”).
A review or an outcome shows a slug instead of a treatment’s name.
Its service (or services) names a slug that no service has. Fix the spelling, or add the service.
A new post isn’t first in the Blog.
The Blog doesn’t sort by date: it shows the posts in the order of src/content/collections/posts.json, newest first in
the demo. Put the new post at the top of the list.
“Call Now” dials the demo’s number.
The buttons carry typed tel: links: search src/content/ for “555” and replace each
(Editing the content).
The map on Contact shows the wrong place.
The map and “Get Direction” search Google Maps for contact.address in src/content/site.json. Write the address the
way Google finds it.
The share image or title is the old one.
Facebook, LinkedIn and X cache them. Use their debuggers to refresh, and confirm that site.url is your domain.
Nothing moves: the blocks, the words. The visitor’s system (yours, if you see it) has “reduce motion” switched on, and the site honours it (Making it look like your brand). Blocks fade in without rising and the video stays on its poster. If nothing appears to move with that setting off, check the browser’s console: the motion runs in small scripts.
The video does not play.
It plays when the call to action is on the screen, muted and in a loop, and never for visitors who prefer reduced motion.
If it doesn’t play for you either, check cta.video.src in src/content/site.json: /videos/cta.mp4 for a file in
public/videos/, or a working address, and an MP4 the browser can play (Editing the content).
A legal link in the footer leads to the 404 page.
footer.legalLinks in src/content/site.json are typed addresses: /legal/<slug> must match a slug in
src/content/collections/legal.json.
Questions
Section titled “Questions”Can I use this template for a client? See License: that is the one place that answers it for your licence.
Can I remove the style guide, a whole page, a section or the video? Yes:
- the style guide: delete
src/pages/style-guide.astroandsrc/components/style-guide/; - a page: see Pages and sections;
- a section: delete its line (and its import) from the page file in
src/pages/, for example<OutcomesSection … />insrc/pages/index.astro; - the video: Editing the content.
Can I change the fonts to my brand’s? Yes: Making it look like your brand.
Does the booking form connect to a calendar or practice software? Not by itself: a booking is a request that reaches you like the other forms. Send it to your practice software or a scheduling tool through a webhook (most offer an API, or connect through Zapier or Make), or replace the Book page’s form with your booking tool’s embed (Forms).
Do I need a CMS? No. Content is files you edit. Add one when somebody who does not use a code editor has to publish (Using a headless CMS).
Can I write the site in another language?
All the copy is content, so write it in your language. Then set lang and og:locale in src/layouts/Layout.astro,
the date format in src/lib/format.ts ("en-US") and the menu’s name for screen readers, “Main”, in
src/components/site/Header.astro. The template has no language switch or language-based routing.
Does the site need a cookie banner? As shipped, the template sets no cookies of its own and the font is served from your own domain. The Contact page embeds a Google Maps view, which loads from Google and may set Google’s cookies; declare it, or replace it with a static picture and the “Get Direction” link. A form service you choose in static mode, and any analytics you add, are yours to declare too. The demo’s Privacy Policy is a sample: edit it to match what your site does.
Does the site need JavaScript? A little. The pages are static HTML and CSS, and small scripts (no framework) play the motion — the blocks and words that rise as you scroll — and run the menu, the services filter and search, the tabs, the accordions, the outcomes’ index, the booking form’s dentists, the video and the forms. Every word and link is in the HTML, so search engines read the whole site. Visitors without JavaScript see every block in place.
Can I show dates in another format?
Yes. Post, review and legal dates (“Mar 12, 2026”) come from formatDate in src/lib/format.ts.
Will it work with Tailwind plugins, React or Vue components, or my component library?
Yes. It is a standard Astro + Tailwind CSS 4 project: add packages as usual, and a UI framework with
npx astro add react (or vue, svelte) if you want one. The design tokens are plain CSS variables, so other
libraries can read them.
How do I update to a new version of the template?
Download the new release and copy your src/content/, src/assets/images/, public/ and your theme.css into it.
Then re-apply any component changes you made. CHANGELOG.md lists what moved.
Can you customise it for me, or build my site? Yes. Marcframe, the studio behind this template, updates templates to your needs (brand, content, new pages and features), builds custom templates and designs new websites. Get in touch at marcframe.com/contact or hire us on Contra.
Something is broken and none of this helps. Support and updates: https://framebrick.co/support. Send the page, the browser, and the error text or a screenshot: it makes the answer much faster.