# Chair: a Page Lemon website template > A quiet, precise barber studio in cool greys and white, with architectural artwork, cobalt details and a service list that gives time a visible shape. You are reading this because the user wants their own website made from the Chair template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Chair": 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: "chair"` 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:** Minimal grooming, cool greys (light, calm, modern) - **Pages:** Home (`index.html`): Studio atmosphere, service duration disclosures, walk-in note, team and visit preview; Services (`services.html`): Six HTML service prices and duration bars, detailed inclusions, restyle feature and practical FAQs; The team (`team.html`): Two staggered barber portraits, individual specialities and shared consultation approach; Visit (`visit.html`): Shop frontage, full weekly hours, map-search address, transport, parking and access; Book a chair (`book.html`): Booking plugin slot with phone fallback, inert request form, walk-in policy and appointment changes - **Fonts:** Onest, Azeret Mono (Google Fonts) - **Colours:** `--bg` #ffffff, `--ink` #22292f, `--accent` #244bc9, `--surface` #eef1f3, `--muted` #58636d - **Live demo:** https://pagelemon.com/templates/chair/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Chair/preview) - **Manifest:** https://pagelemon.com/templates/chair/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Storefront, studio, haircut profile and stylist portraits are SVG files in art/ using pale blue-grey linear gradients, many flat paths and a thin tile-joint pattern, with a cobalt accent. CSS has no decorative effects; images are placeholders for photos. To sketch similar art: "Draw a calm flat SVG barbershop storefront in pale blue-greys with soft vertical gradients, tiled wall joints and one cobalt-blue sign accent." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "chair"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/chair/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/chair/index.html - https://pagelemon.com/templates/chair/services.html - https://pagelemon.com/templates/chair/team.html - https://pagelemon.com/templates/chair/visit.html - https://pagelemon.com/templates/chair/book.html - https://pagelemon.com/templates/chair/404.html - https://pagelemon.com/templates/chair/privacy.html - https://pagelemon.com/templates/chair/styles.css - https://pagelemon.com/templates/chair/script.js - https://pagelemon.com/templates/chair/favicon.svg - https://pagelemon.com/templates/chair/og.png - https://pagelemon.com/templates/chair/apple-touch-icon.png - https://pagelemon.com/templates/chair/art/studio.svg - https://pagelemon.com/templates/chair/art/cut-profile.svg - https://pagelemon.com/templates/chair/art/ellis-ward.svg - https://pagelemon.com/templates/chair/art/robin-keene.svg - https://pagelemon.com/templates/chair/art/storefront.svg ## Notes for Chair (its `customise` rules) - Replace every data-pl-fill fact, including metadata, biographies, prices, durations, policies and JSON-LD. Use one identical business name, full address and display phone throughout. - The example business is Chair at 24 Slate Row, Oakenholt, QC2 6SL; phone 01632 960 412; email hello@chair.example.com. - Verify hair types served, quiet appointments, doorway width, step-free access, parking, bus stops, opening hours and cancellation policy before publishing. - Update the schema.org HairSalon structured data (schema.org has no BarberShop type); replace fictional geo coordinates. - **Colours:** Edit the commented :root tokens at the top of styles.css. Keep one accent with enough contrast against white and cool grey panels. - **Fonts:** Onest 400/500 and Azeret Mono 400, three font files in total. Change the Google Fonts link in all seven page heads and the two :root font tokens together; at most two families and four files. - **Sections:** All pages share header, footer and mobile Call / Book / Directions bar. Services use native details disclosures with proportional duration bars; work without JS. The walk-in note is a policy, not a live availability claim. Keep the booking slot and matching inert template; a real booking plugin replaces the fallback. Booking requests need studio confirmation. Add the inert privacy forms paragraph only when enabling the plugin, completing retention and processor details. - **Images:** Replace art/studio.svg with a bright interior, 1600×1200, accepting a portrait desktop crop; cut-profile.svg with a finished haircut, 1000×1200; ellis-ward.svg and robin-keene.svg with barber portraits, 800×1000; storefront.svg with the entrance, 1600×1000. Keep img dimensions, data-pl-photo, object-fit and frame aspect ratios. Prefer WebP under 300 KB. The pipeline generates og.png and apple-touch-icon.png; these are referenced and listed but deliberately not created here. ## 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, service names, durations and prices, barber names, roles and specialities, walk-in and cancellation policy, quiet appointments, hair types served, access, transport and parking, geographic coordinates, privacy practices). If they can't answer one, remove that element rather than inventing it. - What is the studio called? - What is the full studio address? - What phone number should clients use to book? - What are your weekly opening hours? - Which services do you offer? - Who are your barbers? - What is your walk-in policy? 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: "chair"` (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.