Going live — Brickfolio Next.js
Before the Brickfolio site goes public, replace the demo’s person and work with yours and point the two forms at you; then deploy it to any Next.js host and check it again.
Replacing the demo means your name and photo, your texts, projects, services, posts, testimonials and CV; pointing the forms at you means giving them a destination. Once the site is deployed, click through the live address once more.
Before you deploy
Section titled “Before you deploy”| Where | |
|---|---|
Your domain in site.url (until you change it, it is the demo’s address) |
src/content/site.ts. Share links, sitemap.xml and robots.txt are built from it. |
| Name, title and description (they describe the template: write yours) | site in src/content/site.ts |
| Your name and photo instead of Javier Martinez’s: the profile card, the greeting and the roles | profile in src/content/pages/home.ts |
| Your name instead of “Brickfolio”: the logo, the copyright line | Search src/ for “Brickfolio” (Editing the content) |
The “Email me” address (hello@example.com is a placeholder) |
services.cta.buttons in home.ts, and site.email |
| Social links (they open the networks’ home pages) | social in src/content/site.ts |
| Your projects, services and posts (the demo’s are samples) | src/content/collections/ (Editing the content) |
| Your testimonials, experience, client logos and questions | src/content/pages/home.ts; the logos in public/images/ |
| Your CV | public/cv.pdf |
| Logo and browser icon replaced | Making it look like your brand |
| Placeholder photos replaced (projects, services, posts, testimonials, the profile) | public/images/ |
| The two forms deliver to you | Forms |
| A privacy page, if your country asks for one (the forms collect names, e-mails and phone numbers) | Pages and sections |
| Style guide kept or deleted | src/app/style-guide/ |
npm run lint and npm run build pass |
— |
The demo content is there to be replaced. Leaving the sample person, the sample e-mail, the sample testimonials or the sample CV on a live site is the most common mistake.
Deploy
Section titled “Deploy”The site is a normal Next.js app: it builds to pre-rendered pages and runs on Node.js, which also handles the two forms, so any host that supports Next.js works. It can’t be published as plain static files, because the forms need the server.
Vercel (made by the Next.js team, free for personal sites)
Section titled “Vercel (made by the Next.js team, free for personal sites)”- Push the project to GitHub, GitLab or Bitbucket.
- https://vercel.com/new → import the repository → Deploy. The framework, build command and output are detected.
- Add your form variables under Settings → Environment Variables, then redeploy.
- Settings → Domains → add your domain and follow the DNS instructions.
If your folder has a vercel.json with a git entry that switches off automatic deployments (the demo is deployed that
way), delete the entry if you want Vercel to deploy on every push.
Netlify
Section titled “Netlify”Import the repository, keep the detected settings (npm run build), add the environment variables, deploy.
Cloudflare
Section titled “Cloudflare”Cloudflare runs Next.js through the OpenNext adapter (@opennextjs/cloudflare); follow Cloudflare’s Next.js guide to
build and deploy with Wrangler.
Your own server
Section titled “Your own server”npm cinpm run buildnpm start # listens on port 3000Run it under a process manager (pm2, systemd) behind nginx or Caddy for TLS, or in a container: an LTS Node image such
as node:24-alpine, copy the project, build, CMD ["npm", "start"].
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the header’s links from Home and from a project page, and the menu on a phone;
- “More Projects” and “More Posts”, a project and a post with their close buttons;
- “Download CV”, the questions, the tickers;
- both forms.
- Send a message and sign up from the live site with your own address and check that both arrived.
- Verify the share cards. Paste the URL of the home page and of a project into https://www.opengraph.xyz or a chat window, and confirm the title and description (and, for the project, its cover). Home has no share image, as in the original design: to give it one, see Troubleshooting and questions.
- Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. - Analytics, if you want it. Add your snippet to
src/app/layout.tsx, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. A new project is one entry in
src/content/collections/projects.tsand its photos inpublic/images/; a new post is one entry inposts.tswith today’s date, and it shows first among the articles by itself (Editing the content). Connect a CMS (Using a headless CMS) if someone else will publish.
Performance and SEO
Section titled “Performance and SEO”The template ships with what search engines look for:
- pre-rendered HTML, with links in it to every project and post (the cards past the first four are in the page, hidden until “More” is pressed);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; - sized, lazy-loaded images that keep their space while they load, and alt texts on every photo.
Keeping the site fast is mostly about images. Export photos at the size they are shown, not the size your camera
produced (about 1600 px wide for the covers, 300 px for the service photos); the placeholders show the size of each demo
photo. next/image then serves each visitor a scaled, compressed copy.