Rep: gyms and strength studios website template

An app template for a strength gym: members book classes from their phone (the desk confirms the place or puts them on the waitlist), check in at the desk by showing a code, and every tenth check-in earns a free guest pass. Members pay monthly on an Off-peak or Full plan. A public page with the timetable and plans, six member screens under /app and a privacy notice with blanks.

Built from: Pages · Lists · Sign-in: users · Actions: pay, scan

To use it, paste this into your AI chat:

Use template pagelemon.com/tp/Rep

Copy the prompt Preview (opens in a new tab)

Who it suits

Made for: gyms and strength studios, barbell and Olympic lifting clubs, small gyms with a class timetable, boxing gym, yoga studio, climbing wall, martial arts club, spin studio, pilates studio. In the gallery under Membership & community.

Its 9 pages

Home: The public page: Ironbark in one screen, what the member app does (book, check in, guest passes), this week's timetable, the two plans with prices, the coaches, opening hours and the way in to the app
Today: Signed out: the welcome screen with the plans and sign-in. Signed in: a greeting, the membership card with check-ins toward a guest pass and Show my code, the next class with its status, quick actions and this month's numbers
Book: The week's timetable starting today; tapping a class fills the booking form (class, date, time) and Request a place saves it; the waitlist and cancellation rules sit next to the button
Bookings: Upcoming classes with the desk's status (Requested, Booked, Waitlist) and reply, and past classes newest first with Book again
Cancel: Can't make it: cancel a booked class (filled from the booking), so the desk gives the place to the waitlist; your cancellations with the desk's answer (Sent, Done)
Card: The check-in code to show at the desk, check-ins toward the next guest pass, a guest pass ready to use, and every check-in newest first
Plan: The member's plan, what it covers and its price, the other plan, and the rules for freezing, changing and cancelling
Account: The member's name, email, devices, billing, renewal date and leaving (Page Lemon's account block)
Privacy: The privacy notice, with blanks the Site Owner fills in

Look: Gym whiteboard on steel: chalk boards, a yellow primary and plate colours, with a drawn barbell and condensed type; dark, bold, modern; fonts Antonio and Roboto Flex.

What you can change

Everything, by asking your AI: the name, words, photos, colours, fonts and pages. Your AI first asks you a few questions (such as your gym name, address, phone, email, opening hours and plan names and monthly prices), then replaces every piece of sample text with your own details. Later you can add a contact form, bookings or a password by asking again.

The rest of this page is for your AI: it says what the template is, where its files are, and how to build your site from it and publish it.

You are reading this because the user wants their own website made from the Rep template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Rep": that is the whole request, so start now. In short: ask them a few questions about their business, get the template's files (with the Page Lemon connector, deploy with template: "rep" copies them for you), make the site theirs (their name, words, details and pictures; no sample content left), then publish it with Page Lemon and give them the link. The steps below say exactly how. The full publishing guide is at https://pagelemon.com/agents.

About this template

