Going live — Fitbricks Next.js
Before the Fitbricks site goes public, replace the demo gym with yours, replace the program videos, have the legal pages written and point the forms at you; then deploy it to any Next.js host and check it again.
Replacing the demo gym means its name, logo, contact details, programs, clubs, trainers, posts and photos; pointing the forms at you means giving the contact, free-trial and booking forms 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 and meta.title in src/content/pages/home.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| Your gym instead of Waras: the name (“Waras”, “WARAS”), the copyright, the Instagram handle, the page copy, the FAQ, the page titles and descriptions | Search src/content/ in any case (Editing the content) |
Contact details: the e-mails (@warasfit.com, example.com), phone numbers and addresses are made up |
office in src/content/pages/contact.ts, ctaBand.office and footer.emails in src/content/site.ts, every club and trainer |
| Social links (they open the networks’ home pages), the trainers’ links, the Instagram grid’s link, the footer’s Career link | socials and footer in src/content/site.ts, trainers.ts, gallery in src/content/pages/about.ts |
| Claims and prices (“1,5K+”, “98%”, “$29/Month”, the plans) | src/content/pages/home.ts, about.ts, the programs’ plans |
| The program videos replaced: the demo’s are other creators’ YouTube videos | video of each program in src/content/collections/programs.ts (Editing the content) |
The legal pages written for your business (the samples hold [Your Country/State] and Waras’s details) |
src/content/collections/legal.ts (Editing the content) |
| The App Store and Google Play badges pointed at your app, or removed | appBadges in src/content/site.ts (Editing the content) |
| Your programs, categories, cities, clubs, facilities, trainers and posts | src/content/collections/ |
| Logos replaced | public/images/logo-light.svg, logo-dark.svg, logo-black.svg (Making it look like your brand) |
| Browser icons replaced | src/app/icon.svg, src/app/apple-icon.png |
| Share image replaced and described | public/opengraph-image.png, its description in src/lib/meta.ts |
| Placeholder photos and the demo app screens replaced | public/images/ |
| Page titles and descriptions written for your site | The meta of each file in src/content/pages/ |
| The forms deliver to you | Forms |
| 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 “Waras”, the sample e-mails and phone numbers, the demo videos or the sample legal texts 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 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.
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 menu on desktop, tablet and phone, and the header over the cover photos as you scroll;
- the hero’s quotes, the stories ticker or carousel;
- Programs and its category filter, Clubs and its city filter, Trainers and Blog loading more as you scroll;
- a program with its video and plans, a club, a trainer, a post;
- the footer’s links and legal pages.
- Write to yourself on the live site — a contact message, a free trial and a booking from a club page — and reply to a message.
- Verify the share card. Paste the URL of the home page and of a program into https://www.opengraph.xyz or a chat window, and confirm the image and title.
- 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 program, club, trainer or post is one entry in
src/content/collections/(a new post goes at the top ofposts.ts); see Editing the content. Connect a CMS (Using a headless CMS) if people who don’t use a code editor 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 page — every item of the lists that load on scroll too;
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards (posts as articles, with their date); - sized, lazy-loaded images that keep their space while they load, and YouTube players that load only when clicked.
Keeping the site fast is mostly about images. Export photos at the size they are shown, not the size your camera produced; the placeholders show the size each one was designed for.