Skip to content
Sign inJoin waitlist

Editing the content — Fitbricks Next.js

All the words and images of this Next.js template live in src/content/, in plain TypeScript files you edit while npm run dev shows the result.

No CMS is needed: text goes between quotes and items are separated by commas. If you would rather manage content in Sanity, Payload, Strapi or Directus, see Using a headless CMS.

src/content/
site.ts name, title, description, domain, logos, menu, the header's button, the CTA band, the
trainers band, the app store badges, socials, the footer
pages/home.ts the copy of the home page and the counts of its lists
pages/about.ts …and of every other page
collections/*.ts programs, program categories, cities, clubs, facilities, trainers, posts, legal pages
routes.ts the URL of every page
types.ts the fields each kind of item has

Not sure which file holds a piece of text? The page maps label every section of every page with its file.

src/content/site.ts holds what appears on every page:

Export Shown where
site.name The browser title suffix (“Programs | Fitbricks”), share cards
site.title The browser title of a page without one of its own (Home’s is meta.title in pages/home.ts)
site.description Search results and share cards of the home page, and of any page without its own description. It describes the template: write yours.
site.url Set this to your domain before publishing. Canonical links, share links, sitemap.xml and robots.txt are built from it.
logo The logo files: light (white, over photos and in the footer), dark (on the white header), their name for screen readers and where they link (Making it look like your brand)
navigation The menu in the header: Home, About, Programs, Trainers, Club, Blog
headerAction The header’s button, “Claim free trial”
ctaBand The band with a photo above the footer (“TAKE THE FIRST STEP TOWARD A STRONGER YOU”): title, text, the “Contact us” button, the main office and the photo
trainersBand “Expert Guidance. Real Results.” on About, Clubs and the city pages: eyebrow, title, text, how many trainers (count, 3), the cards’ label and the “All Trainers” button
appBadges The Google Play and App Store badges (Home’s app section and the footer): where they link and their light and dark images (below)
socials Instagram, Facebook, Twitter (X) and Youtube: the footer’s Social column
footer The tagline, the Contact e-mails, the four columns (Programs — the first five programs —, Pages, Resources — with the legal pages —, Social), the Instagram grid (four photos, the handle and its link) and the copyright ({year} becomes the current year)
controls The names screen readers hear for the menu, the quote dots, the carousel arrows and the footer

site.brand, header and the pages lists of ctaBand and trainersBand are notes from the original design; the site doesn’t read them. Which pages show the bands is set in each page’s copy (Pages and sections), and which pages put the header over a photo in src/content/routes.ts (Pages and sections).

The demo is the website of Waras, a gym chain that doesn’t exist. Its name, its logo, the e-mail addresses (…@warasfit.com), the phone numbers, the addresses of the head office and of every club, the members’ quotes and the numbers (“1,5K+”, “98%”, “30+ Clubs in 10 Cities”, the prices) are all made up; the footer’s e-mails use example.com. Replace every one of them before you publish:

  • the name: site.ts (the CTA band, the trainers band, the Instagram handle @waras, the copyright), the page copy (Home, About, Free trial, Contact and its FAQ, the page descriptions) and the collections (the program, club, category and legal texts). Search src/content/ for “Waras” in any case: it is also written “WARAS”;
  • the logos: public/images/logo-light.svg, logo-dark.svg and logo-black.svg, and the browser icons (Making it look like your brand);
  • the contact details: office in src/content/pages/contact.ts, ctaBand.office and footer.emails in site.ts, the address, phone, email and mapUrl of every club and the email and phone of every trainer.

The demo’s FAQ says “120+ clubs in 30 cities” where the rest of the site says 30+ clubs in 10 cities: write your own answers in faq of src/content/pages/contact.ts.

There is one file per page in src/content/pages/. Each exports the parts of that page and, for the pages with one address, a meta entry:

export const meta = {
"title": "About", // browser tab ("About | Fitbricks") and share card
"description": "At WARAS, we believe fitness isn’t…", // search results and share cards (80–160 characters)
};
export const eyebrow = "About Us";
export const title = "Building Stronger, Healthier Lives — Together.";

Change the text between the quotes, keeping the field names: the sections read them by name. Apostrophes are safe inside double quotes, and the demo uses the typographic ’. A double quote inside a double-quoted string needs a backslash before it.

Words in braces are filled in for each item: {name}, {category}, {city}, {description}, {title}, {summary}, {date}. Keep them where you want the value. Entries called rule describe how a list is filled; they are notes, and the numbers that count are count, countPhone, countSmall, pageSize and pageSizeSmall.

File Page
home.ts Home: its browser title (meta.title, used as it is, without the suffix); the hero (eyebrow, title, lead, two buttons, photo, three member quotes with their photos and the “1,5K+” line); the three facts; memberships with four feature cards; clubs (count, 6); personal training with four goals; the Pilates Reformer promotion; programs (count, 6); five members’ stories; the app’s three features; the blog (count, 6; countPhone, 4); ctaBand
about.ts About: eyebrow, title, lead, the photo with the logo, two facts and two photos; “Why Choose” with four cards; vision and mission; the gallery (six photos, the handle and its link); trainersBand, ctaBand
programs.ts Programs (/program): title block, the category filter (“{name} Class”, “All Class”), six programs at a time (list.pageSize), ctaBand
program-category.ts Every category page: “{name} Class” (also its browser title), the category’s description, the filter, list.pageSize (6), ctaBand
program.ts Every program page: the labels of its facts and levels, the “Start Your Free Trial” button, “Key Benefits”, “Program Details”, the plans (title, currency, period, “Includes:”, button), the sidebar (“Other Programs in {category} Class”, count 6; “All Class”), “Other Programs” (count 6, “View all classes”), the play button’s label
clubs.ts Clubs (/club): title block, “All” in the city filter, six clubs at a time, trainersBand, ctaBand
city.ts Every city page: its browser title and description patterns, the title block, six clubs at a time, trainersBand, ctaBand
club.ts Every club page: the titles and labels (About, Opening Hours, General Information, Facilities, “Popular Classes in {name}”), the booking form (Forms), “More in {city}”, “Other Club Location” (count 6)
trainers.ts Trainers (/trainer): title block, six trainers at a time on desktops (pageSize), four on tablets and phones (pageSizeSmall), ctaBand
trainer.ts Every trainer page: the browser title and description patterns, “Let’s Create Something Amazing”, “Follow me”, “My Fitness Programs”, “Other Trainers” (count 6, countSmall 4) and the social icons
free-trial.ts Free trial: the photo, eyebrow, title, text, “What’s Included:” and the form (Forms)
contact.ts Contact: title block, the main office, the customer service hours, the form, “Find Your Nearest Club” (count 6) and the FAQ (nine questions; the first one opens by itself)
blog.ts Blog: title block, five posts at a time (list.pageSize), “Read more”
post.ts Every post page: the breadcrumb’s “Blog”, “Recent posts” (count 6), “Related Articles” (count 6, countPhone 4)
legal.ts “Last Updated: “ on the legal pages, and their lead
not-found.ts The 404 page: its browser title, the photo, “404”, the title, the text and the button

A page shows the CTA band when its copy says export const ctaBand = true;, and the trainers band with export const trainersBand = true;. Set one to false to take the band off that page.

src/content/collections/ holds the lists the site builds pages and sections from:

File What it feeds
programs.ts One page per program; Programs; the category pages; Home’s programs; the free trial’s Preferred Class (the first ten); a club’s “Popular Classes”; a trainer’s programs; the footer’s Programs column (the first five)
program-categories.ts One page per category; the filter of Programs and the category pages; a program’s Class Type, its card’s colour and icon; the program page’s “All Class”
cities.ts One page per city; the city filter of Clubs; the free trial’s Preferred Location; the city on every club card
clubs.ts One page per club; Clubs and the city pages; Home’s and Contact’s clubs; “More in {city}” and “Other Club Location”
facilities.ts The Facilities of a club page (each club lists its own)
trainers.ts One page per trainer; Trainers; the trainers band (the first three); “Other Trainers”
posts.ts One page per post; Blog; Home’s blog; “Recent posts” and “Related Articles”
legal.ts One page per legal text: /legal/privacy-policy, /legal/terms-conditions, and their links in the footer’s Resources column

Every list keeps the order of its file, except posts: they are sorted by date, newest first (posts of the same day keep their order in the file). Home, Contact and the bands take the first items, so the order of the file decides which show. A new post with the latest date is the newest everywhere, wherever it sits in posts.ts.

Copy an existing entry, paste it, and change the values:

{
"slug": "boxing", // the URL: /program/boxing
"name": "Boxing", // the card, the page title, the browser title
"category": "cardio", // a slug of program-categories.ts: Class Type, the card's colour and icon
"level": "medium", // "easy", "medium" or "hard"
"duration": 45, // minutes: "45 min"
"instructor": "Certified Boxing Coach",
"subtitle": "Punch Harder, Move Faster", // over the text of the page
"image": { "src": "/images/program-boxing.jpg", "alt": "…" }, // the cover, the cards and the share image
"video": "https://www.youtube.com/watch?v=…", // a YouTube link (below)
"about": [ …rich text… ], // the first paragraph is also the search description
"benefits": [ …rich text… ], // "Key Benefits"
"details": [ …rich text… ], // "Program Details"
"plans": [ // "Choose Your Perfect Plan"
{ "name": "Standard Plan", "description": "…", "price": 55, "includes": ["…", "…"] },
],
}

The demo’s programs each have two plans; prices are whole numbers shown as “$55” “/month” (plans in src/content/pages/program.ts holds the currency and the period).

{
"slug": "my-club", // the URL: /club/my-club
"name": "My Club",
"city": "chicago", // a slug of cities.ts
"location": "River North", // the neighbourhood, before the city on cards
"image": { "src": "/images/club-my-club.jpg", "alt": "…" }, // the cover, the cards, the share image
"gallery": [ { "src": "…", "alt": "…" }, … ], // four photos under the cover
"about": [ …paragraphs… ], // "About My Club"; the first is the search description
"facilities": ["cardio-area", "locker-rooms"], // slugs of facilities.ts, in the order shown
"programs": ["hiit-burn", "zumba"], // slugs of programs.ts: "Popular Classes in My Club"
"address": "…", "mapUrl": "https://www.google.com/maps/…", // "Show on map" opens mapUrl
"phone": "+1 (555) 000-0000", "phoneHref": "tel:+15550000000",
"email": "myclub@yourgym.com", "emailHref": "mailto:myclub@yourgym.com",
"hours": { "weekdays": "6:00 AM – 10:00 PM", "weekends": "7:00 AM – 8:00 PM" },
}

Adding a trainer, post, city, category or facility

Section titled “Adding a trainer, post, city, category or facility”
Add Fields
Trainer slug, name, title (the role), summary (a line on the card), image ({ src, alt }), about (paragraphs), programs (slugs of programs.ts, in the order shown), email and emailHref, phone and phoneHref, socials (a list of { name: "facebook" | "instagram" | "x", label, href }; an href of null shows the icon without a link)
Post slug, title, category (a name, such as “Fitness Tips”: it is text, not a slug), date ("2025-08-18", shown as “Aug 18, 2025”), excerpt (the card and the search description), image ({ src, alt }: the card, the cover, the share image) and body (rich text)
City slug and name. Clubs join it through their city.
Program category slug, name, color (the card’s symbol and the filter’s square), icon (a white line icon, an SVG), description (its page’s text and search description)
Facility slug, name, description and image ({ src, alt }). Clubs list it by slug.

The posts’ four categories (Fitness Tips, Nutrition & Wellness, Mindset & Motivation, Member Stories) have no pages; a post’s “Related Articles” are the posts with exactly the same category text.

program-categories.ts ends with Default, as the original design does: it has a page, /program-category/default (“Default Class”), which lists no program, and it is left out of every filter. Its colour and icon mark “All Class”. Keep it, give it programs, or remove it (its page and sitemap entry go with it, and “All Class” falls back to the orange token).

Delete the entry. Its page and its sitemap entry disappear on the next build, and it leaves the lists. A club or trainer that lists a removed program or facility simply skips it. Move the programs of a category, and the clubs of a city, before you remove it: an item that names a missing slug shows the slug itself as its category or city name, and links to a page that no longer exists.

src/content/types.ts is the reference: it lists every field and a comment for the ones that are not obvious. Your editor shows the same information while you type.

No list has its own selection: each takes items from a collection by a rule, written next to its count in the page copy.

Block Rule Change it with
Home: clubs The first six clubs the order of clubs.ts; clubs.count in home.ts
Home: programs The first six programs the order of programs.ts; programs.count
Home: blog The first six posts (four on phones) the order of posts.ts; blog.count, blog.countPhone
Trainers band (About, Clubs, cities) The first three trainers trainersBand.count in site.ts
Footer: Programs The first five programs footer.columns in site.ts
Footer: Resources Blog, Career, then every legal page footer.columns; legal.ts
Contact: “Find Your Nearest Club” The first six clubs clubs.count in contact.ts
Free trial: Preferred Location / Class Every city / the first ten programs form.fields in free-trial.ts
Program: sidebar The other programs of its category (up to six) and every category but Default sidebar.count in program.ts
Program: “Other Programs” The first six programs of the other categories other.count
Club: “Popular Classes” and Facilities The club’s own programs and facilities, in its order the club’s entry
Club: “More in {city}” Every club of its city, this one included (as the original design) —
Club: “Other Club Location” The first six clubs of the other cities other.count in club.ts
Trainer: programs / “Other Trainers” The trainer’s programs / the first six other trainers (four on tablets and phones) the trainer’s entry / other in trainer.ts
Post: “Recent posts” The first six other posts recent.count in post.ts
Post: “Related Articles” The other posts of the same category, up to six (four on phones); hidden when there are none related in post.ts
Programs, a category, Clubs, a city, Trainers, Blog Every item, loading 6 (Trainers: 6 on desktops, 4 below; Blog: 5) at a time as the list’s end comes into view list.pageSize of each page

Every program page shows a video: the program’s video, a YouTube link (watch?v=, youtu.be/ or embed/). The page shows YouTube’s thumbnail with a play button and loads the player from youtube-nocookie.com only when the visitor clicks it.

The demo’s videos are other creators’ videos on YouTube, kept as examples of what goes there. They are not part of the template and don’t belong on your site: put the address of your own video (or one you have the right to show) in each program’s video before you launch. To leave the video out of every program page, delete the <YouTubeEmbed … /> line in src/components/sections/program/ProgramMainSection.tsx.

The Privacy Policy and the Terms & Conditions in src/content/collections/legal.ts are sample texts written for the demo gym, with Waras’s details and a placeholder, [Your Country/State]. They are not ready to publish as they are. Have them written for your business — what you collect through the forms, your memberships, your country’s law — and replace the texts. Each has a title, updated (the date shown as “Last Updated: May 6, 2025”), a description (the lead under the title), a metaDescription (the search description) and a body (rich text).

The footer’s Resources column links every legal page by its title.

Home’s app section and the footer show the Google Play and App Store badges from appBadges in src/content/site.ts. They link to the stores’ home pages. If your gym has an app, point href at its pages in the stores; if not, remove the badges (<StoreBadges … /> in src/components/sections/home/AppSection.tsx and src/components/site/Footer.tsx) or the whole app section from src/app/page.tsx. The badges belong to Apple and Google, whose guidelines say how they may be used. The app screens (app-*.png, feature-app.png) show the demo’s app: replace them with yours.

A program’s about, benefits and details, a club’s and a trainer’s about, a post’s body and a legal text’s body are a list of blocks:

"body": [
{ "type": "heading", "level": 3, "text": "Why Consistency Matters" },
{ "type": "paragraph", "text": "Plain text with a **bold** run and a [link](/free-trial)." },
{ "type": "list", "ordered": false, "items": ["First item", "Second item"] }, // ordered: true for numbers
]
  • Headings: posts use levels 3 and 4, the legal pages 3. Level 3 is drawn in the Heading 3 style and level 4 in Heading 4; they are rendered one level up (h2, h3) so they follow the page’s h1 in order.
  • Inline marks: **bold** and text links (an address starting with / stays on the site; https:// addresses open in a new tab; mailto: and tel: work too). A \n breaks the line. There is no italic.
  • Lists: each item is a line of text, with the same inline marks.
  • Clubs and trainers show only the paragraphs of their about; programs use paragraphs and lists.
  1. Put the file in public/images/.
  2. Refer to it in the content as /images/<file> (the path starts at public).

Sizes and formats are handled for you: pages use next/image, which serves a scaled, modern format per device. The download’s placeholders show the size each photo was designed for; use photos at least as large:

Photos Demo size
A program’s image (the full-width cover, the cards, the share image) 1920 × 1280 (3 : 2)
A club’s image (the cover, the cards, the share image) 1200 × 800
A club’s gallery (four) 800 × 533
A facility’s image 400 × 267
A trainer’s image (a portrait) 800 × 1200
A post’s image (the cards, the cover, the share image) 1200 × 800
Home’s hero, the CTA band, Free trial and the 404 (full width) 1920 × 1280
The members’ stories, About’s “Why Choose” cards, the training goals 800 × 1200, 600 × 900
The gallery of About 1200 × 1800 and 1200 × 800
The footer’s Instagram grid 400 × 400
The member photos of the hero’s quotes 160 × 160

Photos in a fixed frame are cropped to fill it, so a photo of other proportions works, but you lose the edges the frame cuts. Frames that follow the screen change shape between phone, tablet and desktop (a program’s photo is a full-width cover on its page and a card elsewhere), so keep the subject away from the edges.

Every photo written as { src, alt } has an alt: a short description for screen readers and search engines. Write one for each photo you change. The category icons (category-*.svg) and the logos are SVG files.

Two things sit outside the content because browsers and social networks ask for them by name:

File What it is
src/app/icon.svg, src/app/apple-icon.png The icon in the browser tab (the Waras mark, a vector) and on a phone’s home screen (180 × 180)
public/opengraph-image.png The picture shown when someone shares a link (2400 × 1260; 1200 × 630 or larger works)

The share image’s description for screen readers is shareImage.alt in src/lib/meta.ts, next to its size: change them if your image has another size, and write a description of your own. Every page uses this image when shared, except the program, club, trainer and post pages, which share their own photo.

Almost every word is content, including the forms’ messages. The few interface words that never change per site live in the code:

  • the date format of posts and legal pages (“Aug 18, 2025”) in src/lib/format.ts;
  • the page’s language, lang="en", in src/app/layout.tsx;
  • the forms’ fallback labels in the design system, used only when the copy gives none.

Search for the word and you will find it.

Terminal window
npm run build

A successful build means every content file has the fields it needs and every page still renders. It doesn’t check that the images exist or that links written as text ("/contact") lead somewhere: click through the site once with npm start after big changes. See Going live for the rest of the checklist.