Skip to content
Sign inJoin waitlist

Troubleshooting — Marai Neesu 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.

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 (text where a number is expected, such as a testimonial’s rating). The message names the collection, the item and the field, for example projects → my-project data does not match collection schema and summary: Required. 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 some 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 contact inquiry could not be delivered (or “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 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.

The footer’s clock shows the wrong time. It shows the time in footer.timeZone of src/content/site.json, not the visitor’s: write your city’s IANA time zone there ("Europe/Berlin"), and your city in footer.city.

A project’s service badge leads to the Services page instead of the service. The badge links to the url of the service whose title is the project’s service; the spelling and the capital letters must match. A name that matches no service links to the Services page.

“See more posts” is missing under a post. No other post has the same category (the spelling and the capital letters must match), and the section is left out then.

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.

The Blog shows only six posts. That’s on purpose: “Load More” under the list shows the rest. Every post is in the page’s HTML from the start. To show more at first, raise pageSize in src/content/pages/blog.json.

Home shows fewer products on a phone than on a laptop. That’s on purpose: six on desktops, four on tablets and three on phones (count, tabletCount and phoneCount of products in src/content/pages/home.json); the third post of Home and of “See more posts” is hidden on tablets.

The contact form offers services I don’t have. Its “I’m interested in” choices are the titles of src/content/collections/services.json: edit the services and the choices follow.

The header’s background stays light grey after I changed the Background colour. The header bar’s colour is written as rgba(246,246,246,…) in src/components/site/Header.astro and src/components/site/header.ts, so the scroll animation can fade it: change it there too (Making it look like your brand).

I changed “Work with Me” (or a list’s title) and another page still shows the old one. Each page’s file holds its own copy of the blocks several pages show: change it in each (Pages and sections).

Nothing moves: the tickers stand still, the questions open at once. 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).

“Go Back” takes me to the list instead of the page I came from. It goes back only when the previous page is on your site; a page opened in a new tab, from a shared link or from a search result goes to Projects, Products or Blog instead.

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 course? 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, and the <Divider /> before it) from the page file in src/pages/, for example <TestimonialsSection … /> in src/pages/index.astro;
  • the course: remove the Course page (Pages and sections) and the banner on Home, the course prop of <ProductsSection> in src/pages/index.astro.

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

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, including the menu’s labels (menuLabels in src/content/site.json) and the shared labels (src/content/pages/shared.json). Then set lang and og:locale in src/layouts/Layout.astro and the date formats in src/lib/format.ts ("en-US"). 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. Any analytics or embeds 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) play the motion — the hovers, the rolling texts, the header, the slideshow — and run the phone menu, the questions, the course modules, “Load More”, “Go Back”, the footer’s clock 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 the first six posts of the Blog.

Can I show dates in another format? Yes. Post dates (“Jul 8, 2024”) come from formatDate and project months (“June 2024”) from formatMonth, both 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.