Skip to content
Sign inJoin waitlist

Troubleshooting — Goeboek Next.js

Most problems with this Next.js template come from a content typo, a missing image, a slug that no longer matches or a form variable not set on the host. 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 20.9 or newer.

Port 3000 is already in use. npm run dev -- -p 3001, or stop whatever holds the port.

npm run dev or npm run build stops with “Failed to fetch font Plus Jakarta Sans” (or Inter). The fonts are downloaded from Google Fonts when the site builds (and the first time the development server runs), and the message ends with “Please check your network connection”. Connect, check your proxy or firewall, and run it again. To build without that download, host the fonts yourself with next/font/local (Making it look like your brand).

Module not found: Can't resolve '@/content/…' The path or the file name is wrong. @/ means src/, so @/content/site is src/content/site.ts. File names are case-sensitive on the servers that build your site, even when they are not on your laptop.

Property 'x' is missing in type …, or Type '"…"' is not assignable to type '"rent" | "sell"'. A content item lacks a field that src/content/types.ts requires, or a field has the wrong kind of value (an image written as a plain string instead of { src, alt }, a price or size written in quotes, a for other than rent or sell). Your editor names the file and the line; fix the field.

Cannot find name 'PageProps' (or 'LayoutProps') from npx tsc --noEmit. Next.js generates those types into .next/. Run npm run dev or npm run build once (or npx next typegen), then check again.

An image does not appear. The file must be in public/images/ and the content must refer to it as /images/<file>: same spelling, same extension, no public in the path. A photo from another address needs its host in images.remotePatterns in next.config.ts.

A photo is cropped in the wrong place. Every photo sits in a frame and is cropped to fill it, from the centre: wider than tall on the property cards and pages, taller than wide on the post cards. Keep the subject in the middle (Editing the content).

The build fails but npm run dev was fine. The build is stricter: it checks the types and renders every page. Read the first error, not the last; it names the file. A common cause is a missing field in a content item (the development server doesn’t check types).

A card shows “No Name”, “No Location” or “Uncategory”. The property’s agent, location or category doesn’t match the slug of an item in agents.ts, locations.ts or categories.ts. Check the spelling: slugs are lower case with hyphens (staten-island).

A new property doesn’t show on Home. Home’s slideshow shows the first four properties of properties.ts and Featured the next six. Move the new one up the file (Editing the content).

“Related properties” or “More in …” is empty on a property page. No other property has the same category and type (for), or the same location. The Related block keeps its title and “More Property”, as in the original design (the demo’s Marble House shows none).

A form says “Something went wrong”. A required field is empty or the e-mail isn’t an e-mail address, the provider rejected the request, or a variable is missing. The reason is in your host’s function logs (Vercel: the deployment’s Logs tab), after [forms] … could not be delivered. Check that the environment variables are set for the environment you deployed to, that FORM_PROVIDER names a provider that exists (console, webhook, mailchimp, resend), and redeploy after adding them.

A form says “Thank you” (or opens its thank-you page) but nothing arrives. With FORM_PROVIDER=console (the default, also when the variable is missing) submissions are only written to the server log: set a provider (Forms). With Mailchimp’s default status, transactional, the contact is in your audience but not subscribed to campaigns (Forms).

The video or the map is blank. A property’s video must be a YouTube link (https://www.youtube.com/watch?v=… or https://youtu.be/…); without one the Video block is left out. The Contact map searches Google Maps for map.query in contact.ts: write an address Google can find. Both need the visitor to be online and not blocking those services.

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 slideshows don’t move. The visitor’s system (yours, if you see it) has “reduce motion” switched on, and the site honours it: the slides change only with the arrows and dots (Making it look like your brand).

Vercel doesn’t deploy when I push. vercel.json holds "git": { "deploymentEnabled": false }, which turns automatic deployments off: delete the entry (Going live).

An AGENTS.md or a CLAUDE.md appeared in the project. Next.js 16.4 adds them when npm run dev runs next to an AI coding assistant (Install and run). Keep or delete them; the site doesn’t use them.

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, the blog or the Add property page? Yes:

  • the style guide: delete src/app/style-guide/;
  • the blog: delete src/app/blog/, <LatestPosts … /> on Home, the links to /blog in site.ts and the posts in src/app/sitemap.ts;
  • Add property: delete src/app/add-property/ and src/app/success-add-property/, the header’s “Add Property” in headerActions and their lines in the sitemap (Pages and sections).

Can the filter combine choices (a location and a price range)? Not built in: the filter is a list of links to the listing pages, one choice at a time, as in the original design, so every listing is a real page that search engines find. A combined filter needs a client component that hides the cards that don’t match, or a search service.

Can I mark which properties are featured? Home takes them by position: the first four in the slideshow, the next six in Featured. Order properties.ts (or your CMS) accordingly, or add a featured field to Property in types.ts and filter by it in src/app/page.tsx.

Can Home have a share image? Yes. The original design has none, so Home shares its title and description only. Put an image in public/ (1200 × 630 or larger) and pass it to the home page’s pageMeta in src/app/page.tsx: openGraph: { images: [{ url: "/opengraph-image.png", width: 1200, height: 630, alt: "…" }] }. pageMeta then gives it the large card, as it does for the properties and posts.

Can I change the currency or the units? The price is a number shown with a dollar sign by formatPrice in src/lib/format.ts; change it there. The size unit (“m2”) is propertyCard.sizeUnit in sections.ts and sizeUnit / heightUnit in property.ts.

Can I add a dark theme? The design is light only. The colours are tokens (Making it look like your brand), so you can change them, but the translucent blacks are written on the components (bg-ink/3, border-ink/5) and would need a second set.

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 listings (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 in src/app/layout.tsx (and locale in its openGraph and in src/lib/meta.ts), the date and number formats in src/lib/format.ts ("en-US"), and the interface words listed in Editing the content. The template has no language switch or language-based routing.

Does the site need a cookie banner? The template sets no cookies of its own and serves its fonts from your own domain. The property pages embed YouTube and the Contact page embeds Google Maps, and those services can set cookies; anything you add (analytics) is yours to declare too. Check what your visitors’ country requires.

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, shadcn/ui, or my component library? Yes. It is a standard Next.js + Tailwind CSS 4 project; add packages as usual. 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/, public/, your icons 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.