Skip to content
Sign inJoin waitlist

Troubleshooting — Balancee Astro

Most problems with this Astro template come from a typo in a content file, a missing image, or a setting not rebuilt into the site. Those answers come first.

Then come the questions buyers ask most.

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 image written as a plain string instead of { "src": …, "alt": … }, a rich-text body that is not a list). The message names the collection, the item and the field, for example posts → the-future-of-ai-opportunities-and-challenges data does not match collection schema and excerpt: Required. npm run check finds the same thing faster.

The build stops on a rich-text block. A block of a post’s, legal page’s or case study section’s body has a type other than heading, paragraph or list, or a list whose items are not lists of blocks (each item is [{ "type": "paragraph", "text": "…" }], in square brackets) (Editing the content).

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 (Caught error rendering /blog/…). Videos are the exception: they go in public/ (Editing the content).

The build stops after I deleted a case study. Home’s caseStudies in src/content/pages/home.json names case studies by slug (cards, spotlight, recent). A slug that no longer exists stops the build: replace it with one that does (Editing the content).

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.

A new page’s classes have no effect in npm run dev. The development server adds a new file’s Tailwind classes by itself (src/integrations/rescan.ts); if a style is still missing, save the file once more or restart npm run dev. The build always has them.

/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.

The 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 message from the Balancee contact form could not be delivered (your notification title); 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). The footer’s box says “Try again” instead.

The 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 form won’t send and a field turns red. Name, Company and Email are required, and the e-mail must look like an address (“Please enter a valid email address.”). The other fields can be empty unless you made them required.

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).

A service is missing from the form’s choices, or an old one is still there. The choices of “I’m interested in …” are written in src/content/pages/shared.json (contactForm.fields.service.options), not read from services.json: edit that list (Forms).

The videos don’t play, or play someone else’s clip. In the demo they play from the Pexels website; with no connection, or if Pexels moves the file, the poster stays. Put your own clips in public/ and their paths in video.src (Editing the content). With “reduce motion” switched on in the system, the hero video and the About clip stay on their poster on purpose.

The “Contact us” button is missing on a tablet. It shows from desktop width (1200 px) and at the end of the phone menu; on tablets the header holds the logo and the links (Pages and sections).

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 ticker, the video. 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).

The Blog or the Portfolio shows only four items. That’s on purpose: four more appear each time the visitor scrolls near the end of the list. Every item is in the page’s HTML from the start. To change the number, set list.pageSize in src/content/pages/blog.json or portfolio.json.

A new post isn’t first on the Blog or Home. The site 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.

“Other blogs” is missing under a post. No other post has the same category (spelled exactly the same), and the section is left out then.

I changed the numbers (or the social links, or my e-mail) and another place still shows the old one. Some details have a copy in more than one file: the figures in home.json, about.json and each case study, the booking link in two places of shared.json, the e-mail in site.json and in the texts you wrote (Pages and sections).

The legal pages say “[Your Company Name]”. They are samples: write your own texts in src/content/collections/legal.json (Editing the content).

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 or a section? Yes:

  • the style guide: delete src/pages/style-guide.astro and src/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 <HomeTestimonials … /> in src/pages/index.astro.

Can I change the fonts to my brand’s? Yes: Making it look like your brand.

Can I add more case studies, services or posts? Yes: copy an entry in its collection and edit it (Editing the content). Add a new service to the form’s choices too.

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 take online bookings? The contact form sends a message; you answer it yourself. “Let’s talk” and “Book a Free Consultation” open https://cal.com/ in the demo: point consultation.link.href and ctaBand.secondary.href in shared.json at your own scheduling page (Cal.com, Calendly, Acuity…).

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 interface words “Main”, “Mobile” and “Menu” 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 and loads no third-party scripts: the font is served from your own domain. The demo videos come from the Pexels website until you replace them. Any analytics you add are yours to declare.

Does the site need JavaScript? A little. The pages are static HTML and CSS, and small scripts (no framework) run the phone menu, the case study accordion, the logo slideshow on phones, the video players, the lists that load more as you scroll 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 and every post and case study on the lists.

Can I show dates in another format? Yes. The dates (“Feb 21, 2024”) come from formatDate in src/lib/format.ts.

Can I sell a site I build with this? Building sites for clients is what the licence is for; reselling the template itself as a template is not. The licence has the exact wording.

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.