# Walkies: a Page Lemon website template
> An app template for a dog walker: clients keep a profile for each dog, book group or solo walks by the day and slot, follow each booking from Requested to Walked with the walker's reply, and read a report after every walk with the route, time, distance and an album link. Pay as you go or a weekly plan. A public page with the free meet and greet, six member screens under /app and a privacy notice with blanks.
You are reading this because the user wants their own website made from the Walkies template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Walkies": 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: "walkies"` 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:** Sky over field green: walks as a drawn park map with a tennis-ball route, dogs in collar tags (light, bold, modern)
- **Pages:** Home (`index.html`): The public page: services and prices, where Bea walks, how it works, the walker and the free meet and greet booking; Home (app) (`app/index.html`): Signed out: the welcome with the park map and sign-in. Signed in: the latest walk as a park map with your dogs' collar tags and the walk readout (minutes, km, route, how it went, photos), the next walk with its four-stop status and Bea's reply, the plan and the booking rules; Book a walk (`app/book.html`): Pick the dog, the walk (group, solo or puppy visit, with prices), the date and pick-up window and a note; the booking rules beside it; Walks (`app/walks.html`): Upcoming bookings with their status (Requested, Confirmed, Walked, Can't do that slot) and Bea's reply, Book another slot, Ask Bea to cancel (a cancellation Bea marks Cancelled), then past walks with Book again; Reports (`app/reports.html`): A report after every walk as a small park map with its own route: dog, route, minutes, distance, how it went and the photo album link, under the month's totals; Dogs (`app/dogs.html`): Each dog's profile with its photo, how Bea gets in, vet and walk notes, and the form to add a dog; Plan (`app/plan.html`): Pay as you go or the Weekday regular plan, what each covers and how renewal and cancelling work; Account (`app/account.html`): The account block (email, profile, plan, billing, devices, leaving); Privacy (`privacy.html`): The privacy notice for clients, with blanks the owner fills in
- **Fonts:** Bagel Fat One, Nunito Sans (Google Fonts)
- **Live demo:** https://try-walkies.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Walkies in a browser land there). The template's own files: https://pagelemon.com/templates/walkies/; the page about it: https://pagelemon.com/tp/Walkies/use
- **Manifest:** https://pagelemon.com/templates/walkies/template.json (machine-readable: files, customise, slots, facts, interview)
## Files
With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "walkies"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/walkies/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts.
- https://pagelemon.com/templates/walkies/index.html
- https://pagelemon.com/templates/walkies/privacy.html
- https://pagelemon.com/templates/walkies/app/index.html
- https://pagelemon.com/templates/walkies/app/book.html
- https://pagelemon.com/templates/walkies/app/walks.html
- https://pagelemon.com/templates/walkies/app/reports.html
- https://pagelemon.com/templates/walkies/app/dogs.html
- https://pagelemon.com/templates/walkies/app/plan.html
- https://pagelemon.com/templates/walkies/app/account.html
- https://pagelemon.com/templates/walkies/styles.css
- https://pagelemon.com/templates/walkies/app.js
- https://pagelemon.com/templates/walkies/kit.css
- https://pagelemon.com/templates/walkies/kit.js
- https://pagelemon.com/templates/walkies/kit-icons.svg
- https://pagelemon.com/templates/walkies/art/juno.webp
- https://pagelemon.com/templates/walkies/art/biscuit.webp
- https://pagelemon.com/templates/walkies/art/woodland-walk.webp
- https://pagelemon.com/templates/walkies/art/ellerby-green.webp
- https://pagelemon.com/templates/walkies/art/chip-seam.svg
- https://pagelemon.com/templates/walkies/art/stop-paw.svg
- https://pagelemon.com/templates/walkies/art/stop-ball.svg
- https://pagelemon.com/templates/walkies/art/park.svg
- https://pagelemon.com/templates/walkies/site.webmanifest
- https://pagelemon.com/templates/walkies/favicon.svg
- https://pagelemon.com/templates/walkies/og.png
- https://pagelemon.com/templates/walkies/apple-touch-icon.png
- https://pagelemon.com/templates/walkies/icon-192.png
- https://pagelemon.com/templates/walkies/icon-512.png
- https://pagelemon.com/templates/walkies/icon-512-maskable.png
## Notes for Walkies (its `customise` rules)
- Muddy Paws Walking Co. and Bea Langridge-Osei in the header, footer, titles and walker section; replace every data-pl-fill fact with the owner's own, and the services and prices on index.html, the walk options (with prices) in memberApp.lists bookings and app/book.html
- Fill in every highlighted blank on privacy.html with the Site Owner before clients use the site (not legal advice: https://pagelemon.com/agents/member-app-legal)
- Pick-up windows (9 to 11, 11 to 1, 1 to 3), the booking cut-off (6pm the day before) and the cancellation rule (free until 8pm the evening before) are on app/book.html, app/walks.html and index.html; change them together.
- The Weekday regular plan (£65 a week) covers five group walks Monday to Friday: the client books them in the app as usual and Bea doesn't charge them; solo walks and puppy visits are extra. It's a paid plan: save_plan, then Stripe. Pay as you go is the free plan; Bea invoices those walks herself.
- Never ask for health details about the client; keep dog notes to walking (pulling, recall, other dogs). Never collect card, bank or ID numbers.
- **Colours:** Sky and field: edit the --wk-* tokens at the top of styles.css (Sky, Field Green, Deep Field, Tennis Ball, Mud, Chalk, and the --wk-m-* park map colours), light and dark (a dusk park); the --k-* tokens below them follow. favicon.svg uses Field Green and Tennis Ball.
- **Fonts:** Google Fonts: Bagel Fat One (headlines, dogs' names and every number) and Nunito Sans (text), one in every page head and --wk-display / --wk-text in styles.css. If the owner prefers no font service, download both (OFL) into a fonts/ folder and switch to @font-face.
- **Sections:** setup_app with signup "invite" (Bea invites each client after the meet and greet) and the profile fields in memberApp.setup, save_plan for payg (free) and regular (paid), then save_app_list for dogs, bookings (status_options and reply on), cancellations (status_options) and reports (rows Bea assigns to the client). The owner's path: a booking arrives in the Dashboard (Apps, Entries); Bea sets Confirmed or Can't do that slot with a reply, and Walked after the walk; a cancellation arrives the same way and she marks it Cancelled and sets the booking to Cancelled; then she adds a reports row assigned to the client (route, minutes, km, how it went, album link). The client sees each change on Home and Walks, gets an email, and reads the report under Reports. app.js fills Book again links and the dog picker.
- **Images:** art/juno.webp, art/biscuit.webp, art/woodland-walk.webp and art/ellerby-green.webp are Unsplash photos (PHOTOS.md); dogs are round-cropped into collar tags by styles.css. Clients upload their own dog photos in the app; replace the walk photos with your own (no faces). art/park.svg holds the drawn park map parts (trees, pond, paths, gate, paw) that every map on the public page, Home and Reports uses; the route and paw stops are drawn in each page. art/stop-ball.svg, stop-paw.svg and chip-seam.svg are the tennis-ball and paw marks of the status stops, empty states and day pills. favicon.svg is the paw and ball mark; the PNG icons and manifest are made from it.
## Set up the app
This is an app template: the home page and privacy notice are public, and the pages under `/app` are for signed-in users, each seeing only their own entries and the entries the Site Owner assigns to them. Users sign in with a code sent to their email. The full guide is https://pagelemon.com/agents/member-app; read it before you set this up, and its legal notes at https://pagelemon.com/agents/member-app-legal.
- **Needs:** a kept site on App or above, and the Site Owner signed in to Page Lemon with two-step sign-in (they turn the app on themselves, at the approve link `setup_app` returns).
- **Never:** health, mood or therapy records, accounts for children, or fields for card, bank or ID numbers (Acceptable Use: https://pagelemon.com/acceptable-use#member-app). Users pay through Stripe.
- **Then:** `setup_app` with these settings, the join questions and note in the user's own words, then `save_app_list` once for each list below, exactly as written, so the field names match the pages.
```json
{"site":"","signup":"invite","profile_fields":[{"name":"name","type":"text","label":"Your name","required":true},{"name":"street","type":"text","label":"Street, for pick-ups"},{"name":"phone","type":"phone","label":"Phone on walk days"}],"display_field":"name","path":"/app"}
```
- **Dogs** (`dogs`): users add these rows themselves on the pages.
```json
{"site":"","list":"dogs","label":"Dogs","fields":[{"name":"name","type":"text","label":"Dog's name","required":true},{"name":"breed","type":"text","label":"Breed"},{"name":"age","type":"number","label":"Age in years"},{"name":"walk_style","type":"choice","label":"Walks best","required":true,"options":["In a small group","On their own"]},{"name":"keys","type":"choice","label":"How Bea gets in","required":true,"options":["Key safe","Spare key with Bea","Someone home"]},{"name":"vet_practice","type":"text","label":"Vet practice"},{"name":"likes","type":"long_text","label":"Anything Bea should know on walks"},{"name":"photo","type":"photo","label":"Photo of your dog"}]}
```
- **Walk bookings** (`bookings`): users add these rows themselves on the pages.
```json
{"site":"","list":"bookings","label":"Walk bookings","fields":[{"name":"dog","type":"text","label":"Which dog","required":true},{"name":"walk","type":"choice","label":"Walk","required":true,"options":["Group walk, 1 hour (£14)","Solo walk, 1 hour (£18)","Puppy visit, 30 min (£12)"]},{"name":"date","type":"date","label":"Date","required":true},{"name":"slot","type":"choice","label":"Pick-up window","required":true,"options":["Morning, 9 to 11","Midday, 11 to 1","Afternoon, 1 to 3"]},{"name":"notes","type":"long_text","label":"Anything for Bea"}],"status_options":["Requested","Confirmed","Walked","Can't do that slot","Cancelled"],"reply":true}
```
- **Walk cancellations** (`cancellations`): users add these rows themselves on the pages.
```json
{"site":"","list":"cancellations","label":"Walk cancellations","fields":[{"name":"walk","type":"text","label":"Which walk","required":true},{"name":"why","type":"text","label":"Anything Bea should know"}],"status_options":["Received","Cancelled"]}
```
- **Walk reports** (`reports`): the Site Owner adds these rows in the Page Lemon Dashboard (Apps tab) and assigns each to one user, who only reads it.
```json
{"site":"","list":"reports","label":"Walk reports","fields":[{"name":"date","type":"date","label":"Date","required":true},{"name":"dog","type":"text","label":"Dog","required":true},{"name":"walk","type":"choice","label":"Walk","required":true,"options":["Group walk","Solo walk","Puppy visit"]},{"name":"route","type":"text","label":"Route"},{"name":"minutes","type":"number","label":"Minutes"},{"name":"km","type":"number","label":"Distance in km"},{"name":"how_it_went","type":"long_text","label":"How it went"},{"name":"photos_link","type":"text","label":"Photo album link (https)"}]}
```
- **Plans** (`save_plan`; the pages use `data-pl-if="plan:"` and join buttons): `payg` "Pay as you go" (free); `regular` "Weekday regular" (paid, sample price 65.00 GBP a week; ask the user for theirs). Paid plans need Starter or Scale and the Site Owner's Stripe account connected; `save_plan` returns the onboarding link if it isn't.
## 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, walker's name and credentials, phone and email, postcode and areas covered, services and prices, walk time slots and opening hours, meet and greet booking). If they can't answer one, remove that element rather than inventing it.
- What is the business called, and who walks the dogs?
- Which areas and postcode do you cover, and what are your walk and sitting prices?
- Which time slots do you offer, and how many dogs can join a group walk?
- How do you hold keys for clients, and which vet practice details do you ask for?
- Which email address and phone number should clients use, and what do your insurance and checks cover?
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: "walkies"` (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.
7. **Turn on the app** as "Set up the app" above says: `setup_app`, then `save_app_list` for each list, `save_plan` for each plan, the approve link to the Site Owner, `invite_users`, a test with `preview_as_user` and `get_app` with `check: true` before you say it's ready.
## 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.