Look: Gym whiteboard on steel: chalk boards, a yellow primary and plate colours, with a drawn barbell and condensed type (dark, bold, modern)
Pages: Home (index.html): The public page: Ironbark in one screen, what the member app does (book, check in, guest passes), this week's timetable, the two plans with prices, the coaches, opening hours and the way in to the app; Today (app/index.html): Signed out: the welcome screen with the plans and sign-in. Signed in: a greeting, the membership card with check-ins toward a guest pass and Show my code, the next class with its status, quick actions and this month's numbers; Book (app/book.html): The week's timetable starting today; tapping a class fills the booking form (class, date, time) and Request a place saves it; the waitlist and cancellation rules sit next to the button; Bookings (app/bookings.html): Upcoming classes with the desk's status (Requested, Booked, Waitlist) and reply, and past classes newest first with Book again; Cancel (app/cancel.html): Can't make it: cancel a booked class (filled from the booking), so the desk gives the place to the waitlist; your cancellations with the desk's answer (Sent, Done); Card (app/card.html): The check-in code to show at the desk, check-ins toward the next guest pass, a guest pass ready to use, and every check-in newest first; Plan (app/plan.html): The member's plan, what it covers and its price, the other plan, and the rules for freezing, changing and cancelling; Account (app/account.html): The member's name, email, devices, billing, renewal date and leaving (Page Lemon's account block); Privacy (privacy.html): The privacy notice, with blanks the Site Owner fills in
Fonts: Antonio, Roboto Flex (Google Fonts)
Live demo: https://try-rep.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Rep in a browser land there). The template's own files: https://pagelemon.com/templates/rep/; the page about it: https://pagelemon.com/tp/Rep/use
Manifest: https://pagelemon.com/templates/rep/template.json (machine-readable: files, customise, facts, interview)

Files

With the Page Lemon connector you don't need to fetch these: deploy with template: "rep" copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/rep/ and save it with the same relative path (including art/). Fetch nothing else: templates have no external images or scripts.

Notes for Rep (its `customise` rules)

Ironbark Gym, its address, phone, email and hours in the header, footer, titles and copy: replace every data-pl-fill fact with the owner's own. Replace the name in site.webmanifest too; keep short_name Ironbark unless the owner chooses another.
Fill in every highlighted blank on privacy.html before members join (not legal advice: https://pagelemon.com/agents/member-app-legal).
Make the bookings and cancellations lists (with status_options and reply) and the visits list with its scan actions exactly as memberApp.lists and memberApp.scan say, changing only labels and the owner's numbers. Keep the class names and times on app/book.html, app/cancel.html, index.html and the lists' options the same.
Set the plans with save_plan at the owner's prices and change the prices on index.html, app/index.html and app/plan.html together. Call setup_app with signup "open" and the name profile field, so staff see the member's name when they scan.
Staff answer bookings in the Dashboard (Apps, Entries): Booked, Waitlist, Checked in or Cancelled, with a short reply the member sees on app/bookings.html. A cancellation request is answered by setting the booking to Cancelled and the request to Done. Page Lemon does not count places: the desk decides who gets a place and who waits.
Staff scan with their phone's camera: add each one with add_people as a collaborator with the scan permission, so they can check members in and redeem guest passes but not change the site.
A gym app only: never add health, body measurement, payment card, bank or ID fields, and never collect anything about under-18s.
Colours: Edit the --k-brand, --k-hero and --k-gold tokens at the top of styles.css; light and dark follow the device.
Fonts: Antonio and Roboto Flex, loaded from Google Fonts on every page; your AI can self-host them on request.
Sections: Public: index.html (what the app does, timetable, plans, coaches, visit). Member pages under /app use the shared app kit (kit.css, kit.js, kit-icons.svg: never edit them) and site.js (timetable dates and the booking summary). The timetable markup on app/book.html is the class list: one link per class with data-day and the class and time in its address.
Images: art/gym-floor.svg is the app welcome picture (1200×1260); art/barbell.svg is drawn hero art for the public page; the five art/class-*.svg are the class pictures (600×600). Replace them with the gym's own photos at the same sizes (WebP under 300 KB), never a stranger's face.

Set up the app

This is an app template: the home page and privacy notice are public, and the pages under /app are for signed-in users, each seeing only their own entries and the entries the Site Owner assigns to them. Users sign in with a code sent to their email. The full guide is https://pagelemon.com/agents/member-app; read it before you set this up, and its legal notes at https://pagelemon.com/agents/member-app-legal.

Needs: a kept site on App or above, and the Site Owner signed in to Page Lemon with two-step sign-in (they turn the app on themselves, at the approve link setup_app returns).
Never: health, mood or therapy records, accounts for children, or fields for card, bank or ID numbers (Acceptable Use: https://pagelemon.com/acceptable-use#member-app). Users pay through Stripe.
Then: setup_app with these settings, the join questions and note in the user's own words, then save_app_list once for each list below, exactly as written, so the field names match the pages.
```
{"site":"<site>","signup":"open","profile_fields":[{"name":"name","type":"text","label":"Your name","required":true}],"display_field":"name","path":"/app"}
```

Class bookings (bookings): users add these rows themselves on the pages.

{"site":"<site>","list":"bookings","label":"Class bookings","fields":[{"name":"class","type":"choice","label":"Class","required":true,"options":["Barbell Basics","Strength Club","Engine","Kettlebells","Mobility"]},{"name":"date","type":"date","label":"Date","required":true},{"name":"time","type":"choice","label":"Time","required":true,"options":["06:30","07:00","09:00","10:00","11:15","12:15","18:00","18:30","19:30"]},{"name":"message","type":"text","label":"Note for the coach"}],"status_options":["Requested","Waitlist","Booked","Checked in","Cancelled"],"reply":true}

Cancellations (cancellations): users add these rows themselves on the pages.

{"site":"<site>","list":"cancellations","label":"Cancellations","fields":[{"name":"class","type":"choice","label":"Class","required":true,"options":["Barbell Basics","Strength Club","Engine","Kettlebells","Mobility"]},{"name":"date","type":"date","label":"Date","required":true},{"name":"time","type":"choice","label":"Time","required":true,"options":["06:30","07:00","09:00","10:00","11:15","12:15","18:00","18:30","19:30"]},{"name":"message","type":"text","label":"Anything the desk should know"}],"status_options":["Sent","Done"],"reply":true}

Check-ins (visits): the Site Owner adds these rows in the Page Lemon Dashboard (Apps tab) and assigns each to one user, who only reads it.
```
{"site":"<site>","list":"visits","label":"Check-ins","fields":[{"name":"visit","type":"text","label":"Visit","required":true}]}
```
Plans (save_plan; the pages use data-pl-if="plan:<id>" and join buttons): offpeak "Off-peak" (paid, sample price 24.00 GBP a month; ask the user for theirs); full "Full" (paid, sample price 39.00 GBP a month; ask the user for theirs). Paid plans need Starter or Scale and the Site Owner's Stripe account connected; save_plan returns the onboarding link if it isn't.

Build the site, step by step

Interview first. Ask the user these questions, a few at a time, in plain words, and collect every fact the site needs (gym name, address, phone, email, opening hours, plan names and monthly prices, what a trial visit includes, coach names and roles, class timetable and class lengths, check-in and guest pass rules, privacy contact and address). If they can't answer one, remove that element rather than inventing it.
- What is your gym called, and where is it?
- What are your opening hours on weekdays and at weekends?
- Which plans do you sell, at what monthly price, and when can members train on each?
- What does a trial visit include, if you offer one?
- What classes run each week, and how many places does each one have?
- Who scans members in at the desk? Each needs a Page Lemon sign-in: invite them as collaborators with Scan users ticked.
- Which email address, phone number and privacy contact should members see?
Get the files. If you have the Page Lemon tool (the MCP connector with a deploy tool; https://pagelemon.com/docs/connect sets it up), call deploy with template: "rep" (no files): Page Lemon copies every file above on its side and returns site, revision and, without an account, site_token. Read each page you will change with get_site and path, make the changes below, then publish only the changed files with deploy, site, base_revision (that revision) and patch: true; show the link only after that. Without the tool, fetch the files listed above. If you cannot fetch files either, ask the user for what you need and rebuild the pages from the live demo as closely as you can.
Make it the user's site. Follow customise in template.json:
- Replace every element marked data-pl-fill (names, phone, email, address, hours, prices, people, dates, links, stats) on every page, then remove the attributes. Never ship a data-pl-fill default. The sample town, street and people's names also appear in ordinary sentences, aria-labels and image alt text: replace them there too. Name, address and phone must match exactly in the footer, the visit or contact page and the JSON-LD.
- Sample reviews (data-pl-fill="review") are fictional: delete them unless the user gives you real ones. Delete each whole review, with its name or caption, and the section and its nav link when none is left. Never invent reviews, numbers or awards.
- Update each page's <title>, meta description, canonical, og:url and og:image to the user's real address, and the JSON-LD block on the home page (type, name, address, geo coordinates (delete them unless you have the real ones), hours, phone, url).
- Photos: this template is drawn art, not photos. If the user wants their own photos, add them where they fit (compressed, WebP or JPEG under about 300 KB, real alt). Ask for photos; never hot-link.
- Make a new og.png (1200×630) of the new home page if you can, with its og:image tags; otherwise delete the sample one and its og:image tags (a template deploy has already left both out). Change colours only through the :root tokens in styles.css, fonts through the font tokens and the <link> that loads them. Google Fonts is fine, but it sends each visitor's IP address to Google, so the privacy-friendly choice is to self-host the font files (woff2) in the site folder with @font-face, or use system fonts.
- Delete pages or sections the user doesn't need (and their nav links) rather than leaving them generic. Keep the layout, type scale and signature interaction: they are what makes it look designed.
- Remove the  comment.
Forms and bookings. Templates have no fake forms. Each data-pl-slot shows a fallback that works today (call, email, or the Site Owner's own booking or payment link: ask for it). The designed form sits next to it in an inert <template data-pl-slot-form="<id>">; template.json.slots says which page has which. When the user wants the real thing (Forms and Booking: any paid plan; staff and rooms only on some, and each plan has a limit of online bookings a day), set the form up as a list (save_list) or the service (save_service), put the matching markup in the slot (reuse the template's form classes so it matches), delete the fallback and the <template>, and copy the paragraph from <template data-pl-privacy="forms"> into privacy.html.
Check before publishing:
- Search every file for data-pl-fill, the template's fictional business name and its sample phone, email and street, in links too (tel: and mailto: hrefs, and map links, where the street is written like 18+Linden+Walk): none left.
- All links between pages work; nav and footer are the same on every page.
- Body text contrast at least 4.5:1, large text and buttons 3:1, after any colour change.
- No horizontal scroll at 320 px; headlines still fit on a phone after copy changes.
- One h1 per page, a unique <title> and meta description per page, alt text on meaningful images.
- Copy sounds like the user, not like an AI (see https://pagelemon.com/guides/website-copy-that-doesnt-sound-like-ai).
Publish with Page Lemon (below; with the tool, the patch deploy from step 2 is the publish), then tell the user which template you used and that they can keep changing the site, or add bookings and forms, by asking.
Turn on the app as "Set up the app" above says: setup_app, then save_app_list for each list, save_plan for each plan, the approve link to the Site Owner, invite_users, a test with preview_as_user and get_app with check: true before you say it's ready.

Publish with Page Lemon

Pick the first route you can use:

You can run shell commands: build if needed, then upload only the folder with index.html (dist/, build/, out/…). Never upload source code, .env files or keys: everything you upload becomes public. (at most 100 files and 1 MB in all, index.html at the root):
```
node -e 'const fs=require("fs"),p=require("path"),d=process.argv[1],files=[];(function w(x){for(const e of fs.readdirSync(x,{withFileTypes:true})){const f=p.join(x,e.name);e.isDirectory()?w(f):files.push({path:p.relative(d,f).split(p.sep).join("/"),content_base64:fs.readFileSync(f).toString("base64")})}})(d);console.log(JSON.stringify({files}))' <dir> \
  | curl -sS --fail-with-body -H "Content-Type: application/json" --data-binary @- https://api.pagelemon.com/v2/anonymous-sites
```
If the user gave you an API key (plak_…) or ~/.config/pagelemon/credentials exists, publish into their account instead (see "Updating a site" in https://pagelemon.com/agents). If .pagelemon.json exists, the site is already published: see "Updating a site" in https://pagelemon.com/agents.
You have the Page Lemon MCP connector (https://mcp.pagelemon.com/mcp): call its publish_site tool with every file. See "No shell: the MCP connector" in https://pagelemon.com/agents.
Neither (a chat app without the Page Lemon connector): say once that they can connect Page Lemon to this AI app (steps at https://pagelemon.com/docs/connect) so you can publish and change the site for them. In the Gemini app or Grok (free plan included) it takes about a minute: Gemini at gemini.google.com/customize/connectors (Custom), Grok at grok.com/connectors (New Connector, Custom), with the link https://mcp.pagelemon.com/mcp; then they sign in and click Allow. Give those steps in plain words. If they can't or would rather not (for example ChatGPT's free plan), don't ask them to save or upload files. Put the whole site in ONE complete page: CSS and JavaScript inline, images as https links or small data URIs, from <!DOCTYPE html> to </html>. Show it as one code block, then tell them: "Tap Copy on the code, open pagelemon.com/publish, tap Paste and publish." Only if you can really give them a downloadable .zip (a file they tap to download, not code to save): "Download this zip, open pagelemon.com/publish, tap Drop or choose a file." They get a live link with no account, online for 72 hours unless they tap Keep it free. Don't say you can't help.

Then:

Pass on agent_message from the response in full, success or failure, in the user's language and your own words. It has the link, the expiry time, the private keep link and the terms line: copy every link, code, number, date and domain exactly, and never drop a link, deadline or the terms line (keep both its links). If it asks a question, ask it and wait. Times in it are UTC; *_at fields have them in ISO, so you can give the user's local time.
On success, save .pagelemon.json in the project folder and add it to .gitignore (see https://pagelemon.com/agents).
Offer to help keep the site (see "Keeping the site" in https://pagelemon.com/agents). Sites published without an account go offline after 72 hours unless the user keeps them with a free account.

By publishing, the user agrees to the Terms (https://pagelemon.com/terms) and Privacy Policy (https://pagelemon.com/privacy). The agent_message includes this line; keep it.

More: https://pagelemon.com/agents (full guide: updating a site, keeping it, custom domains, plugins). All templates: https://pagelemon.com/templates/index.json.