Stub: village fetes and fairs website template

An app template for a one-day festival: ticket holders keep their ticket on their phone with a countdown, plan their day from the set times, and show a code at the gate, where stewards scan them in with their own phone. A public page with tickets and the line-up, six member pages 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/Stub

Copy the prompt Preview (opens in a new tab)

Who it suits

Made for: festivals and gig promoters, village fetes and fairs, small venues running gig nights, gig tickets, club nights, fairs and open days, conference check-in, festival entry. In the gallery under Membership & community.

Its 8 pages

Home: The public page: a screen-printed festival poster (12 JUN, the billing stack, the marsh at sunset), the wristband at real size and how it works, the ticket types with prices and Buy buttons, set times, getting there and sign-in
Home: The ticket holder's home: the wristband across the page (name, ticket type, gate, a tide-chart countdown to the gates and the scan block on its tab), their running order, gate status and times; a welcome screen when signed out
Ticket: The wristband at full size (type, name, gate, reference) with the scan block Show my code and the wallet buttons on its tab, the gate scans so far and the entry rules
Line-up: A poster stack per stage (Lantern and Samphire), billed by size with the headliner biggest, each set with Add to my day and your picks marked; the ceilidh and food
My day: Your picked sets as a running order on a tide-chart line from gates to last song, and a form to add a set with a note
Info: Getting there, access, what to bring, refunds and transfers, the festival phone
Account: The first name stewards see, the account block (sign-in, devices, leaving) and ticket help
Privacy: The privacy notice, with blanks the organiser fills in

Look: Screen-printed festival poster at night: coral sun, marsh ochre and navy, with a woven wristband and a tide chart; dark, bold, modern; fonts Bowlby One and Martian Mono.

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 festival name, date and gate times, address, contact email, phone and line-up and set times for each stage), 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 Stub template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Stub": 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: "stub" 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: Screen-printed festival poster at night: coral sun, marsh ochre and navy, with a woven wristband and a tide chart (dark, bold, modern)
Pages: Home (index.html): The public page: a screen-printed festival poster (12 JUN, the billing stack, the marsh at sunset), the wristband at real size and how it works, the ticket types with prices and Buy buttons, set times, getting there and sign-in; Home (app/index.html): The ticket holder's home: the wristband across the page (name, ticket type, gate, a tide-chart countdown to the gates and the scan block on its tab), their running order, gate status and times; a welcome screen when signed out; Ticket (app/ticket.html): The wristband at full size (type, name, gate, reference) with the scan block Show my code and the wallet buttons on its tab, the gate scans so far and the entry rules; Line-up (app/lineup.html): A poster stack per stage (Lantern and Samphire), billed by size with the headliner biggest, each set with Add to my day and your picks marked; the ceilidh and food; My day (app/day.html): Your picked sets as a running order on a tide-chart line from gates to last song, and a form to add a set with a note; Info (app/info.html): Getting there, access, what to bring, refunds and transfers, the festival phone; Account (app/account.html): The first name stewards see, the account block (sign-in, devices, leaving) and ticket help; Privacy (privacy.html): The privacy notice, with blanks the organiser fills in
Fonts: Bowlby One, Martian Mono (Google Fonts)
Live demo: https://try-stub.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Stub in a browser land there). The template's own files: https://pagelemon.com/templates/stub/; the page about it: https://pagelemon.com/tp/Stub/use
Manifest: https://pagelemon.com/templates/stub/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: "stub" copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/stub/ and save it with the same relative path (including art/). Fetch nothing else: templates have no external images or scripts.

Notes for Stub (its `customise` rules)

