# Willow: a Page Lemon website template > A calm counselling practice site: a soft willow-and-river palette, a serif headline and a gentle layout that explains the approach, the fees and the confidentiality limits, then offers a free 20-minute intro call through a booking picker. You are reading this because the user wants their own website made from the Willow template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Willow": 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: "willow"` 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:** Willow and river light: soft willow green, river blue-grey and warm cream, with drooping willow-branch line art and water ripples (light, calm, classic) - **Pages:** Home (`index.html`): Who the counsellor works with, the free intro call, a willow-by-the-river frame and the book CTA; How I work (`approach.html`): Integrative approach, what a first session is like step by step, how long the work lasts, and confidentiality and its limits in plain words; Fees (`fees.html`): £65 a session as a fee list, a few lower-cost places, the 48-hour cancellation rule, how to pay by bank transfer after the session, and the book CTA; Book (`book.html`): Free 20-minute intro call booking slot with a phone and email fallback, the inert picker, what happens next, and a line not to share health details here; Contact (`contact.html`): Enquiry slot with the inert contact form, the practice address and front door, and the hours - **Fonts:** Lora, Nunito Sans (Google Fonts) - **Colours:** `--cream` #F6F1E6, `--willow` #4E6A52, `--river` #3E5C68, `--river-deep` #2F4A55 - **Live demo:** https://pagelemon.com/templates/willow/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Willow; the page about it is https://pagelemon.com/tp/Willow/use) - **Manifest:** https://pagelemon.com/templates/willow/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made art/river-hero.svg, art/room.svg and art/weir-house.svg are layered SVG drawings in the willow and river palette: a willow over a river, an empty counselling room with an arched window, and a brick house with a green door. art/branch.svg is drooping willow line art and art/ripples.svg is a water-ripple tile. No people and no identifiable places. To sketch similar art: "Calm, soft natural light: a willow over a still river, an empty counselling room with two armchairs and an arched window, a brick house with a green front door; willow green, river blue-grey and warm cream, no people, no signage." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "willow"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/willow/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/willow/index.html - https://pagelemon.com/templates/willow/approach.html - https://pagelemon.com/templates/willow/fees.html - https://pagelemon.com/templates/willow/book.html - https://pagelemon.com/templates/willow/contact.html - https://pagelemon.com/templates/willow/privacy.html - https://pagelemon.com/templates/willow/404.html - https://pagelemon.com/templates/willow/styles.css - https://pagelemon.com/templates/willow/script.js - https://pagelemon.com/templates/willow/favicon.svg - https://pagelemon.com/templates/willow/og.png - https://pagelemon.com/templates/willow/apple-touch-icon.png - https://pagelemon.com/templates/willow/art/river-hero.svg - https://pagelemon.com/templates/willow/art/room.svg - https://pagelemon.com/templates/willow/art/weir-house.svg - https://pagelemon.com/templates/willow/art/branch.svg - https://pagelemon.com/templates/willow/art/ripples.svg ## Notes for Willow (its `customise` rules) - Practice name 'Hester Calloway Counselling' in every title, the header wordmark, the footer, the JSON-LD and the privacy notice; replace the sample 'Hester Calloway' in the body copy with the counsellor's name - Address 'Room 2, The Weir House, 14 Osier Walk, Brindlemere QU7 4NA', telephone 01632 960 838 and email hello@hestercalloway.example.com: identical in the footer, the JSON-LD, the contact page and the booking fallback - Replace the sample training, history and years in practice in the About me section of approach.html with the counsellor's own; add a registration only when verified - Add a named professional registration and its verification link only when you have one; approach.html makes no membership claim until then - Fees on fees.html (the fee list rows: individual session £65.00 and lower-cost place £35.00) and the £65 figures on index.html and approach.html must match; keep the 48-hour cancellation rule consistent - Hours in the footer, contact page and JSON-LD openingHoursSpecification must match; the intro call times in the picker on book.html must fall inside them - The crisis note carries only the emergency-services sentence (999 or A&E), as written; add a named helpline only when a verified one is supplied - Never add a form that asks for health, diagnosis or medication details; the notes on book.html and contact.html say to talk on the call - **Colours:** Edit the :root tokens at the top of styles.css. Keep --willow and --river-deep at 4.5:1 or better against their text, and update the theme-color meta on every page - **Fonts:** Change the Google Fonts link on every page and --serif / --sans in styles.css (at most two families) - **Sections:** Each page is self-contained: header with at most three links and one CTA, the footer, the crisis note on index, approach, book and contact, and the mobile Call / Book / Directions bar. Booking slot (book.html, id intro): ask the counsellor for the intro-call days and times, add the booking, confirm the summary with them, then build the picker from the inert template in this design (fill it from slots_url, post JSON to post_url) and keep its link to booking_url for visitors without JavaScript. Test with one test booking before calling it live. Enquiry slot (contact.html, id enquiry): build the form from the inert template, keep the email fallback. Do not add a booking or contact form anywhere else. - **Images:** Replace the drawn art with photographs only if they are calm and show no identifiable clients: art/river-hero.svg (1600×1000, willow over the river, the hero), art/room.svg (1600×1200, the counselling room, keep the empty chairs), art/weir-house.svg (1000×1250, the front door of the house). Keep the width, height and data-pl-photo notes; WebP under 300 KB. The 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 (practice name and town, address (room, building, street, town, postcode), phone, email, opening hours, session fee and lower-cost place fee, cancellation notice period and late-cancellation fee, intro call length and times, supervision and any professional registration, training and years in practice (approach.html About me), access to the room (steps, parking, toilet)). If they can't answer one, remove that element rather than inventing it. - What is the practice called, and what is the address of the room? - What are your opening hours, and when can people book the free intro call? - What does a session cost, what is the lower-cost place fee, and how do you handle late cancellation? - Which counselling approaches do you draw on, and how do you handle supervision? - Do you offer sessions in person, online, or both, and how do people pay after a session? 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: "willow"` (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.