Skip to content
Sign inJoin waitlist

Fitbricks documentation — HTML

Everything you need to take Fitbricks for HTML 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
Editing the site Opening the site, where everything is, text, images, the program videos, adding programs, clubs, trainers and posts, the legal pages, adding and removing pages
Pages and sections Every page with a map of its sections, how the pages link to each other, the header, what search engines see
Making it look like your brand How the styling works, rebuilding the stylesheet, colours, the logo and icons, fonts, sizes and spacing, motion
Forms Connecting the contact, free-trial and booking forms to a form service or webhook
Editing without touching HTML Editing without touching HTML: a visual editor, a git-based CMS, or the Astro edition
Going live Pre-launch checklist, what to upload, hosts, your domain, after launch
Troubleshooting and questions Problems, questions and answers
  • 16 kinds of page, 103 addresses:
    • Home (index.html), About, Programs (program.html), Clubs (club.html), Trainers (trainer.html), Blog, Free Trial, Contact and the 404 page;
    • a page for each of the 20 programs (program/), 5 program categories (program-category/), 30 clubs (club/), 10 cities (city/), 12 trainers (trainer/), 16 posts (blog/) and 2 legal texts (legal/).
  • 3 forms: contact, free trial and the booking form on every club page, posting to any form service or webhook you choose.
  • Lists that load as you scroll: Programs, Clubs, Trainers and Blog show their first cards, then more as the visitor scrolls; every card is in the HTML, so search engines find them all and visitors without JavaScript see them all.
  • A video on every program page that loads from YouTube only when the visitor presses play.
  • Motion from the original design (the hero’s entrance, the quote slider, the stories ticker, blocks that rise in, cards that reveal their details), with reduced-motion support, and a style guide of every component in style-guide.html.
  • Search and sharing: a title, a description and a canonical link for every page, share cards, icons, sitemap.xml and robots.txt.
  • Placeholders to replace:
    • every photo in assets/images/ is a grey placeholder that shows its size (the demo uses photos from Unsplash and Pexels, which can’t be sold with a template), and so is the share image; the four app screens (app-*.png, feature-app.png) are drawn for the template and ship as they are;
    • the program videos are other creators’ YouTube videos, kept as examples;
    • the gym, Waras, is made up: its logo, name, @warasfit.com e-mails, phones and addresses; the footer’s e-mails use example.com;
    • the legal pages are sample texts with a placeholder, [Your Country/State];
    • the App Store and Google Play badges link to the stores’ home pages.
  • These docs (docs/), CHANGELOG.md and LICENSE.md.
  1. Open index.html in your browser, or run npx serve . in the folder and open the address it prints.
  2. Replace https://fitbricks-html-framebrick.vercel.app with your domain in every file, and the demo’s gym name, e-mails, phones, address and social links, with your editor’s find and replace in files (Editing the site).
  3. Replace the images in assets/images/ (keep the file names and you are done): the programs, the clubs and their galleries, the facilities, the trainers, the posts and the photos of Home and About (Editing the site).
  4. Replace the logos assets/images/logo-light.svg, logo-dark.svg and logo-black.svg, the browser icons (icon.svg, apple-icon.png) and the share image (opengraph-image.png).
  5. Replace the program videos with your own (Editing the site), point the app badges at your app or remove them, and have the legal pages written for your business (Editing the site).
  6. Point the forms at your inbox in assets/js/config.js: Forms.
  7. Upload the folder: Going live.

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

  • Every page is a file. What you see in the browser is in that page’s HTML: the words, the links, the cards. Blocks that repeat on many pages (the header, the footer, the CTA band, the trainers band) are copied into each file (Editing the site).
  • Lists are written out. Home, Programs, Clubs, the city and category pages, Trainers, Blog and the “other” lists of each page hold copies of the cards; adding an item means adding its card where it should show (Editing the site).
  • Design is Tailwind classes. The colours, breakpoints and font are tokens in src/css/style.css; the stylesheet assets/css/style.css is built from it and the classes in the pages (Making it look like your brand).
  • One script. assets/js/main.js runs the header, the sliders, the lists that load on scroll, the videos, the FAQ and the forms; assets/js/config.js holds your settings.