# Pantry: a Page Lemon website template > A plain-language food pantry site: tomato red, deep green and sunshine yellow on white, rounded Fredoka headings, big tap buttons, and an open-now light that tells people if they can come in today. You are reading this because the user wants their own website made from the Pantry template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Pantry": 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: "pantry"` 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:** Plain-language food bank, big colour blocks (light, bold, modern) - **Pages:** Home (`index.html`): Opening times and location up top with a live open-now light, what we need this week, how to get help in three steps, volunteer shifts, and how to give; Get help (`get-help.html`): How to get a parcel: what to bring, what you get, when we are open, and a delivery request form slot with a phone and email fallback; Volunteer (`volunteer.html`): Roles by type with the time each takes, next shifts, a coordinator portrait, and a volunteer sign-up form slot; Donate (`donate.html`): Drop-off rules, what the money buys at three amounts, where the money goes with honest running-cost figures, and a food drive form slot; About us (`about.html`): Founding story, year in numbers, the people who run it, and an honest what-did-not-work block - **Fonts:** Fredoka, Figtree (Google Fonts) - **Colours:** `--bg` #FFFFFF, `--ink` #17301F, `--accent` #C92E1E, `--green` #1F5C3B, `--yellow` #FFC83D - **Live demo:** https://pagelemon.com/templates/pantry/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Pantry/preview) - **Manifest:** https://pagelemon.com/templates/pantry/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Flat SVG placeholders in tomato red, deep green, sunshine yellow and pale green: crates of tins and vegetables, stocked shelves, volunteers at a sorting table, and a plain portrait. To sketch similar art: "Draw a flat SVG of crates of tins, bread and carrots on a hall table, in tomato red, deep green and sunshine yellow on pale green, with no outlines thicker than 8 px." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "pantry"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/pantry/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/pantry/index.html - https://pagelemon.com/templates/pantry/get-help.html - https://pagelemon.com/templates/pantry/volunteer.html - https://pagelemon.com/templates/pantry/donate.html - https://pagelemon.com/templates/pantry/about.html - https://pagelemon.com/templates/pantry/privacy.html - https://pagelemon.com/templates/pantry/404.html - https://pagelemon.com/templates/pantry/styles.css - https://pagelemon.com/templates/pantry/script.js - https://pagelemon.com/templates/pantry/favicon.svg - https://pagelemon.com/templates/pantry/og.png - https://pagelemon.com/templates/pantry/apple-touch-icon.png - https://pagelemon.com/templates/pantry/art/hero.svg - https://pagelemon.com/templates/pantry/art/shelf.svg - https://pagelemon.com/templates/pantry/art/volunteers.svg - https://pagelemon.com/templates/pantry/art/team.svg ## Notes for Pantry (its `customise` rules) - Replace every data-pl-fill fact: name, address, phone, email, hours, donation amounts and the example.com donation link. - Keep name, address and phone identical in the footer, the find-us block, the JSON-LD and the privacy page. - Rewrite the needs list on index.html each week (the meter classes: very-low, low, mid, ok) and keep the best-before note. - Replace the spending split and the 2025 numbers on about.html and donate.html with your own audited figures, or delete the block. - **Colours:** Edit the :root tokens at the top of styles.css. Keep tomato red and white contrast at 4.5:1 or better for text. - **Fonts:** Fredoka 600 for headings and Figtree 400 and 700 for body: three files. Change the Google Fonts link in every HTML head and the two font tokens in styles.css. - **Sections:** The open-now light reads the schedule in script.js (the slots array). Change it to match your opening days. Without JavaScript the hours table still shows the times. - **Images:** Replace art/hero.svg, art/shelf.svg and art/volunteers.svg with landscape 1600×1000 photos, and art/team.svg with a portrait 800×1000 photo. WebP under 300 KB each. Keep the width, height and data-pl-photo attributes. ## Offer these Page Lemon features - **Co-edit:** Volunteer coordinators edit the rota and the needs list together ## 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 (name, address, phone, email, hours, donation amounts and what they buy, online donation link, volunteer roles, shift times and dates, coordinator and trustee names, parcel contents and counts, spending split and accounts year, founding year and volunteer numbers, safeguarding and data retention policy). If they can't answer one, remove that element rather than inventing it. - What is the pantry called and where is it? - Which days and times do you hand out food? - What do you need this week, and where should drop-offs go? - How do people get a parcel, and what do they bring? - Who coordinates volunteers, and which roles and shifts do you need? - Where can people give money online, and what does each amount buy? - What email and phone should people use if they cannot come in? 2. **Get the files.** If you have the Page Lemon tool (the MCP connector at https://mcp.pagelemon.com, with a `deploy` tool), call `deploy` with `template: "pantry"` (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.** 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. 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, 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. - Regenerate `og.png` (1200×630) from the new home page if you can, or delete it and its `og:image` tags. 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 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: any paid plan; Booking: Team, Company or Enterprise), add the Forms or Booking plugin (`set_plugin`), put its `snippet_html` 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` and the template's fictional business name: 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. ## 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. `tar -czf - -C <dir> . | curl -sS --fail-with-body --data-binary @- https://api.pagelemon.com/v1/deploy` If `PAGELEMON_TOKEN` is set, or `~/.config/pagelemon/credentials` exists, add `-H "Authorization: Bearer <that token>"`. 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`): call its `deploy` tool with every file. See "No shell: the MCP connector" in https://pagelemon.com/agents. 3. **Neither:** tell the user to connect Page Lemon to this AI app once (steps at https://pagelemon.com/docs/connect), then ask you again. If they can't (for example ChatGPT's free plan), give them the site as one `index.html` file and send them to https://pagelemon.com/drop to put it online with no account (on a phone with no file, they can copy the whole code and paste it there). 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.