Saltmarsh Sessions, its date (Saturday 12 June 2027), gate times, address, organiser and contacts: replace them on every page and in site.webmanifest.name; keep short_name Stub unless the organiser picks another app name. The wristband countdown reads data-s-countdown="2027-06-12" on app/index.html, app/ticket.html and index.html: change that date too.
Fill in every highlighted blank on privacy.html before you sell tickets (not legal advice: https://pagelemon.com/agents/member-app-legal).
setup_app with signup invite, the profile field name (First name) and display_field name, so stewards see the holder's first name when they scan.
Make the tickets list (by owner) with save_app_list exactly as memberApp.lists says: one row per ticket, assigned to its holder once they have paid, then invite_users with their email. One ticket per account: each attendee signs in with their own email, because the gate code is per account.
Make the entry list and its scan actions with one save_app_list call: the list as memberApp.lists says and scan as memberApp.scan says. Checked in keeps goal 1 and daily_limit 1; the Re-entry daily_limit is how many times a holder may come back in. Gate staff need only Scan members.
Make the picks list (by member) exactly as memberApp.lists says. Its act options are the sets written as start time, act, stage, so they sort into running order; change them together with the rows on app/lineup.html and index.html.
Ticket sales: the Buy buttons on index.html link to the organiser's own Stripe Payment Links (one per ticket type). A payment does not add a ticket by itself: the organiser adds the ticket row and invites the buyer, as the steps on index.html say.
Festival tickets only: keep to first name, email, ticket and gate details; never add card, bank, ID or personal-life fields.
Colours: Edit the :root tokens at the top of styles.css: Night, Dusk Navy, Foam, Coral and Marsh Ochre. Both device schemes stay dark (the light one is dusk navy, the dark one night).
Fonts: Google Fonts: Bowlby One (poster billing, the date, names and prices) and Martian Mono (times, references, labels and text), one <link> in every page head and --s-display / --s-mono in styles.css. If the owner prefers no font service, download both (OFL) into a fonts/ folder and switch to @font-face.
Sections: Public: index.html (the poster, the wristband at real size, tickets, line-up, getting there) and privacy.html. Member pages under /app on the shared app kit (kit.css, kit.js, kit-icons.svg; never edit them): index.html (home: the wristband with the scan block on its tab and the tide-chart countdown), ticket.html (the wristband large with the scan block and wallet buttons), lineup.html (a poster stack per stage, billed by size), day.html (the picks form and the running order), info.html, account.html (the account block). Tabs: Home, Ticket, Line-up, My day, Info. Template pieces are the s-* (app) and p-* (public) classes in styles.css.
Images: art/marsh.svg (1600×600) is the public poster's two-colour screen print: a coral sun over the tidal marsh, ochre grass, the two stages on the far bank. art/poster.svg (800×920) is the same scene upright, for the signed-out welcome. art/site-map.svg and art/site-map-phone.svg are the site map in the same inks. Swap them for the event's own art in the same frames. favicon.svg is the wristband mark; the PNG icons are made from it. icons.svg holds the extra icons (ticket, music, tent).

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"}
```

Tickets (tickets): 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":"tickets","label":"Tickets","fields":[{"name":"ticket_type","type":"choice","label":"Ticket","required":true,"options":["Day","Concession","Evening"]},{"name":"ref","type":"text","label":"Reference","required":true},{"name":"holder","type":"text","label":"Name on ticket","required":true},{"name":"gate","type":"text","label":"Gate"}]}

Gate scans (entry): 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":"entry","label":"Gate scans","fields":[{"name":"gate","type":"text","label":"Gate","required":true}]}
```

My day (picks): users add these rows themselves on the pages.

{"site":"<site>","list":"picks","label":"My day","fields":[{"name":"act","type":"choice","label":"Set","required":true,"options":["11:30 Oriel Shaw, Lantern Stage","12:00 Brine Hollow, Samphire Stage","13:15 Hobb and Tamsin, Lantern Stage","13:45 Ada Greenlaw, Samphire Stage","15:00 The Quay Sisters, Lantern Stage","15:30 The Ropewalk Fiddlers, Samphire Stage","17:30 Mudflat Ensemble, Lantern Stage","18:15 Ninepenny Jig, Samphire Stage","20:00 Peg Loom, Samphire Stage","21:00 Vesper Lane, Lantern Stage"]},{"name":"memo","type":"long_text","label":"Note"}]}

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 (festival name, date and gate times, address, contact email, phone, line-up and set times for each stage, ticket types and prices, refund and transfer rules, privacy contact and address). If they can't answer one, remove that element rather than inventing it.
- What is the event called, and when and where is it?
- Which ticket types and prices do you sell?
- Who plays, on which stage, and at what time?
- How long before the day can people ask for a refund, and how do transfers work?
- Who on your team scans tickets at the gate? Each needs a Page Lemon sign-in: invite them as collaborators with only Scan members ticked.
- Which email address and phone number should buyers use?
- What address and privacy contact should the privacy notice show?
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: "stub" (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.