Skip to content
Sign inJoin waitlist

Fitbricks documentation — Next.js

Everything you need to take Fitbricks for Next.js from the downloaded folder to a published gym or fitness club website. Read in this order, or jump to what you need.

Guide What it covers
Install and run Requirements, install, the commands, what is in each folder
Editing the content Editing text, images, programs, clubs, cities, trainers, posts, the legal pages, the videos and the demo gym — no CMS needed
Making it look like your brand Colours, the logo, fonts, text styles, spacing, motion, components, icons, the style guide
Pages and sections The header, the sections of every page with a map of each, adding, removing and reordering pages and sections
Forms Making the contact, free-trial and booking forms deliver to you
Using a headless CMS The collections and their fields, for connecting Sanity, Payload, Strapi, Directus or any other headless CMS
Going live Pre-launch checklist, deploying, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers
  • 16 kinds of page, 103 addresses in the sitemap:
    • Home, About, Programs (/program), Clubs (/club), Trainers (/trainer), Free trial, Contact, Blog and the 404 page;
    • a page for each of the 20 programs, 5 program categories, 30 clubs, 10 cities, 12 trainers, 16 posts and 2 legal pages, built from the collections.
  • 8 collections in src/content/collections/: programs (20), program categories (5), cities (10), clubs (30), facilities (14), trainers (12), posts (16) and legal pages (2).
  • 3 forms: contact, free trial and the booking form of every club page, with a server action each and four ways to deliver them (a log, a webhook, Mailchimp, Resend).
  • Lists that fill themselves: Home shows the first six clubs and programs and the six newest posts; a program page the other programs of its category and of the others; a club page the clubs of its city and of other cities; a post “Recent posts” and “Related Articles”; Programs, Clubs, the cities, Trainers and Blog load more items as the visitor scrolls.
  • Motion from the original design (the hero’s appear effects, the member quotes, the stories ticker, cards whose actions rise on hover, the FAQ, the header changing as you scroll), with reduced-motion support, and a style guide of every component at /style-guide.
  • Search and sharing: a title, a description and a canonical link for every page, share cards, icons, sitemap.xml and robots.txt.
  • Placeholders: the photos in public/images/ and the share image are grey placeholders that show their sizes (the demo uses photos from Unsplash and Pexels, which can’t be sold with a template). The app screens are the template’s own art. The gym, Waras, is made up, and the program videos are other creators’ YouTube videos: replace both (Editing the content).
  • These docs (docs/), the forms guide (Forms reference), the design system’s reference (Fitbricks design system), CHANGELOG.md and LICENSE.md.
Terminal window
npm install
npm run dev
  1. Open http://localhost:3000.
  2. Put your site’s name, title, description and domain in src/content/site.ts, and your menu, header button, CTA band, app badges, social links and footer in the same file.
  3. Replace the images in public/images/ (keep the file names and you are done): the hero, the programs, the clubs and their galleries, the facilities, the trainers, the posts and the page photos (Editing the content).
  4. Replace the logos public/images/logo-*.svg (Making it look like your brand), the browser icons in src/app/ (icon.svg, apple-icon.png) and the share image (public/opengraph-image.png).
  5. Write your programs, clubs, cities, trainers and posts in src/content/collections/, and the page copy in src/content/pages/. Search for “Waras” (in any case): the demo’s gym is named in many places.
  6. Replace the program videos (Editing the content) and have the legal pages written for your business (Editing the content).
  7. Point the forms at your inbox or your tools: Forms.
  8. Deploy: Going live.

Nothing else is required: the site has no database, no account to create and no paid service to run.

  • Content is data. All text and every collection item live in src/content/. Pages read the collections through src/lib/content.ts, which is why swapping in a CMS later touches one file, not the whole site.
  • Design is tokens. Colours, breakpoints and easing curves are in src/design-system/theme.css; text styles and transitions in src/design-system/tokens/. Change a token and every page follows (Making it look like your brand).
  • Components are shared. Every button, card, form field and section is in src/design-system/ or src/components/, and is shown at /style-guide on your own site.
  • Blocks are shared too. The CTA band, the trainers band, the header and the footer appear on many pages from one copy (Pages and sections).