Pledge: Membership & community website template

An app template for a community orchard charity: monthly donors sign in to see what their level paid for this season, read the impact updates, book a volunteer Saturday and get a reply from the team, and collect a stamp at the gate for every Saturday worked, ten for a case of the orchard's apple juice. Friend is free; Seed, Grow and Orchard are monthly gifts. A public page with the levels and a one-off gift, eight 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/Pledge

Copy the prompt Preview (opens in a new tab)

Who it suits

Made for: community orchards and food-growing charities, small charities that take monthly gifts, friends groups and supporters' clubs that run a donor area, recurring donations for a charity, friends of a park, community garden donors, monthly patrons, supporters' updates, volunteer rota for a charity, conservation volunteers, friends of a nature reserve. In the gallery under Membership & community.

Its 10 pages

Home: The public page: a red poster with the crate label and its tree row, the app at real size, the orchard in numbers, three monthly levels as crate labels and Friend, volunteer Saturdays through the year, a one-off gift, where the money went last year, and Sign in
Home: The donor's home: their level as a crate label with a row of apples for the trees it keeps in care, their next volunteer Saturday as an almanac page with its status and reply, work days toward the juice share with Show my code, the winter appeal, the latest reply and this month's update; signed out, a welcome with Continue with email
Updates: Every impact update, newest first, with the numbers each one reports
This month's update: The latest update in full: what was done, what the levels paid for, and what's next
Volunteer: The next four open Saturdays with each one's job, the request form (closes at noon on the Friday before), and the donor's requests with the team's status and reply
Volunteer card: The code to show at the gate, work days toward a case of apple juice, the juice share when ready and every work day stamped
Giving: The donor's level as a crate label with its trees, what it pays for this winter, the appeal, Gift Aid, a one-off gift, and the levels as crate labels with Give monthly buttons
Ask the team: Send the team a note and read their replies, with each note's status
Account: Profile, level and renewal, billing, devices and leaving, and links to the card, notes and privacy
Privacy: The privacy notice, with blanks the charity fills in

Look: Apple crate labels on timber slats: apple red, leaf and sky, slab lettering and a row of apples per tree; light, bold, classic; fonts Alfa Slab One and Lato.

Ready for: payments, once you ask your AI to turn it on.

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 charity name and registered number, address, phone and email, director, the four levels and their monthly prices, what each level pays for and one-off gift amounts), 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 Pledge template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Pledge": 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: "pledge" 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: Apple crate labels on timber slats: apple red, leaf and sky, slab lettering and a row of apples per tree (light, bold, classic)
Pages: Home (index.html): The public page: a red poster with the crate label and its tree row, the app at real size, the orchard in numbers, three monthly levels as crate labels and Friend, volunteer Saturdays through the year, a one-off gift, where the money went last year, and Sign in; Home (app/index.html): The donor's home: their level as a crate label with a row of apples for the trees it keeps in care, their next volunteer Saturday as an almanac page with its status and reply, work days toward the juice share with Show my code, the winter appeal, the latest reply and this month's update; signed out, a welcome with Continue with email; Updates (app/updates.html): Every impact update, newest first, with the numbers each one reports; This month's update (app/update.html): The latest update in full: what was done, what the levels paid for, and what's next; Volunteer (app/volunteer.html): The next four open Saturdays with each one's job, the request form (closes at noon on the Friday before), and the donor's requests with the team's status and reply; Volunteer card (app/card.html): The code to show at the gate, work days toward a case of apple juice, the juice share when ready and every work day stamped; Giving (app/giving.html): The donor's level as a crate label with its trees, what it pays for this winter, the appeal, Gift Aid, a one-off gift, and the levels as crate labels with Give monthly buttons; Ask the team (app/messages.html): Send the team a note and read their replies, with each note's status; Account (app/account.html): Profile, level and renewal, billing, devices and leaving, and links to the card, notes and privacy; Privacy (privacy.html): The privacy notice, with blanks the charity fills in
Fonts: Alfa Slab One, Lato (Google Fonts)
Live demo: https://try-pledge.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Pledge in a browser land there). The template's own files: https://pagelemon.com/templates/pledge/; the page about it: https://pagelemon.com/tp/Pledge/use
Manifest: https://pagelemon.com/templates/pledge/template.json (machine-readable: files, customise, slots, facts, interview)

Files

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

Notes for Pledge (its `customise` rules)

