Skip to content
Sign inJoin waitlist

Troubleshooting — Brickfolio Next.js

Most problems with this Next.js template come from a content typo, a missing image, an anchor 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 Inter” (or Fragment Mono). 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 … A content item lacks a field that src/content/types.ts requires. Your editor names the file and the line; add the field. A gallery image needs its visible.

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: 3 : 2 on a project or post page, a fixed height on the 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 header link doesn’t scroll to its section. The link’s href in navigation (src/content/site.ts) must match the section’s id in src/content/pages/home.ts: #project goes to the section whose id is project.

The profile card stops sticking before the end of Home. You added or removed a block of Home’s column: change lg:row-span-11 on <Profile> in src/app/page.tsx to the number of blocks beside it (Pages and sections).

A form says “Something went wrong”. A field is missing or 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” 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).

“More Posts” is missing under a post. No other post has exactly the same category; the block and its line are left out then. Check the spelling.

Home shows only four projects or four posts. That’s pageSize in src/content/pages/home.ts; “More Projects” and “More Posts” show the rest, four at a time.

A new post isn’t first. Posts are sorted by date, newest first: check the post’s date ("2026-11-02", year, month, day). Projects keep the order of projects.ts: put a new one at the top to show it first.

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 tickers or the roles don’t move. 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).

Vercel doesn’t deploy when I push. If the folder has a vercel.json with "git": { "deploymentEnabled": false }, automatic deployments are 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, a section or the blog? Yes:

  • the style guide: delete src/app/style-guide/;
  • a section: delete its line in src/app/page.tsx (Pages and sections);
  • the blog: delete <Blog … />, its link in navigation, src/app/blog/ and the posts in src/app/sitemap.ts.

Can I have a page that lists every project or every post? Not built in: Home lists them four at a time. Add a page (Pages and sections) that maps getProjects() to ProjectCards, as src/components/sections/Projects.tsx does.

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

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 projects and posts.

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 and in src/lib/meta.ts), the date formats in src/lib/format.ts ("en-US"), and the interface words (“Main”, “out of 5”) listed in Editing the content. 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 fonts are served from your own domain. Anything you add (analytics, embedded videos) is yours to declare.

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 icon 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.