Skip to content
Sign inJoin waitlist

Editing without touching HTML — Fitbricks

Fitbricks’ HTML edition has no admin panel: programs, clubs, trainers, posts and every other text are written into the pages, and you edit files (Editing the site).

When someone who doesn’t write HTML needs to publish, the options are the same for every Framebrick template: keep editing the files (GitHub’s web editor works too), a visual editor such as CloudCannon, or an edition built for a CMS. They are explained in Edit HTML templates without touching HTML. This page lists what is specific to Fitbricks, for whoever sets that up.

For a gym that changes its programs, clubs and timetable often, the Fitbricks Astro or Fitbricks Next.js edition is the shorter road: the same design, with every collection below in data files, every list built from them, and a documented path to Sanity, Payload, Strapi, Directus or any headless CMS. In this edition a new club is a page plus its card in up to five lists.

The repeated content of the site, and the fields each item shows:

Collection In the demo Fields Pages
Program 20 name, category, level (easy, medium, hard), duration (minutes), instructor, subtitle, photo, YouTube video, about (rich text), benefits (list), details (list), plans (name, text, price per month, what’s included) program/<slug>.html, Programs, its category’s page, Home (the first six), the footer (the first five), Free Trial’s “Preferred Class” (the first ten), the clubs and trainers that list it, the “other programs” lists
Program category 5 name, colour, symbol, description program-category/<slug>.html, the category filter and “All Class”, every program card’s chip
City 10 name city/<slug>.html, the city filter, Free Trial’s “Preferred Location”, every club card
Club 30 name, city, area, photo, gallery (four photos), about (rich text), facilities, programs, address, map link, phone, e-mail, opening hours (weekdays, weekends) club/<slug>.html, Clubs, its city’s page, Home and Contact (the first six), “More in” and “Other Club Location”
Facility 14 name, description, photo The Facilities list of the clubs that have it
Trainer 12 name, title, summary, portrait, about (rich text), programs, e-mail, phone, social links trainer/<slug>.html, Trainers, the trainers band (the first three), “Other Trainers”
Post 16 title, category (a label), date, excerpt, cover, text (rich text) blog/<slug>.html, Blog, Home (the six newest), “Recent posts”, “Related Articles”
Legal page 2 title, update date, lead, description for search engines, text (rich text) legal/<slug>.html, the footer

Members’ stories, the hero’s quotes, the coaching goals, the app’s features, the FAQ and the About facts are page copy, not collections.

In the HTML each place holds a copy; in a CMS these become references and rules:

  • a program belongs to one category: its card shows the category’s name, colour and symbol, and the category page lists it; “Default” is a category with a page and no programs, left out of the filter;
  • a club belongs to one city and lists its facilities and its five programs in its own order; a trainer lists the programs they teach;
  • lists follow the collection’s order: Programs, Clubs, Trainers, the category and city pages, Home’s clubs and programs (the first six), the footer (the first five programs), the trainers band (the first three), “Other Club Location” (the first six clubs of the other cities), “Other Programs” (the first six of the other categories);
  • posts are newest first: Blog, Home (the six newest), “Recent posts” (the six newest others), “Related Articles” (the newest others of the same category, up to six).

Post texts use a small set of HTML: paragraphs, headings (<h2> and <h3>) and bulleted lists. Legal texts use paragraphs, <h2> headings, bulleted lists and <strong> for bold. Program, club and trainer texts are paragraphs, and a program’s benefits and details are bulleted lists. There are no tables, images or quotes inside the text.

Every photo sits in a frame and is cropped to fill it, so a photo of other proportions works; use images at least as large as the layout needs:

Image Size
A program’s photo (cards, its cover, the share image) 1920 × 1280 (3 : 2)
A club’s main photo (cards, its page, the share image) 1200 × 800 (3 : 2)
A club’s gallery photo 800 × 533 (3 : 2)
A facility’s photo 400 × 267 (3 : 2)
A trainer’s portrait 800 × 1200 (2 : 3)
A post’s cover 1200 × 800 (3 : 2)
A category’s symbol SVG, white on the category’s colour