Chapter website template

An app template for an invite-only monthly book club: members see the next meeting and its book, say if they're coming, vote on the next book from a shortlist and see the result, log the page they're on and see the pace to finish, send notes the host reads out in the room, and check in at the door with a code, so every tenth meeting earns a free paperback. A public page, seven member pages under /app and a privacy notice with blanks.

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

To use it, paste this into your AI chat:

Use template pagelemon.com/tp/Chapter

Copy the prompt Preview (opens in a new tab)

Who it suits

Made for: book clubs and reading groups that vote on their own books, literary societies with a small, approved membership, monthly meetings that want notes from members before they meet, poetry society, film club, writing group, library friends group, theatre reading circle. In the gallery under Membership & community.

Its 9 pages

Home: The public page: the club, this month's book and meeting, how the app works (reply, vote, notes, check in), the season's books, the January shortlist, where we meet and Ask to join (an email to the host)
Home: Signed out, a welcome with Sign in and Ask to join. Signed in: the month's book as a dust jacket with the meeting on its flap, the member's reply card in its pocket with past check-ins stamped, the page they are on as a bookmark ribbon and the pace to finish, this week's question, the vote closing date, the member's latest note and its status, and meetings attended toward a free paperback
Meeting: This month's meeting: the book, when and where, the host, the discussion questions, where the member is up to (log a page, see the last three), the reply form (coming, maybe or not, and what they bring) and the member's replies
Vote: The January shortlist of four with covers and blurbs, the vote form with a reason, the member's own vote, and how the winner is announced
Notes: Write notes for a meeting (book, rating, thoughts, a line to read out), then follow each note from Received to Read out with the host's reply
Card: The member's code for checking in at the door, meetings attended toward a free paperback (every tenth meeting), the reward ready to collect, and the meetings attended
Shelf: The club's books this year with meeting dates, the member's ratings and notes newest first, and what comes next
Account: The member's name, the account block (sign-in, devices, leaving), the club's rules and how to reach the host
Privacy: The privacy notice, with blanks the host fills in

Look: Dust jackets by lamplight: an oxblood poster, Cormorant italics, spines on a shelf and a stamped library card; light, calm, classic; fonts Cormorant Garamond and Josefin Sans.

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 club name, meeting day, time and venue, host's name and email, phone number, this season's books and meeting dates and the shortlist for the next vote and its closing date), 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 Chapter template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Chapter": 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: "chapter" 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: Dust jackets by lamplight: an oxblood poster, Cormorant italics, spines on a shelf and a stamped library card (light, calm, classic)
Pages: Home (index.html): The public page: the club, this month's book and meeting, how the app works (reply, vote, notes, check in), the season's books, the January shortlist, where we meet and Ask to join (an email to the host); Home (app/index.html): Signed out, a welcome with Sign in and Ask to join. Signed in: the month's book as a dust jacket with the meeting on its flap, the member's reply card in its pocket with past check-ins stamped, the page they are on as a bookmark ribbon and the pace to finish, this week's question, the vote closing date, the member's latest note and its status, and meetings attended toward a free paperback; Meeting (app/meeting.html): This month's meeting: the book, when and where, the host, the discussion questions, where the member is up to (log a page, see the last three), the reply form (coming, maybe or not, and what they bring) and the member's replies; Vote (app/vote.html): The January shortlist of four with covers and blurbs, the vote form with a reason, the member's own vote, and how the winner is announced; Notes (app/notes.html): Write notes for a meeting (book, rating, thoughts, a line to read out), then follow each note from Received to Read out with the host's reply; Card (app/card.html): The member's code for checking in at the door, meetings attended toward a free paperback (every tenth meeting), the reward ready to collect, and the meetings attended; Shelf (app/shelf.html): The club's books this year with meeting dates, the member's ratings and notes newest first, and what comes next; Account (app/account.html): The member's name, the account block (sign-in, devices, leaving), the club's rules and how to reach the host; Privacy (privacy.html): The privacy notice, with blanks the host fills in
Fonts: Cormorant Garamond, Josefin Sans (Google Fonts)
Live demo: https://try-chapter.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Chapter in a browser land there). The template's own files: https://pagelemon.com/templates/chapter/; the page about it: https://pagelemon.com/tp/Chapter/use
Manifest: https://pagelemon.com/templates/chapter/template.json (machine-readable: files, customise, facts, interview)

Files

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

Notes for Chapter (its `customise` rules)

