What is real, and what you have to
wire up.
Most templates leave this page out. It is here because a demo that looks like it takes payments and gates content, and does neither, is the fastest way to earn a refund.
Works the moment you
remix it.
No accounts, no plugins, no keys. Open the preview and it behaves.
01
The whole catalog, its filters, sorting and every detail page — native Framer CMS, no plugin.
02
The cart: add, remove, and persistence across navigation and a browser reload.
03
The session player: set-by-set logging, rest timer, previous-session ghost values, PR flags, pound/kilo conversion.
04
Progress: adherence heatmap, weekly volume, estimated 1RM — all computed from your own log.
05
The PAR-Q health screening and scroll-to-accept waiver, with a stored consent record.
06
The program finder quiz, with real branching and a scored recommendation.
Demo only, and labelled
on screen.
These look complete because they are designed complete. They are not connected to anything yet.
01
Checkout runs in demo mode until you connect a store. It grants access locally instead of taking money, and says so on screen.
02
The member area is gated by navigation only. Anyone with the URL can reach it until you install an auth tool.
03
Coach screens are seeded demo data and are labelled as such on the canvas.
04
Drip release uses a release-day number and a date check in the browser. It is a convenience, not a lock.
05
Hero photography on About, Coaching, Contact, Method, Results, Challenge, Free week and Journal is a plain image fill on the frame named Portrait or Hero Plate. Swap it on all three breakpoints. Program, exercise, coach and journal-post pages take theirs from the CMS.
Seven things to
connect.
In this order. The whole list is under an hour except the content, which is the actual work.
01
Framer Pro
This template uses ten CMS collections. Free and Basic plans cap below that, so the site needs Pro.
02
A payment processor
Create one product per program, per bundle and per membership tier, then paste each checkout URL into the Checkout URL field on that CMS item. About twenty minutes. Turn off demo mode on the checkout component when you are done.
03
Auth, if you want a real gate
Install a Framer membership plugin, protect /train and /account, and drop its login components onto the two auth pages. Budget roughly twenty dollars a month.
04
Protect the assets, not the pages
This is the part people skip. On a static site, page gating is cosmetic — the real boundary is signed video URLs and licence-keyed file delivery from your host. Do that and it does not matter much who reaches the page.
05
Video hosting
Put exercise demos on a host that supports signed or domain-locked playback, then replace the Exercise Media map on each program.
06
Your content
Swap the CMS rows. Rewrite the prescription blocks in the same notation — the session player parses them, so keep the format.
07
Legal review
The terms, privacy, refund and health pages are placeholder copy with a warning box on each. Have a lawyer read them, then delete the boxes.
Limitations, stated
up front.
Framer publishes a static site. These are structural, not oversights, and every one of them is visible in the design rather than hidden.
01
Checkout handles one product at a time. A cart with three separate programs becomes three checkouts — the cart says so plainly rather than hiding it, and offers membership as the one-payment alternative.
02
There is no server. Cart totals, ownership and drip dates are client-side assertions, which is fine for convenience and not fine as security.
03
Custom code and third-party scripts do not run in Framer Preview. Test every integration on the published URL.
04
The training log lives in one browser. It does not sync across devices unless you add a backend.