Troubleshooting — Lookis 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, a plain string where an image needs src and alt). The message names the collection, the item and
the field, for example portfolio → downtown-vows data does not match collection schema and summary: Required.
npm run check finds the same thing faster.
The build stops on a rich-text block.
The collections’ details and content accept paragraphs only: { "type": "paragraph", "text": "…" }. A heading or a
list block is refused until you widen the schema (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 /portfolio/downtown-vows).
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.
The build stops after I added an icon.
A new icon in src/design-system/components/icons/paths.ts must also be added to icons in
src/components/style-guide/tokens.ts (npm run check reports it), or delete the style guide
(Making it look like your brand).
/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] <your notification title> could not be delivered; 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 form says “Thank you” but nothing arrives.
With no PUBLIC_FORM_ENDPOINT and no PUBLIC_FORM_MODE, the form runs in demo mode: it logs the fields in the browser
console and sends 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).
“Book a session” or “Schedule a call” opens cal.com.
Those are the demo’s placeholders: put your own booking page (or /contact) in hero.primary.href in
src/content/pages/home.json, and in bookingHref and footer.action.href in src/content/site.json
(Editing the content).
The clock in the header shows the wrong time.
It shows the time of owner.timeZone in src/content/site.json, not the visitor’s: set your own
IANA time zone (Europe/Paris, Asia/Jakarta…). The
clock is hidden on tablets and phones until the phone menu opens.
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 name, the slideshow, 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). The words fade in without rising, the name stands still and the slideshow moves only when its arrows are pressed.
Portfolio shows only four projects. That’s on purpose: four more appear each time the visitor scrolls close to the spinner under the list, and a tab starts again at four. Every project is in the page’s HTML from the start. To change the number, see Making it look like your brand.
A new project isn’t first on Portfolio or Home.
The site doesn’t sort by date: it shows the projects in the order of src/content/collections/portfolio.json, newest
first in the demo. Put the new project at the top of the list.
A project is missing from its tab, or its page has no “Service”.
Its service must be the slug of a service in services.json, spelled the same (weddings-elopements, not “Weddings
& Elopements”).
“Related Projects” is missing under a project.
No other project has the same service, and the section is left out then.
A filter tab shows no project.
Every service gets a tab on Portfolio, in the order of services.json; a service no project points to has an empty tab.
Give it projects, or remove the service.
I changed the numbers (or a heading) and another page still shows the old one.
Home and About each hold their own copy of the four numbers, and Home, Portfolio and Services their own headings: change
them in each file (Pages and sections). The testimonials and “See what I do” come
from one file, src/content/pages/shared.json.
The awards open a placeholder site.
Each award’s href in src/content/pages/about.json is the demo’s: link the real page of the award.
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 or a section? 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<HomeFactsSection … />(the numbers) insrc/pages/index.astro, or<ShowcaseSection … />on any page.
Can I change the fonts 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. Then set lang and og:locale in src/layouts/Layout.astro,
the date format in src/lib/format.ts ("en-US"), the clock’s in src/components/site/clock.ts, and the two interface
words, “Main” 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. 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) play the motion — the name ticker, the introduction’s words, the slideshow, the hovers — and run the phone menu, the clock, the Portfolio filter and its loading, the questions and the form. 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 project on Portfolio; the clock stays empty and the filter tabs do nothing.
Can I show dates in another format?
Yes. The project dates (“Apr 14, 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.