Brookside Orchard Trust, Brook Lane, Ottery Hythe, the director Nkem Ashworth-Lyle, the volunteer lead Ruth Pell, the registered charity number and the phone in the header, footer, titles and privacy notice: replace every data-pl-fill fact with the charity's own, and the appeal, the impact updates and the spending chart with its own figures. Also replace site.webmanifest name and short_name.
Set the four levels with save_plan (friend free; seed £5, grow £12 and orchard £25 a month) and change the prices on index.html and app/giving.html together.
Make the bookings and messages lists with save_app_list exactly as memberApp.lists says (status_options and reply on). The Saturdays' jobs are in app.js (SEASON, a rota per month that turns one job a week; SESSIONS for one-off changes) and in the task options: change them together.
The stamps list and its scan actions: save_app_list for stamps with scan exactly as memberApp.scan says (Work day, goal 10, one a day; Juice share redeems 10). Staff who stamp at the gate need the Scan members permission. Change the reward text on app/card.html and app/index.html if the goal or reward changes.
Fill in every highlighted blank on privacy.html before donors use the site (not legal advice: https://pagelemon.com/agents/member-app-legal).
Each impact update is static HTML: put the newest at the top of app/updates.html and its full text on app/update.html, and change the teaser on app/index.html.
Adults only. Never collect postal addresses, tax details, Gift Aid declarations, card numbers or bank details in the app: Gift Aid declarations are made on the charity's paper form, and payments go through Stripe.
The tree row: £14 keeps one tree in care for a year, so Seed shows 4 apples, Grow 10 and Orchard 21 (index.html, app/index.html, app/giving.html). If your costs or levels differ, change the sentence and the number of <li> in each .p-apples list together.
Colours: Edit the --p-* tokens at the top of styles.css (Apple Red, Leaf, Sky, Cider Cream, Crate Wood, ink); the kit's --k-* tokens follow them. The dark scheme follows the device: the orchard at night, deep leaf with a starry sky band.
Fonts: Alfa Slab One for crate-label lettering and headings, Lato for text, both from Google Fonts (one link in every page head).
Sections: Member pages live under /app and use the data-pl-view markup and the shared app kit (kit.css, kit.js, kit-icons.svg; node scripts/sync-app-kit.mjs pledge). setup_app with signup open and the first-name profile field, so anyone can join as a Friend and staff see the first name when they scan. Then save_app_list for bookings, messages and stamps (with scan), then save_plan for friend (free), seed, grow and orchard (monthly). The level cards sit inside data-pl-if="plan:<level>" and the Give monthly buttons inside no-plan. The team confirms bookings and answers notes in the Dashboard (status and reply); staff stamp work days by scanning the donor's code at the gate.
Images: art/label-scene.svg is the Friend and signed-out crate label's picture (a sun over hills, apple trees and one big apple); art/crate-seed.svg, art/crate-grow.svg and art/crate-orchard.svg are the Seed, Grow and Orchard labels' pictures (a sapling with its guard, a pruned tree with the chipper, a full tree with a ladder and a crate); the label's arched name is live text in each page. art/task-*.svg and art/press.svg are the Saturday jobs as four-colour crate-label drawings (prune, plant, fence, mulch, pick, press); app.js picks one per Saturday by its job. art/apple.svg draws the tree row and stamps, art/hills.svg the hill line under each sky band, and the favicon is the apple on a red label. To use a photo of the orchard, swap a task drawing for a landscape 4:3 photo. Never a stranger's face: show volunteers' hands, tools or backs.

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":"First name","required":true}],"display_field":"name","path":"/app"}
```

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

{"site":"<site>","list":"bookings","label":"Volunteer Saturdays","fields":[{"name":"task","type":"choice","label":"Job","required":true,"options":["Pruning the old block","Planting bare-root trees","Mulching and weeding","Fencing and tree guards","Picking","Pressing"]},{"name":"date","type":"date","label":"Saturday","required":true},{"name":"guests","type":"choice","label":"Who's coming","required":true,"options":["Just me","Me and 1 guest","Me and 2 guests"]},{"name":"tools","type":"choice","label":"Tools","required":true,"options":["Borrow ours","Bringing my own"]},{"name":"memo","type":"text","label":"Anything we should know"}],"status_options":["Requested","Confirmed","Came along","Cancelled"],"reply":true}

Notes to the team (messages): users add these rows themselves on the pages.

{"site":"<site>","list":"messages","label":"Notes to the team","fields":[{"name":"topic","type":"choice","label":"Topic","required":true,"options":["Volunteering","My monthly gift","Fruit and food bank","Events","Something else"]},{"name":"message","type":"long_text","label":"Your message","required":true}],"status_options":["Sent","Read","Answered"],"reply":true}

Work days (stamps): 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":"stamps","label":"Work days","fields":[{"name":"item","type":"text","label":"For","required":true}]}
```
Plans (save_plan; the pages use data-pl-if="plan:<id>" and join buttons): friend "Friend" (free); seed "Seed" (paid, sample price 5.00 GBP a month; ask the user for theirs); grow "Grow" (paid, sample price 12.00 GBP a month; ask the user for theirs); orchard "Orchard" (paid, sample price 25.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 (charity name and registered number, address, phone and email, director, the four levels and their monthly prices, what each level pays for, one-off gift amounts, impact updates, where the money went last year, volunteer days, times, jobs and places, volunteer reward, current appeal and its progress, team names). If they can't answer one, remove that element rather than inventing it.
- What is your charity called, and where is the orchard or project?
- Which monthly levels will you offer, and what does each one pay for over a year?
- When are your volunteer days, and which jobs and how many places does each have?
- Would you like a reward for regular volunteers, and after how many days?
- What is your current appeal, its target and how far you've got?
- Which email address should donors write to, and who answers privacy questions?
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: "pledge" (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: each <img data-pl-photo="..."> says what photo belongs there and its shape. Swap in the user's photos (compressed, WebP or JPEG under about 300 KB, same aspect ratio, real alt), or keep the illustration. 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.