Skip to content
Sign inJoin waitlist

Fitbricks documentation — Astro

Everything you need to take Fitbricks for Astro 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, categories, clubs, cities, facilities, trainers, posts and the legal pages — no CMS needed
Making it look like your brand Colours, the logo, the font, text styles, spacing, motion, components, icons, the style guide
Pages and sections The header and the footer, 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 (plus the 404 page and the style guide):
    • 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 (“Get in Touch”), Free trial (“Claim Free Trial”) and the booking form on every club page (“Book Your Class Now”), in demo mode out of the box, posting to a form service or webhook from any static host, or delivered by the site’s own route (a log, a webhook, Mailchimp, Resend).
  • Lists that fill themselves: a club lists its facilities and classes, a city its clubs, a trainer their programs, a program the others of its category; Home shows the first clubs, programs and posts; Programs, Clubs, a city, Trainers and Blog load more items as the visitor scrolls.
  • Program pages with the facts, a YouTube video, key benefits, details and two pricing plans.
  • Motion from the original design (the hero’s appear effects and member quotes, the testimonial ticker, numbers that rise into view, the header that hides and returns 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 (programs, clubs, trainers and posts share their own photo), icons, sitemap.xml and robots.txt.
  • Placeholders: every photo in src/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). The four app mock-ups are the template’s own art. The gym brand of the demo, Waras, is made up, and the program pages embed other creators’ YouTube videos as examples (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:4321.
  2. Put your name, description and domain in site in src/content/site.json, and your menu, socials, store badges and footer in the same file. Home’s browser title is meta.title in src/content/pages/home.json.
  3. Replace the images in src/assets/images/ (keep the file names and you are done): the programs, clubs, trainers, posts, the page photos and the footer’s grid (Editing the content).
  4. Replace the logo files src/assets/images/logo-light.svg, logo-dark.svg and logo-black.svg (Making it look like your brand), the browser icons in public/ (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” and “warasfit”: the demo’s gym is named in many places.
  6. Replace the YouTube videos of the programs, and have the legal pages written for your business (Editing the content).
  7. Point the forms at your inbox or tool: 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/. Collections are JSON files checked against src/content/schemas.ts; pages read them through src/lib/content.ts, which is why swapping in a CMS later touches one place, 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).
  • No framework in the browser. Pages are static HTML; the header, the sliders, the lists that load on scroll, the video and the forms are small scripts in src/design-system/scripts/ and src/components/site/, and hovers are CSS.
  • 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 header, the footer, the CTA band and the trainers band appear on many pages from one copy (Pages and sections).