Going live — Fitbricks HTML
Publishing the Fitbricks HTML edition means replacing the demo’s gym, pictures and videos, having your legal pages written, pointing the forms at you and uploading the folder to any static host.
There is no build command and no server software: the folder you edited is the site.
Before you upload
Section titled “Before you upload”| Where | |
|---|---|
| Demo domain replaced by yours | Every .html file, sitemap.xml, robots.txt: find https://fitbricks-html-framebrick.vercel.app (Editing the site) |
Your gym’s name instead of “Waras”: the logo, the copy of most pages, the copyright, the logo’s alt, @waras on the Instagram tiles |
Search the folder for “Waras” |
Contact details: the e-mails (@warasfit.com), phones and addresses are made up, and the footer’s e-mails use example.com |
Contact, the CTA band, every club and trainer page, the footer |
| Social links (they open the networks’ home pages), the Career link and the trainers’ links | The footer, About’s gallery, the trainer pages |
| The program videos replaced with your own, or removed: they are other creators’ YouTube videos | Every page in program/ (Editing the site) |
| The App Store and Google Play badges linked to your app, or removed, with the app section’s screens | Home’s app section and the footer |
The legal pages written for your business (the samples describe the made-up Waras gym, and the Terms hold [Your Country/State]) |
legal/ (Editing the site) |
| The demo’s claims: prices, “30+ Clubs in 10 Cities”, the facts and members’ stories, opening hours, the FAQ | Home, About, Contact, the program and club pages |
| Your programs, clubs, cities, trainers and posts | The pages in program/, club/, city/, trainer/, blog/, and every list that shows them (Editing the site) |
| Titles and descriptions written for your site | Each page’s <head>; Home’s still describe the template |
| Logos, icons and share image replaced | assets/images/logo-light.svg, logo-dark.svg, logo-black.svg (Making it look like your brand), icon.svg, apple-icon.png, opengraph-image.png (2400 × 1260; 1200 × 630 or larger) and its description, og:image:alt |
| Demo photos replaced | assets/images/ |
| The forms deliver to you | assets/js/config.js (Forms) |
| Style guide kept or deleted | style-guide.html |
| Stylesheet rebuilt if you changed the theme or used new classes | npm run build:css (Making it look like your brand) |
Leaving “Waras”, the sample e-mails and phones, the demo’s clubs and trainers, the example videos or the sample legal
texts on a live site is the most common mistake. Search the folder for “Waras”, “warasfit”, “example.com” and
[Your one last time (the forms’ placeholder hello@example.com can stay).
What to upload
Section titled “What to upload”Everything except the tools and the documentation:
| Upload | Leave out |
|---|---|
The .html pages, program/, program-category/, club/, city/, trainer/, blog/, legal/ |
node_modules/, src/, docs/ |
assets/ |
package.json, package-lock.json, .gitignore |
icon.svg, apple-icon.png, opengraph-image.png |
README.md, CHANGELOG.md, LICENSE.md |
sitemap.xml, robots.txt |
Documentation.html, Documentation.pdf |
Uploading the extra files does no harm, but there is no reason to publish them.
Where to host
Section titled “Where to host”| Host | How |
|---|---|
| Netlify | Drag the folder onto Netlify Drop. Done; then add your domain. |
| Cloudflare Pages, Vercel | Upload the folder or connect a Git repository; no build command, the output folder is the root. |
| GitHub Pages | Push the folder to a repository and enable Pages. |
| Shared hosting (cPanel, Plesk…) | Upload through the file manager or FTP into public_html (or www). |
Pages link to each other with their file names (about.html, club/<slug>.html), so no server configuration is
needed. One demo program keeps parentheses in its file name, program/ride-(cycling).html; common hosts serve it as it
is, but check it after uploading. Most hosts serve 404.html for unknown addresses automatically; on Apache, add
ErrorDocument 404 /404.html to .htaccess. The paths in 404.html start at the site’s root
(/assets/css/style.css, /index.html), because hosts show it at any address: if your site lives in a sub-folder of its
domain (example.com/gym/, or a GitHub Pages project site), add that folder to those paths.
Your domain
Section titled “Your domain”Add it in the host’s domain settings and point your DNS where they tell you (usually an A record or a CNAME). Turn
on HTTPS: every host above does it for free.
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the menu on desktop, the tablet and phone menus, and the header over the photos as you scroll;
- Home’s hero, its quotes and the stories ticker and carousel;
- Programs, Clubs, Trainers and Blog showing more cards as you scroll, and the category and city filters;
- a program page with its video and plans, a club page with its booking form and map link, a trainer page, a post;
- the footer’s links and legal pages, and the 404 page (open an address that doesn’t exist).
- Write to yourself — a contact message, a free-trial request and a booking from a club page — and reply to them.
- Verify the share card. Paste the URL of the home page and of a program into https://www.opengraph.xyz or a chat window, and confirm the image and title.
- Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. - Analytics, if you want it. Paste your snippet before
</head>in every page (find and replace on</head>does it at once), or use your host’s built-in analytics (Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. Add programs, clubs, trainers and posts as described in Editing the site,
and keep
sitemap.xmlin step.
Performance and SEO
Section titled “Performance and SEO”The pages ship with what search engines look for:
- real HTML, with links in it to every page — every card of the lists that load on scroll too;
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; the 404 page and the style guide are kept out of search results (noindex); - lazy-loaded images below the top of each page, with their size written so that they keep their space while they load;
- the YouTube player loads only when the visitor presses play.
Each image is one file, used at every screen size. Keep the site fast by exporting photos at the size they are shown and compressing them; the photos at the top of each page (Home’s hero, the program covers, the club photos) matter most on phones.