# Gleam: a Page Lemon website template > A crisp home-cleaning site for a cleaning company that books a first clean or a quote call by phone or email, then agrees a regular schedule with the same cleaner and emails a payment link after each visit. Services, areas and a room-by-room checklist are all on the page. You are reading this because the user wants their own website made from the Gleam template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Gleam": 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: "gleam"` 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:** Fresh linen (light, bold, modern) - **Pages:** Home (`index.html`): Promise, three steps from first clean to regular schedule, prices from, areas, reviews and booking CTA; Services (`services.html`): Six services with what is included and starting prices, plus a room-by-room checklist card; Areas (`areas.html`): Five covered postcode districts with the days we clean each one, and a postcode check; Book (`book.html`): Booking picker for a first clean or a free quote call: service, home size, day, time; Pay (`pay.html`): Pay for a clean: the emailed payment link, how to ask for it again and how payment works; FAQ (`faq.html`): Keys and access, pets, cancellations within 48 hours, same cleaner, products, insurance, breakages - **Fonts:** Outfit, Figtree (Google Fonts) - **Colours:** `--paper` #fbfefd, `--mint` #d7f1e6, `--teal` #0d4f52, `--teal-ink` #0b3d40, `--lemon` #ffe45c - **Live demo:** https://pagelemon.com/templates/gleam/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Gleam; the page about it is https://pagelemon.com/tp/Gleam/use) - **Manifest:** https://pagelemon.com/templates/gleam/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Flat SVG art in a fresh-linen palette: crisp white and mint fills, deep teal outlines and shelves, lemon sparkles. Simple layered shapes, no gradients or filters, drawn to read as finished at full size. To sketch similar art: "A tidy arched window over a shelf of folded white linen, with mint wall dots, a teal shelf and small lemon sparkle stars, flat vector style with thin teal outlines." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "gleam"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/gleam/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/gleam/index.html - https://pagelemon.com/templates/gleam/services.html - https://pagelemon.com/templates/gleam/areas.html - https://pagelemon.com/templates/gleam/book.html - https://pagelemon.com/templates/gleam/pay.html - https://pagelemon.com/templates/gleam/faq.html - https://pagelemon.com/templates/gleam/404.html - https://pagelemon.com/templates/gleam/privacy.html - https://pagelemon.com/templates/gleam/styles.css - https://pagelemon.com/templates/gleam/script.js - https://pagelemon.com/templates/gleam/favicon.svg - https://pagelemon.com/templates/gleam/og.png - https://pagelemon.com/templates/gleam/apple-touch-icon.png - https://pagelemon.com/templates/gleam/art/hero-linen.svg - https://pagelemon.com/templates/gleam/art/kitchen-service.svg - https://pagelemon.com/templates/gleam/art/areas-map.svg ## Notes for Gleam (its `customise` rules) - Brightwell & Co. Home Cleaning - Ashby Vale, Kettle Green, Northgate - 2 Pantile Mews, Ashby Vale QR8 5JD - 01632 960 855 - hello@brightwellclean.example.com - Lowri Pembridge-Okafor - **Colours:** Change the palette tokens at the top of styles.css (paper, mint, teal, lemon). Keep teal dark enough for the lemon buttons to read, and the lemon for accents and buttons only, never body text. - **Fonts:** Outfit 600 and 700 for headings, Figtree 400, 600 and 700 for body: two Google Font families, four font files. - **Sections:** The booking picker (book.html) lists every service in services.html, with the same names and starting prices. Booking questions on book.html are q_access (how we get in) and q_pets (pets at home), plus q_home_size (options: Studio or 1 bed, 2 bedrooms, 3 bedrooms, 4 bedrooms or more) and q_postcode (postcode of the home); set up matching booking questions with the same names and options. Keep the picker's sample days on Mon to Sat and its times inside 09:00 to 13:00 so they fit office and Saturday hours. Edit the services and areas lists, not the HTML. Replace the sample reviews with real ones or remove them. The pay page has no form: the emailed payment link does the work. - **Images:** Replace art/hero-linen.svg (hero, 1600×1000), art/kitchen-service.svg (services, 1200×900) and art/areas-map.svg (areas, 1200×900) with real photos of a cleaned home, cropped to the same frames; WebP under 300 KB each. 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 (company name, office address and postcode, phone, email, opening hours for the office and for cleans, service areas, postcode districts and days, starting prices and units for each service, founder name, cleaner employment, DBS and insurance claims, cancellation policy (48 hours), payment link and reference process, real customer reviews, social links). If they can't answer one, remove that element rather than inventing it. - What is your cleaning company called, and who runs it? - Which postcodes and days do you cover? - What phone number and email should people use? - What do you charge to start for each service, and per visit or per hour? - Are your cleaners employed by you, and what checks and insurance do they have? - How do you agree the regular schedule and send payment links after each clean? 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: "gleam"` (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: 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. - 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. ## 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.