# Clubhouse: a Page Lemon website template > An app template for a camera club that approves its members: people ask to join on the sign-in page and the committee reviews each request in the Page Lemon Dashboard; members reply to outings with guests and lifts, enter the monthly theme with a photo and get the judge's score and note back, and check in at club night with a code (every 10th night a free print). A public page, six member pages under /app and a privacy notice with blanks. You are reading this because the user wants their own website made from the Clubhouse template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Clubhouse": 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: "clubhouse"` 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:** Light box of square slide mounts in Kodachrome yellow and red, with members' prints, a navy band and a film-box card (light, bold, classic) - **Pages:** Home (`index.html`): The public page: what the club does, when it meets, the subscription, what members get in the app, and how to ask to join (the button opens the sign-in page, which takes requests); Clubhouse (`app/index.html`): Before anyone signs in, a welcome with Sign in and Ask to join; once signed in, the member card with club nights toward a free print, the next outing with the member's reply, this month's entry with its status, the Tuesday programme and the noticeboard; Outings (`app/outings.html`): Each outing with its cover, meeting point and leader, the member's current reply and a reply form that starts from it (Going, Maybe, Can't go, guests, lifts, a note), plus the member's replies; Enter the theme (`app/enter.html`): This month's theme and how it's judged, and the entry form with a photo; My entries (`app/entries.html`): The member's entries newest first with the status (Received, Judging, Judged) and the judge's score and note, plus last month's results; Card (`app/card.html`): The member card: the code to show at the door on club night, club nights toward a free A3 print, and the nights checked in; Account (`app/account.html`): The member's membership (Full member or Concession, or the two plan cards to pay the year), their club details, card and the secretary, then Page Lemon's sign-in and billing block with profile, devices, renewal and leaving; Privacy (`privacy.html`): The privacy notice, with blanks the Site Owner fills in - **Fonts:** League Spartan, Lexend (Google Fonts) - **Live demo:** https://try-clubhouse.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Clubhouse in a browser land there). The template's own files: https://pagelemon.com/templates/clubhouse/; the page about it: https://pagelemon.com/tp/Clubhouse/use - **Manifest:** https://pagelemon.com/templates/clubhouse/template.json (machine-readable: files, customise, facts, interview) ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "clubhouse"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/clubhouse/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/clubhouse/index.html - https://pagelemon.com/templates/clubhouse/app/index.html - https://pagelemon.com/templates/clubhouse/app/outings.html - https://pagelemon.com/templates/clubhouse/app/enter.html - https://pagelemon.com/templates/clubhouse/app/entries.html - https://pagelemon.com/templates/clubhouse/app/card.html - https://pagelemon.com/templates/clubhouse/app/account.html - https://pagelemon.com/templates/clubhouse/privacy.html - https://pagelemon.com/templates/clubhouse/styles.css - https://pagelemon.com/templates/clubhouse/app.js - https://pagelemon.com/templates/clubhouse/kit.css - https://pagelemon.com/templates/clubhouse/kit.js - https://pagelemon.com/templates/clubhouse/kit-icons.svg - https://pagelemon.com/templates/clubhouse/art/icons.svg - https://pagelemon.com/templates/clubhouse/art/hall-prints.svg - https://pagelemon.com/templates/clubhouse/art/photos/heron.webp - https://pagelemon.com/templates/clubhouse/art/photos/harbour.webp - https://pagelemon.com/templates/clubhouse/art/photos/harbour-wide.webp - https://pagelemon.com/templates/clubhouse/art/photos/birch.webp - https://pagelemon.com/templates/clubhouse/art/photos/puddle.webp - https://pagelemon.com/templates/clubhouse/art/photos/shop-window.webp - https://pagelemon.com/templates/clubhouse/art/photos/groyne.webp - https://pagelemon.com/templates/clubhouse/art/macro-leaf.svg - https://pagelemon.com/templates/clubhouse/art/noon-street.svg - https://pagelemon.com/templates/clubhouse/art/portrait-silhouette.svg - https://pagelemon.com/templates/clubhouse/site.webmanifest - https://pagelemon.com/templates/clubhouse/favicon.svg - https://pagelemon.com/templates/clubhouse/og.png - https://pagelemon.com/templates/clubhouse/apple-touch-icon.png - https://pagelemon.com/templates/clubhouse/icon-192.png - https://pagelemon.com/templates/clubhouse/icon-512.png - https://pagelemon.com/templates/clubhouse/icon-512-maskable.png ## Notes for Clubhouse (its `customise` rules) - Fenwold Camera Club in the header, tab rail, footer and titles; replace every data-pl-fill fact with the club's own: Thursby Hall in Kettlebridge, Tuesdays 7.30pm, the secretary Ottoline Pennick, outings lead Wyn Carrick, competition secretary Hal Brennock and the judge Maggie Thorne. Replace site.webmanifest.name too. - Fill in every highlighted blank on privacy.html with the Site Owner before users use the site (not legal advice: https://pagelemon.com/agents/member-app-legal) - Outings: the rsvps list's outing options. Change them with save_app_list, and the outing cards on app/outings.html (each card's data-c-date, hidden outing and outing_date inputs and data-pl-where) and the Next outing card on app/index.html together, using exactly the same text and date. Replies split into Upcoming and Past by outing_date, and a card hides itself once its day has passed. Add new outings before removing past ones so old replies keep their label. - Themes: the entries list's theme options. Change them with save_app_list, the select on app/enter.html, the theme heading on app/enter.html, the data-pl-where on app/index.html and the red band line at the top of index.html together. Statuses are Received, Judging, Judged and Replaced (for an older entry when a user sends a newer one for the same theme); the owner sets them in the Dashboard (Apps, the entries list) and writes the score and note as the reply. - Check-in: save_app_list for nights with scan exactly as memberApp.scan says (Club night, goal 10, one a day; Free print redeems 10). Change the goal and reward words on app/index.html and app/card.html together. Whoever stands at the door needs the Scan users permission. - Subscriptions: save_plan for member (Full member, £42 a year) and concession (Concession, £24 a year); paid memberships need Starter or Scale and a connected Stripe account. Without them, remove the two plan cards on app/account.html and say how users pay instead (for example to the secretary); the app keeps no record of cash payments. - The Tuesday programme and the noticeboard on app/index.html, the outing rules on app/outings.html and last month's results on app/entries.html are plain HTML the owner edits. - Club business only: never add health or medical questions, and never ask for card, bank or ID numbers in the join questions or the lists. Never create accounts for children or collect their personal data, including through adults' accounts. - Club nights are Tuesdays at 7.30pm; app.js shows the coming Tuesdays' dates in the programme and on the welcome screen (data-c-tue). If the club meets on another day, change the weekday in app.js section 4 and the words Tuesday on the pages. - Staff see each user's first name (display_field name) when they scan; memberApp.demo.staff uses the same first names. - **Colours:** Edit the colour tokens in the art direction 2026-10-25 block at the end of styles.css (the --k-brand, --k-hero and --k-gold tokens, with the navy band and the red band in their own rules); the dark scheme follows the device. --mustard is a background colour for tags and notice pins; keep text on it in --mustard-ink. - **Fonts:** League Spartan and Lexend, loaded from Google Fonts on every page; your AI can self-host them on request. - **Sections:** App pages live under /app and use the data-pl-view markup. Joining is request-to-join: setup_app with memberApp.setup (signup "request", request_note and profile_fields; no template), then save_app_list for each list in memberApp.lists. Ask the owner what the join questions should be (profile_fields, at most 10, no photo or file; start from first name, last name, camera and a line about themselves) and write request_note in their words (at most 300 characters). The sign-in page then reads "Ask to join" with the request note, asks the questions after the email code, and the request waits in the Dashboard (Apps, Requests) for the owner to approve or decline; the person gets an email either way. Through the AI, invite_users naming a waiting address approves it and remove_user declines it (both ask for the owner's yes first). If setup_app refuses signup "request" (request-to-join is not on for this account yet), use signup "invite" without request_note and profile_fields, and the secretary invites the people the club says yes to with invite_users. Then rewrite what promises request-to-join: on index.html and app/index.html the Ask to join buttons become a mailto link to the secretary's email, its paragraphs say to email the secretary with the same details and that the club replies by email and sends an invitation if it says yes, and How users get in says users sign in with the address their invitation went to; on privacy.html, "When you ask to join" becomes what people email the secretary, the email-address line says it is used to invite them and sign them in, and the request sentences under How long we keep it become a blank for how long the club keeps emailed requests (agree it with the owner). app.js shows each reply (Yes, Maybe, No) as Going, Maybe or Can't go with its colour, keeps only the latest reply per outing in Your replies, fills each outing's form from the user's current reply, shows the next Tuesday's date on the signed-out welcome and the chosen photo's name on the entry form. - **Images:** favicon.svg is the enamel badge; the PNG icons and manifest are made from it. The outing covers and the sample prints (art/photos/*.webp) are free stock photos from Unsplash and Pexels (PHOTOS.md): replace them with the club's own photos of its outings and members' prints, with the photographers' permission. art/hall-prints.svg is the felt-board drawing and art/icons.svg holds three icons the app kit doesn't have (image, trophy, flag). ## 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 (request-to-join: people ask on the sign-in page, answer the join questions, and the Site Owner approves or declines each request), 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. ```json {"site":"","signup":"request","request_note":"Ottoline, our secretary, reads every request. The committee answers at the next club night.","profile_fields":[{"name":"name","type":"text","label":"First name","required":true},{"name":"last_name","type":"text","label":"Last name","required":true},{"name":"camera","type":"text","label":"Which camera do you use?"},{"name":"about","type":"long_text","label":"A line about yourself"}],"display_field":"name","path":"/app"} ``` - **Outing replies** (`rsvps`): users add these rows themselves on the pages. ```json {"site":"","list":"rsvps","label":"Outing replies","fields":[{"name":"outing","type":"choice","label":"Outing","required":true,"options":["Sat 17 Oct · Hollin Pier at golden hour","Sun 8 Nov · Sandling Marsh at sunrise","Fri 20 Nov · Ludwell Quay after dark","Mon 7 Dec · Danbrook Woods in the frost"]},{"name":"coming","type":"choice","label":"Are you coming?","required":true,"options":["Yes","Maybe","No"]},{"name":"guests","type":"number","label":"Guests you're bringing"},{"name":"lift","type":"choice","label":"Lifts","options":["I can give a lift","I need a lift","No lift needed"]},{"name":"memo","type":"long_text","label":"Note for the leader"},{"name":"outing_date","type":"date","label":"Outing date"}]} ``` - **Theme entries** (`entries`): users add these rows themselves on the pages. ```json {"site":"","list":"entries","label":"Theme entries","fields":[{"name":"theme","type":"choice","label":"Theme","required":true,"options":["Street","Golden hour","Reflections","Lights after dark","Close up"]},{"name":"title","type":"text","label":"Title","required":true},{"name":"photo","type":"photo","label":"Your photo","required":true},{"name":"memo","type":"long_text","label":"About the photo"}],"status_options":["Received","Judging","Judged","Replaced"],"reply":true} ``` - **Club nights** (`nights`): the Site Owner adds these rows in the Page Lemon Dashboard (Apps tab) and assigns each to one user, who only reads it. ```json {"site":"","list":"nights","label":"Club nights","fields":[{"name":"item","type":"text","label":"For","required":true}]} ``` - **Plans** (`save_plan`; the pages use `data-pl-if="plan:"` and join buttons): `member` "Full member" (paid, sample price 42.00 GBP a year; ask the user for theirs); `concession` "Concession" (paid, sample price 24.00 GBP a year; 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 1. **Interview first.** Ask the user these questions, a few at a time, in plain words, and collect every fact the site needs (club name, where and when the club meets, secretary's name and email, the yearly subscription and concession, the next outings, meeting points and leaders, this month's theme and judge, the check-in reward, privacy contact and address). If they can't answer one, remove that element rather than inventing it. - What is the club called, and where and when do you meet? - Who reads the requests to join, and which email should people write to? - This app is for adults aged 18 or older. What non-sensitive questions should people answer when they ask to join (start: first name, last name, camera, a line about themselves)? - Which outings are coming up: date, place, meeting point and who leads each? - What are this year's monthly themes, who judges, and how is each entry scored? - What does a member get for coming to club nights (every 10th night a free A3 print, or something else)? - What is the yearly subscription, and is there a concession? - What address and privacy contact should the privacy notice show? 2. **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: "clubhouse"` (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. 3. **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-label`s 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 ``, 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 `<!-- Page Lemon template ... -->` comment. 4. **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`. 5. **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). 6. **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. 7. **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: 1. **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): ```bash 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. 2. **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. 3. **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.