Troubleshooting — Kalme Next.js

Most problems come from a content file with a typo, a missing image or a form variable that was not set on the host. The answers below cover those first, then the questions buyers ask most.

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 node -v is 20.9 or newer.

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

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 … A content item lacks a field that src/content/types.ts requires. Your editor names the file and the line; add the field or mark it optional in the type.

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 project’s service tag leads to “404”. The tag links to /services/<slug>: the slug in the project’s services must be the slug of a service in services.ts (Editing the content).

The pricing card has no Weekly / Monthly switch. The switch appears when a service has two or more plans; with one plan the card shows only its price.

The build fails but npm run dev was fine. The build is stricter. Read the first error, not the last; it names the file. Common causes: a missing field in a content item, a link to a slug that no longer exists, an image path with a typo.

The form says “Something went wrong”. The provider rejected it. The reason is in your host’s function logs (Vercel: the deployment’s Logs tab). Check that the environment variables are set for the environment you deployed to, and redeploy after adding them.

The share image or title is the old one. Facebook, LinkedIn and X cache them. Use their debuggers to refresh, and confirm site.url is your domain.

A video does not play. The demo plays stock clips from the web; they are not part of the download and may move. Replace src with your own file (/videos/showreel.mp4 in public/videos/) or a link to one (Editing the content). Phones only autoplay videos that are muted, which the template’s videos always are.

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 video? Yes. Style guide: delete src/app/style-guide/. A page: see Pages and sections. The video under the Home hero: delete <PageVideoSection … /> from src/app/page.tsx (on About, from src/app/about/page.tsx).

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 show prices in another currency, or hide them? Prices are text in each service’s plans (price: "€450", note: "per week"), so write them as you like. To hide the pricing card, remove it from src/components/sections/ServiceContentSection.tsx.

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, copy your src/content/, public/images/, 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.