# Toast: a Page Lemon website template > An invite-only app template for a wedding: each invited guest signs in with the email their invitation went to, replies for every adult on it (coming or not, main course, dessert, a song), sees the couple confirm each reply, and finds the order of the day, travel, places to stay and their table in one place. A public save-the-date 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 Toast template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Toast": 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: "toast"` 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:** Stationery suite on linen: ink navy and dusty rose, an envelope with a pressed-flower liner and a pen-ticked reply card (light, calm, classic) - **Pages:** Save the date (`index.html`): The public page: the couple, the date and venue, the shape of the day and a Sign in to reply button; Home (`app/index.html`): The guest's home: greeting, the countdown card with replies sent and coming, quick actions, their latest replies with the couple's status, their table and what to do next; a welcome screen when signed out; Reply (`app/reply.html`): The names on the guest's invitation with Reply buttons, the reply form (coming, main, dessert, a song), and the replies sent with Received or Confirmed and the couple's note; The day (`app/day.html`): The order of the day from 13:30 to carriages at midnight, the barn, dress code and gifts; Travel (`app/travel.html`): Parking, the lane, train and the minibus home, and three places to stay with prices and the wedding-rate deadline; Table (`app/table.html`): The guest's place card (table and who they sit with) once the couple sets it, and the menu; Account (`app/account.html`): The guest's first name, the account block (sign-in, devices, leaving) and how to change a reply; Privacy (`privacy.html`): The privacy notice, with blanks the couple fills in - **Fonts:** Bodoni Moda, Albert Sans (Google Fonts) - **Live demo:** https://try-toast.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Toast in a browser land there). The template's own files: https://pagelemon.com/templates/toast/; the page about it: https://pagelemon.com/tp/Toast/use - **Manifest:** https://pagelemon.com/templates/toast/template.json (machine-readable: files, customise, facts, interview) ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "toast"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/toast/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/toast/index.html - https://pagelemon.com/templates/toast/privacy.html - https://pagelemon.com/templates/toast/app/index.html - https://pagelemon.com/templates/toast/app/reply.html - https://pagelemon.com/templates/toast/app/day.html - https://pagelemon.com/templates/toast/app/travel.html - https://pagelemon.com/templates/toast/app/table.html - https://pagelemon.com/templates/toast/app/account.html - https://pagelemon.com/templates/toast/styles.css - https://pagelemon.com/templates/toast/app.js - https://pagelemon.com/templates/toast/wedding.ics - https://pagelemon.com/templates/toast/kit.css - https://pagelemon.com/templates/toast/kit.js - https://pagelemon.com/templates/toast/kit-icons.svg - https://pagelemon.com/templates/toast/icons.svg - https://pagelemon.com/templates/toast/site.webmanifest - https://pagelemon.com/templates/toast/favicon.svg - https://pagelemon.com/templates/toast/art/hero-sprig.svg - https://pagelemon.com/templates/toast/art/barn.svg - https://pagelemon.com/templates/toast/art/stem-rose.svg - https://pagelemon.com/templates/toast/art/stem-sage.svg - https://pagelemon.com/templates/toast/art/stem-gold.svg - https://pagelemon.com/templates/toast/art/liner.svg - https://pagelemon.com/templates/toast/art/deckle.svg - https://pagelemon.com/templates/toast/art/map.svg - https://pagelemon.com/templates/toast/og.png - https://pagelemon.com/templates/toast/apple-touch-icon.png - https://pagelemon.com/templates/toast/icon-192.png - https://pagelemon.com/templates/toast/icon-512.png - https://pagelemon.com/templates/toast/icon-512-maskable.png ## Notes for Toast (its `customise` rules) - Imogen Ashcombe and Rafael Quintero-Byrne, Saturday 4 September 2027, Hartsfell Barn, Hartsfell Lane, Coldwater Edge QZ3 8PD, the reply-by date 31 July, rsvp@imogenandrafa.example.com and 07700 900 730 are the sample facts: replace them on every page and in site.webmanifest.name. The countdown reads data-s-countdown="2027-09-04" on app/index.html: change it too. - Fill in every highlighted blank on privacy.html with the couple before guests use the site (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; then invite_users with each invitation's email. - Make the replies list exactly as memberApp.lists says, with status_options Received and Confirmed and reply on. The couple confirms each reply in the Dashboard (Apps, Entries) with one status tap and, if they like, a short note the guest sees under it. Meal and dessert choices are the list's options: change them in app/reply.html too, in the same order, and keep (V) on the vegetarian main. - Make the invitation list (by owner) exactly as memberApp.lists says: one row per adult named on an invitation, assigned to the guest who signs in. app/reply.html lists them with a Reply button that fills in the name. - The table list (by owner): the couple assigns each guest a table and a seated-with line in August; the guest's place card shows on app/table.html and Home. - The order of the day, places to stay and menu are sample text on app/day.html, app/travel.html and app/table.html: replace them with the couple's own. - Wedding only: keep the replies to the list's fields. Guests send dietary and other needs to the couple by email, not through the form. Never ask for card, bank or ID numbers. - **Colours:** Edit the tokens at the top of styles.css: cotton #FBFAF7 card stock on a linen #EFEAE0 table, ink navy #1E2A4A, dusty rose #D9A3A0 (the envelope liner and your table), sage #9DB09A, and gold foil #C9A45C only on navy or as hairlines. The dark scheme follows the device: a navy night with the cards by candlelight. The Day page is the navy night view in both schemes (ts-night on its body). - **Fonts:** Google Fonts: Bodoni Moda (display: the names, the date, times, headings, in italic) and Albert Sans (text and labels), one in every page head and --ts-serif / --ts-sans in styles.css. If the couple prefers no font service, download both (OFL) into a fonts/ folder and switch to @font-face. - **Sections:** Public: index.html (the save-the-date poster: the names and the date, the invitation in its open envelope, a sample reply card and place card, the order of the day on navy, the folded map, sign-in) and privacy.html. Member pages under /app on the shared app kit (kit.css, kit.js, kit-icons.svg; never edit them): index.html (the invitation in its envelope, the reply card with a pen tick per name, the place card, the replies with the couple's notes), reply.html (the reply card large with the add form written on it, and the replies sent with status and note), day.html (the order of the day as a gold-ruled programme on navy), travel.html (the folded map card, getting there, three places to stay keyed A to C), table.html (the place card from the table list, the drawn table plan with the guest's table in rose, the menu, the party's choices), account.html (the account parts as stationery sheets). Tabs: Home, Reply, The day, Travel, Table. Template pieces are the ts-* classes in styles.css; app.js does the countdown, the pen ticks, the falling petals, the reply form and marks the guest's table on the plan (the table field must match a table name in the plan's data-ts-table). - **Images:** Drawn art, no photos: art/hero-sprig.svg (the pressed sprig on the invitation), art/stem-rose.svg, art/stem-sage.svg and art/stem-gold.svg (pressed stems, 240×480), art/liner.svg (the envelope liner tile), art/deckle.svg (the invitation's deckled edge, a mask), art/barn.svg (the barn at night, 1200×800) and art/map.svg (the folded map, 1200×800: redraw it for the couple's venue). The table plan is inline SVG on app/table.html: rename the tables to match the couple's plan. icons.svg holds the extra icons (ring, glass, bed, car, pen, music). ## Offer these Page Lemon features - **Protect (password):** The RSVP, the meal choices and the private details (table, parking, places to stay) sit behind the invitation sign-in; the public page shows only the day and the place. - **Co-edit:** The couple can both edit the guest list, the replies and the table plan in the Dashboard, and add one more person to help with the seating. ## 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":"invite","profile_fields":[{"name":"name","type":"text","label":"First name"}],"display_field":"name","path":"/app"} ``` - **Guest replies** (`replies`): users add these rows themselves on the pages. ```json {"site":"","list":"replies","label":"Guest replies","fields":[{"name":"guest_name","type":"text","label":"Guest's name","required":true},{"name":"coming","type":"choice","label":"Coming?","required":true,"options":["Yes","No"]},{"name":"meal","type":"choice","label":"Main course","options":["Slow-roast lamb","Wild mushroom wellington (V)","Hake with samphire"]},{"name":"dessert","type":"choice","label":"Dessert","options":["Lemon posset","Chocolate torte"]},{"name":"song","type":"text","label":"A song to get you dancing"}],"status_options":["Received","Confirmed"],"reply":true} ``` - **Names on the invitation** (`invitation`): 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":"invitation","label":"Names on the invitation","fields":[{"name":"guest_name","type":"text","label":"Guest's name","required":true}]} ``` - **Table plan** (`table`): 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":"table","label":"Table plan","fields":[{"name":"table","type":"text","label":"Table"},{"name":"seat_with","type":"text","label":"Seated with"}]} ``` ## 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 (the couple's names, the wedding day and date, the ceremony, dinner and carriages times, the venue address and map link, parking and dress code, three places to stay nearby, the reply-by date, the contact email and phone, the privacy contact and address). If they can't answer one, remove that element rather than inventing it. - What are your names, and what is the wedding day and date? - Where is the wedding, and what are the ceremony, dinner and carriages times? - What are the main course and dessert choices for your guests, and what is the reply-by date? - Which places to stay are nearby, and how far is each from the venue? - Who should guests write to with questions, and what phone number should they call? - Which guests get a sign-in: the email each invitation was sent to? - 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: "toast"` (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, 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.