# Aftershow: a Page Lemon website template > An app template for a podcast's supporters: listeners hear every public episode free; Supporters (£4 a month) and Producers (£40 a year) get a monthly bonus feed of walk-alongs, outtakes and map deep-dives, and everyone can send questions to the mailbag and follow each one from Received to the episode that answers it. A public show page, five member pages under /app and a privacy notice with blanks. You are reading this because the user wants their own website made from the Aftershow template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Aftershow": 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: "aftershow"` 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:** Walking map: Explorer Orange map covers with sheet numbers, contour sheets and a dashed red footpath player (light, bold, modern) - **Pages:** The show (`index.html`): The public page: the show, the latest free episodes with play links, the three plans and the mailbag; Home (`app/index.html`): The member's home: their plan card (or a Support prompt for free listeners), the newest bonus episode, quick actions, their mailbag messages with status, the next episode; a welcome screen when signed out; Bonus (`app/bonus.html`): The bonus episodes with covers, runtime and play, open to Supporters and Producers; a locked feed with the plans for everyone else; Mailbag (`app/mailbag.html`): Send a question, myth or walk; counts of sent, shortlisted and answered; each message with its status timeline and the hosts' reply naming the episode; Support (`app/plans.html`): Listener (free), Supporter (£4 a month) and Producer (£40 a year) with what each gets and the join buttons; Account (`app/account.html`): The member's first name, the account block (plan, billing, devices, leaving) and the producer credit; Privacy (`privacy.html`): The privacy notice, with blanks the Site Owner fills in - **Fonts:** Barlow Condensed, Source Serif 4 (Google Fonts) - **Live demo:** https://try-aftershow.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Aftershow in a browser land there). The template's own files: https://pagelemon.com/templates/aftershow/; the page about it: https://pagelemon.com/tp/Aftershow/use - **Manifest:** https://pagelemon.com/templates/aftershow/template.json (machine-readable: files, customise, facts, interview) ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "aftershow"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/aftershow/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/aftershow/index.html - https://pagelemon.com/templates/aftershow/privacy.html - https://pagelemon.com/templates/aftershow/app/index.html - https://pagelemon.com/templates/aftershow/app/bonus.html - https://pagelemon.com/templates/aftershow/app/mailbag.html - https://pagelemon.com/templates/aftershow/app/plans.html - https://pagelemon.com/templates/aftershow/app/account.html - https://pagelemon.com/templates/aftershow/styles.css - https://pagelemon.com/templates/aftershow/kit.css - https://pagelemon.com/templates/aftershow/kit.js - https://pagelemon.com/templates/aftershow/kit-icons.svg - https://pagelemon.com/templates/aftershow/icons.svg - https://pagelemon.com/templates/aftershow/site.webmanifest - https://pagelemon.com/templates/aftershow/favicon.svg - https://pagelemon.com/templates/aftershow/art/map-hero.svg - https://pagelemon.com/templates/aftershow/art/cover-walk.svg - https://pagelemon.com/templates/aftershow/art/cover-outtakes.svg - https://pagelemon.com/templates/aftershow/art/cover-map.svg - https://pagelemon.com/templates/aftershow/art/cover-ford.svg - https://pagelemon.com/templates/aftershow/art/cover-gate.svg - https://pagelemon.com/templates/aftershow/art/cover-bend.svg - https://pagelemon.com/templates/aftershow/og.png - https://pagelemon.com/templates/aftershow/apple-touch-icon.png - https://pagelemon.com/templates/aftershow/icon-192.png - https://pagelemon.com/templates/aftershow/icon-512.png - https://pagelemon.com/templates/aftershow/icon-512-maskable.png ## Notes for Aftershow (its `customise` rules) - Lost Footpaths, Tamsin Rowe-Abara and Gil Fennimore, the address, phone and email: replace them on every page and in site.webmanifest; replace the four public episodes on index.html and the six bonus episodes on app/bonus.html and app/index.html with the show's own titles, runtimes, notes and audio file links. - Fill in every highlighted blank on privacy.html with the Site Owner before members use the site (not legal advice: https://pagelemon.com/agents/member-app-legal). - setup_app with signup open, the profile fields name (First name) and credit_name (the name Producers want read in the credits), display_field name. - Make the mailbag list exactly as memberApp.lists says, with the segment options Question, Myth or fact and Recommend us a walk, status_options Received, Shortlisted, Answered on air and Read, not on air (the end state for messages that are not used, with a short thank-you reply) and reply on. The hosts move each message along in the Dashboard (Apps, Entries) and reply with the episode and timestamp; the member sees both on app/mailbag.html and Home. - Set the plans with save_plan: listener (free), supporter (£4 a month) and producer (£40 a year). Change prices on index.html and app/plans.html together. - A new bonus episode is static HTML: add its card inside both the plan:supporter and plan:producer blocks on app/bonus.html (and as the newest on app/index.html), and a locked card in the no-plan block. Its cover is an m-cover with the next sheet number (B7) and one of art/cover-*.svg in its window. - Adults only. Never adapt this app to collect health data or children's data, and never ask for card, bank or ID numbers. - **Colours:** Edit the --m-* tokens at the top of styles.css (Explorer Orange covers, Map White, Contour Brown, Moor Green, Path Red); the dark scheme is a night map in deep brown-black, keeps the orange covers and follows the device - **Fonts:** Barlow Condensed (display, sheet numbers, cover titles) with Source Serif 4 (episode notes and reading text), from Google Fonts; one link in every page head - **Sections:** Public: index.html 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), bonus.html (plan-gated feed), mailbag.html (the add form, totals and the messages with status and reply), plans.html (join buttons), account.html (the account block). Tabs: Home, Bonus, Mailbag, Support, Account. Template pieces are the m-* classes in styles.css: m-cover (an episode map cover), m-route (the grid-reference scrubber with the walked footpath), m-card (a mailbag postcard with its postmark). - **Images:** art/map-hero.svg (1600×1000) is the unfolded walking map; art/cover-walk.svg, cover-outtakes.svg, cover-map.svg, cover-ford.svg, cover-gate.svg and cover-bend.svg (400×400) are the map windows on the episode covers per kind (drawn contours, a trig point, a stile). Replace them with the show's own artwork in the same frames. icons.svg holds the extra icons (headphones, mic, play, heart). ## 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. ```json {"site":"","signup":"open","profile_fields":[{"name":"name","type":"text","label":"First name"},{"name":"credit_name","type":"text","label":"Name for the credits (Producers)"}],"display_field":"name","path":"/app"} ``` - **Mailbag** (`mailbag`): users add these rows themselves on the pages. ```json {"site":"","list":"mailbag","label":"Mailbag","fields":[{"name":"segment","type":"choice","label":"Segment","required":true,"options":["Question","Myth or fact","Recommend us a walk"]},{"name":"question","type":"long_text","label":"Your question, myth or walk","required":true},{"name":"name_on_air","type":"text","label":"Name to read out (optional)"}],"status_options":["Received","Shortlisted","Answered on air","Read, not on air"],"reply":true} ``` - **Plans** (`save_plan`; the pages use `data-pl-if="plan:"` and join buttons): `listener` "Listener" (free); `supporter` "Supporter" (paid, sample price 4.00 GBP a month; ask the user for theirs); `producer` "Producer" (paid, sample price 40.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 (show name, hosts' names, episode numbers and runtimes, supporter and producer prices, studio address, contact email and phone, bonus episode list, mailbag rules). If they can't answer one, remove that element rather than inventing it. - What is the show called, and who hosts it? - How often do you release episodes, and how many are out so far? - What do supporters get beyond the public episodes? - What does a supporter pay a month, and what does a producer pay a year? - Which email address and phone number should listeners and members use? - What address 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: "aftershow"` (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.