Skip to content
Sign inJoin waitlist

Troubleshooting — Semono Next.js

Most problems with this Next.js template come from a content typo, a missing image 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 Inter”. The font is 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 font 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 … 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.

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 is cropped in the wrong place. Every photo sits in a frame and is cropped to fill it (from the centre; the team portraits from the top), 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 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).

The build stops after I added an icon. The style guide lists every icon on purpose, so a new one must be added to icons in src/app/style-guide/tokens.ts, or delete src/app/style-guide/ (Making it look like your brand).

A form says “Something went wrong”. 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] New contact inquiry could not be delivered (or “New consultation request”, “New job application”). Check that the environment variables are set for the environment you deployed to, that FORM_PROVIDER names a provider that exists, and redeploy after adding them.

A form says “Thank you” 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). If you added a field named fax, rename it: that name is the hidden spam trap, and a submission that fills it is dropped.

“Book a free consultation” opens cal.com. The button under the process tabs on Home is the demo’s placeholder: put your own booking page (or /contact) in process.book.href in src/content/pages/home.ts. The button of the same name at the end of a service page is the form’s submit button (consultationForm.submit in src/content/pages/service.ts).

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 header is transparent, with white text, all the way down Home. On Home the header turns light at the section marked headerSwitch, “About Semono”. If you removed it, put headerSwitch on the section that should take over (Pages and sections).

A page I added starts under the header, or runs under it. Pages start below a spacer of the header’s height. A page whose first section carries data-header-cover runs under the header instead, with a transparent header over it (Pages and sections).

The pages don’t slide when I follow a link. The page change uses the browser’s View Transitions: a browser without it, a visitor who prefers reduced motion, a click with a modifier key, a link that opens in a new tab and a link to the same page all navigate normally (Making it look like your brand). To switch it off for everyone, delete <RouteTransition /> from src/app/layout.tsx.

Nothing moves: the ticker, the words, the blocks. 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). Blocks and words fade in without rising, and the logo ticker stands still.

A video does not play. Nothing plays by itself: the card plays its clip when it is pressed (tapped, on a phone), muted and in a loop. If pressing does nothing, the file can’t be loaded: check src in video (Editing the content): /videos/intro.mp4 for a file in public/videos/, or a working address, and an MP4 the browser can play. The demo’s clips come from Pexels’ servers, are not part of the download, and may move: replace them with your own. A poster from another address needs its host in images.remotePatterns in next.config.ts.

Services, Testimonial or Blog show only four (or six) items. That’s on purpose: more appear each time the visitor scrolls close to the spinner under the list (four at a time; the Blog six at a time on desktop). Every item is in the page’s HTML from the start. To change the numbers, see Making it look like your brand.

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.ts, newest first in the demo. Put the new post at the top of the list.

“Related articles” 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 testimonial shows in the wrong place on Home, or the cards look different from what I expected. The testimonials are read by position: the first is the client story in “Why Choose”, the third the quote on About, the fourth the quote beside the services on Home, and the look of each card of the grid follows its position (Editing the content).

The Contact form offers services I don’t have. Its “Service Required” list is typed in contactForm.fields.service.options in src/content/pages/contact.ts, and includes two choices that are not services (“Process Optimization”, “Organizational Growth”). Make it match yours.

A legal link in the footer leads to the 404 page. footer.legalLinks in src/content/site.ts are typed addresses: /legal/<slug> must match a slug in src/content/collections/legal.ts.

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, a whole page, a section or a video? Yes:

  • the style guide: delete src/app/style-guide/;
  • a page: see Pages and sections;
  • a section: delete its line in the page file, for example <CtaBandSection … /> (the photo band with a call to action) in src/app/page.tsx;
  • a video: Editing the content.

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 in src/app/layout.tsx (and locale in its openGraph), the date format in src/lib/format.ts ("en-US") and the two interface words, “Main” and “Menu”, in src/components/site/Header.tsx. 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. Two things are yours to declare: the demo’s video clips, which are fetched from Pexels when pressed (replace them), and any analytics you add. The demo’s Privacy Policy mentions cookies and analytics: edit it to match what your site does.

Can I show dates in another format? Yes. Post and legal dates (“May 20, 2026”) 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, 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.