# Pour: a Page Lemon website template > A loud street-corner coffee bar with chunky display type, saturated colour blocks, sticker illustrations and a switchable HTML drinks board. You are reading this because the user wants their own website made from the Pour template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Pour": 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: "pour"` 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:** Loud street-corner coffee bar, chunky type, colour blocks (light, bold, modern) - **Pages:** Home (`index.html`): Street-corner poster, interactive drinks board, people, events and beans; Menu (`menu.html`): HTML drinks board with milk, sizes, prices, bakes and dietary information; Beans (`beans.html`): Roast profiles, coffee purchases and subscription payment slots; Events (`events.html`): Event calendar, tasting RSVP slot and visitor questions; Visit (`visit.html`): Address, map link, opening hours, directions, access and parking - **Fonts:** Changa One, Mulish (Google Fonts) - **Colours:** `--ink` #171b13, `--paper` #fff9e9, `--orange` #ff671d, `--acid` #e6ff55, `--blue` #154bec - **Live demo:** https://pagelemon.com/templates/pour/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Pour/preview) - **Manifest:** https://pagelemon.com/templates/pour/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made art/ holds placeholder flat SVG illustrations (cup, bean bag, awning, bakes, map) with thick black outlines, bold fills on acid yellow, starburst shapes and motion ticks, standing in for photos. CSS is mostly layout with acid-colored blocks and few effects. To sketch similar art: "Draw a bold flat SVG of a striped flat-white cup with thick black outlines on acid-yellow, plus a blue starburst and a few motion tick marks." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "pour"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/pour/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/pour/index.html - https://pagelemon.com/templates/pour/beans.html - https://pagelemon.com/templates/pour/404.html - https://pagelemon.com/templates/pour/menu.html - https://pagelemon.com/templates/pour/visit.html - https://pagelemon.com/templates/pour/events.html - https://pagelemon.com/templates/pour/privacy.html - https://pagelemon.com/templates/pour/styles.css - https://pagelemon.com/templates/pour/script.js - https://pagelemon.com/templates/pour/favicon.svg - https://pagelemon.com/templates/pour/og.png - https://pagelemon.com/templates/pour/apple-touch-icon.png - https://pagelemon.com/templates/pour/art/after-hours.svg - https://pagelemon.com/templates/pour/art/coffee-kick.svg - https://pagelemon.com/templates/pour/art/corner-bar.svg - https://pagelemon.com/templates/pour/art/corner-map.svg - https://pagelemon.com/templates/pour/art/house-beans.svg - https://pagelemon.com/templates/pour/art/morning-bakes.svg - https://pagelemon.com/templates/pour/art/spilled-it.svg ## Notes for Pour (its `customise` rules) - Replace every data-pl-fill fact, including names, roasts, origins, flavour notes, menu descriptions, dietary tags, prices, VAT terms, event dates and subscription terms. - Keep Pour, 14 Kickturn Street, Spindleford, SF3 8KT and 01632 960 812 identical in footer, visit page and JSON-LD; replace metadata, aria labels and schema facts too. - Replace Nia Finch, Cal Fenner and Ida Wardle with the real team and event hosts; verify all access, transport, parking, facilities and dog policies. - Replace payment and social example.com links with owner-supplied destinations. Update map queries, event JSON-LD, opening hours and coordinates. - **Colours:** Edit the five :root colour tokens in styles.css. Keep dark ink on orange/acid, and paper on cobalt for contrast. - **Fonts:** Update the Google Fonts link in all seven heads and --display/--body in styles.css. Changa One 400 and Mulish 400/700 use three files. - **Sections:** Five content pages plus matching privacy and 404. Native radio controls and CSS :has switch the HTML drinks board; mobile details works without JS. Keep all forms inside slot templates; payment and RSVP fallbacks remain links. Header has five links plus Find the bar; footer and mobile actions repeat it. - **Images:** Replace coffee-kick and house-beans square 1000×1000; corner-bar and morning-bakes landscape 1600×1000; after-hours portrait 800×1000. Preserve object-fit frames, width/height and data-pl-photo; WebP under 300 KB. corner-map 1000×1000 is an illustrative location frame, not navigation; replace with an accurate diagram or venue neighbourhood photo. Keep spilled-it 1000×1000 as decorative 404 art. Pipeline generates og.png and apple-touch-icon.png. ## 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, prices and dietary information, coffee origins and roast notes, team and event hosts, event dates and ticket policies, subscription, delivery and cancellation terms, access, facilities, parking and directions, coordinates and social/payment links). If they can't answer one, remove that element rather than inventing it. - What is your coffee bar called? - What is its full address? - What telephone number should visitors use? - What are your regular opening hours? - Which drinks, milk choices, sizes and prices are on your menu? - Which roasts and subscription terms should customers see? - Which events are coming up? 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: "pour"` (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.