# Tidy: a Page Lemon website template

> A friendly home-services template with rounded Sunday-room illustrations, peach, mint and lilac colours, and a live room-and-frequency price estimator.

You are reading this because the user wants their own website made from the Tidy template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Tidy": 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: "tidy"` 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:** Soft Sunday rooms (light, calm, modern)
- **Pages:** Home (`index.html`): Friendly introduction, service mosaic, cleaning process, estimator, kit and sample review; Services (`services.html`): Illustrated regular, deep and moving cleans, scope and guide prices; Prices (`prices.html`): Room-and-frequency estimator, static guide table, extras and booking questions; Areas (`areas.html`): Illustrated local neighbourhoods and covered postcodes; Reviews (`reviews.html`): Clearly labelled sample feedback and service promises; Get a quote (`quote.html`): Contact slot, phone and email fallbacks, quote checklist and office address
- **Fonts:** DynaPuff, Lato (Google Fonts)
- **Colours:** `--paper` #fff9f2, `--ink` #392b43, `--peach` #f5cbbb, `--mint` #dcebe0, `--lilac` #dfd2ee, `--butter` #f3dc91
- **Live demo:** https://pagelemon.com/templates/tidy/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Tidy/preview)
- **Manifest:** https://pagelemon.com/templates/tidy/template.json (machine-readable: files, customise, slots, facts, interview)

## How the visuals were made

SVG files in art/ (home, kitchen, kit, neighbourhood) are rounded, friendly interiors: flat peach, mint, lilac and butter fills with thick dark-plum outlines and no gradients or filters. They are illustrations that could be swapped for photos; the CSS only adds simple pseudo-element decoration.

To sketch similar art: "Draw a cozy flat SVG room with an arched window, a plant and a tidy counter, in peach, mint, lilac and butter yellow with thick rounded plum outlines."

## Files

With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "tidy"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/tidy/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts.

- https://pagelemon.com/templates/tidy/index.html
- https://pagelemon.com/templates/tidy/services.html
- https://pagelemon.com/templates/tidy/prices.html
- https://pagelemon.com/templates/tidy/areas.html
- https://pagelemon.com/templates/tidy/reviews.html
- https://pagelemon.com/templates/tidy/quote.html
- https://pagelemon.com/templates/tidy/404.html
- https://pagelemon.com/templates/tidy/privacy.html
- https://pagelemon.com/templates/tidy/styles.css
- https://pagelemon.com/templates/tidy/script.js
- https://pagelemon.com/templates/tidy/favicon.svg
- https://pagelemon.com/templates/tidy/og.png
- https://pagelemon.com/templates/tidy/apple-touch-icon.png
- https://pagelemon.com/templates/tidy/art/home.svg
- https://pagelemon.com/templates/tidy/art/kitchen.svg
- https://pagelemon.com/templates/tidy/art/kit.svg
- https://pagelemon.com/templates/tidy/art/neighbourhood.svg

## Notes for Tidy (its `customise` rules)

- Sunday Home
- Elmsby
- Hartsholm
- Clover End
- Little Wren
- 8 Clover Yard, Elmsby, EB1 2QT
- 01632 960 823
- hello@example.com
- Nora Whyte
- Ivo Lane
- **Colours:** Change the six palette tokens in styles.css and recolour the SVG art to match; keep plum ink dark enough for readable pastel text.
- **Fonts:** DynaPuff 600 display and Lato 400/700 body; three font files across two Google Font families.
- **Sections:** Keep the room estimator, static price table and real tel/mailto fallbacks. Update data-base, data-room-rate and radio frequency values in both estimators along with all table/add-on prices. Rooms means bedrooms, living rooms and kitchen; one bathroom included. Activate forms through Page Lemon slots, then activate the inert privacy forms paragraph. Remove every sample review unless the owner supplies real feedback. Verify and replace all data-pl-fill facts, JSON-LD and example.com social link before launch.
- **Images:** Replace art/home.svg with a bright cleaned living room (1200×1000; service crop 4:3), art/kitchen.svg with a freshly cleaned kitchen (1200×900), art/kit.svg with real cleaning products or team kit (1200×900), and art/neighbourhood.svg with a local photo or original area illustration (1200×1000). Preserve photo-frame aspect ratios; use WebP under 300 KB. The illustrated map is decorative, not a geographical claim. 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 (business name, phone, email, address and coordinates, hours, service areas and postcodes, service scope, insurance and vetting, eco-product claims, team names, prices and VAT treatment, estimator base rate, room rate and frequency multipliers, cancellation policy, response and rectification times, real customer reviews, privacy retention policy, social and canonical URLs). If they can't answer one, remove that element rather than inventing it.
   - What is your business called?
   - Which postcodes do you cover?
   - What phone number should people call?
   - What cleaning services do you offer?
   - How do you calculate your visit prices?
   - Which insurance and vetting claims can you verify?
   - Do you have real customer reviews to share?
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: "tidy"` (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 `<title>`, 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.