The Lamplight Readers in the header, footer and titles, with the host Maud Inglethorpe-Sale, Pellow & Daughters Bookshop and 27 Vellum Row, Hartcombe QU3 9GJ: replace every data-pl-fill fact with the club's own, and site.webmanifest.name and the wordmark text on index.html and every app page.
Fill in every highlighted blank on privacy.html with the Site Owner before users sign in (not legal advice: https://pagelemon.com/agents/member-app-legal).
Set up with setup_app (signup invite, the profile field name as the display field, so the host sees first names at the door), then save_app_list for rsvps, votes, thoughts, pages and attendance exactly as memberApp.lists says, with status_options and reply on thoughts.
Meetings live in the meetings list (Lists in the Dashboard, or save_list): book, author, date and time, pages, about the book, the questions for the room (one a line), cover, status and the club rating. Each month set the meeting just held to Read (with its club rating) and the next one to Next: Home, the meeting page, the reply form, the notes and reading forms, the shelf and the public page follow, with no page edits. Exactly one meeting is Next; Later meetings show in the reply form.
The book vote lives in the shortlist list: four books with poll (the month it picks), closes (the closing time) and status Open. Members vote on app/vote.html (the book and poll come from the Open rows). When it closes, count each member's newest vote for the poll in the Dashboard (Apps, Book votes), then set the winner to Chosen and the others to Not chosen, each with its votes: the result card shows on the vote page and Home at once. The page closing is a display: a vote sent late still saves, so count only votes sent before the closing time.
Reading progress: the pages list (book, on_page, line); the book comes from the Next meeting, and the pace on Home from its pages and date.
Check-in at the door: save_app_list for attendance with scan exactly as memberApp.scan says (At the meeting, goal 10, once a day, so once per meeting night; Free paperback redeems 10). The host or a helper with Scan users scans each member's code on their phone. Change the goal and the reward text on app/card.html, app/index.html and index.html together.
Notes: the host sets each note's status (Received, On Maud's list, Read out) and an optional reply in the Dashboard (Apps); members see both on app/notes.html.
Joining is by invitation: the public page asks people to email the host, and the host sends invite_users to the people the club says yes to. Replace hello@lamplightreaders.example.com everywhere with the club's own address.
Club business only: adults aged 18 or older. Never add health or medical questions, never ask for card, bank or ID numbers in the app lists, never create accounts for children or collect their personal data, and never request passwords.
Notes carry read_as (With my name or Without my name): the host reads anonymous notes without the member's name.
Colours: Edit the --c-* and --k-* tokens at the top of styles.css (page, oxblood, bookcloth blue, brass foil, manila for the reply pocket); the dark scheme (a lamplit room) follows the device. Jackets and spines take their colours from each book's cover.
Fonts: Google Fonts: Cormorant Garamond (titles, book names, reading text) and Josefin Sans (labels, dates, buttons), one <link> in every page head and --c-serif / --c-sans in styles.css. If the owner prefers no font service, download both (OFL) into a fonts/ folder and switch to @font-face.
Sections: App pages live under /app on the shared app kit (kit.css, kit.js, kit-icons.svg: never edit those copies) and use the data-pl-view markup. Each app list is a form and a row template: keep the field names and select options together with save_app_list. Update meetings and shortlist through save_list; the pages follow those lists.
Images: art/cover-*.svg are drawn sample covers (400×600) used by the meetings and shortlist lists' cover field: put the real cover in the site and set the field, or keep a drawn one. Each jacket's spine is a blurred wash of the same cover with the title over it, so a real cover gives its own spine colour. art/lamp-room.svg is a spare drawing of the reading lamp. icons.svg holds the app's extra icons (book, pen, ballot, quote, door, shelf).

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":"invite","profile_fields":[{"name":"name","type":"text","label":"First name"}],"display_field":"name","path":"/app"}
```

Meeting replies (rsvps): users add these rows themselves on the pages.

{"site":"<site>","list":"rsvps","label":"Meeting replies","fields":[{"name":"meeting","type":"text","label":"Which meeting?","required":true},{"name":"coming","type":"choice","label":"Are you coming?","required":true,"options":["Yes","Maybe","No"]},{"name":"bringing","type":"text","label":"Bringing something for the table?"}]}

Book votes (votes): users add these rows themselves on the pages.

{"site":"<site>","list":"votes","label":"Book votes","fields":[{"name":"book","type":"text","label":"Your pick","required":true},{"name":"why","type":"long_text","label":"Why this one?","required":true},{"name":"poll","type":"text","label":"Which vote","required":true}]}

Notes for the meeting (thoughts): users add these rows themselves on the pages.

{"site":"<site>","list":"thoughts","label":"Notes for the meeting","fields":[{"name":"book","type":"text","label":"Book","required":true},{"name":"rating","type":"choice","label":"Your rating","required":true,"options":["5","4","3","2","1"]},{"name":"thoughts","type":"long_text","label":"Your thoughts","required":true},{"name":"favourite_line","type":"text","label":"A line you'd like read out"},{"name":"read_as","type":"choice","label":"Read it out","required":true,"options":["With my name","Without my name"]}],"status_options":["Received","On Maud's list","Read out"],"reply":true}

Reading progress (pages): users add these rows themselves on the pages.

{"site":"<site>","list":"pages","label":"Reading progress","fields":[{"name":"book","type":"text","label":"Book","required":true},{"name":"on_page","type":"number","label":"Page","required":true},{"name":"line","type":"text","label":"Where in the book"}]}

Meetings attended (attendance): 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":"attendance","label":"Meetings attended","fields":[{"name":"item","type":"text","label":"For","required":true}]}
```

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 (club name, meeting day, time and venue, host's name and email, phone number, this season's books and meeting dates, the shortlist for the next vote and its closing date, the reward for meetings attended, 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 does it meet?
- Who hosts, who scans members in at the door, and how many members do you keep to?
- Which books are this season's, with their meeting dates, and what was read earlier this year?
- What are the four shortlisted books for the next vote, with a line about each, and when does the vote close?
- What discussion questions does the host set for this month's book?
- What do members get for coming regularly (for example a free paperback every tenth meeting), and who pays for it?
- What email and phone should people use, and how long should the privacy notice say you keep members' details and notes?
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: "chapter" (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, 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.