# Buff: a Page Lemon website template > A glossy nail studio site in milky pink, lacquer red and chrome silver, with a price list by treatment, technician profiles, a nail design gallery and a phone and email booking page that carries the chosen treatment, ready for an online booking picker. You are reading this because the user wants their own website made from the Buff template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Buff": 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: "buff"` 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:** Gloss and chrome (light, bold, modern) - **Pages:** Home (`index.html`): Glossy hero, shade strip, price preview, how booking works, technicians, design ideas, before your appointment (patch test, removals, cancellation); Services (`services.html`): Fourteen treatments with time and price, filter by group, lash patch-test and longer-treatment notes; Gallery (`gallery.html`): Eight nail design ideas (chrome, lacquer, marble, ombre, half-moon) with a filter by group; The team (`team.html`): Three technicians with specialities and bios, owner note; Visit (`visit.html`): Shopfront, hours, address with map link, parking, access, aftercare and the 24-hour cancellation policy; Book (`book.html`): Booking slot with a phone and pre-filled email request that carries the treatment chosen on Services, patch-test call, inert picker for treatment, technician, day and time - **Fonts:** Cormorant Garamond, Manrope (Google Fonts) - **Colours:** `--milk` #f8eef0, `--blush` #f0d3dc, `--rose` #e4a2b4, `--lacquer` #8e1b2e, `--lacquer-deep` #5c0f1d, `--ink` #2b1417, `--muted` #6e5258 - **Live demo:** https://pagelemon.com/templates/buff/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Buff; the page about it is https://pagelemon.com/tp/Buff/use) - **Manifest:** https://pagelemon.com/templates/buff/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Vector illustration only: milky pink and lacquer red gradients, chrome silver drawn as SVG gradients, nail-shape almonds with gloss highlights, and the chrome plinth. No raster images and no stock photos. To sketch similar art: "A glossy manicure set on a chrome plinth, milky pink and deep lacquer red, soft studio light, shallow depth of field, clean background." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "buff"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/buff/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/buff/index.html - https://pagelemon.com/templates/buff/services.html - https://pagelemon.com/templates/buff/team.html - https://pagelemon.com/templates/buff/gallery.html - https://pagelemon.com/templates/buff/book.html - https://pagelemon.com/templates/buff/visit.html - https://pagelemon.com/templates/buff/404.html - https://pagelemon.com/templates/buff/privacy.html - https://pagelemon.com/templates/buff/styles.css - https://pagelemon.com/templates/buff/script.js - https://pagelemon.com/templates/buff/favicon.svg - https://pagelemon.com/templates/buff/og.png - https://pagelemon.com/templates/buff/apple-touch-icon.png - https://pagelemon.com/templates/buff/art/hero-set.svg - https://pagelemon.com/templates/buff/art/shopfront.svg - https://pagelemon.com/templates/buff/art/team-mai.svg - https://pagelemon.com/templates/buff/art/team-delphine.svg - https://pagelemon.com/templates/buff/art/team-rosa.svg - https://pagelemon.com/templates/buff/art/gallery-1.svg - https://pagelemon.com/templates/buff/art/gallery-2.svg - https://pagelemon.com/templates/buff/art/gallery-3.svg - https://pagelemon.com/templates/buff/art/gallery-4.svg - https://pagelemon.com/templates/buff/art/gallery-5.svg - https://pagelemon.com/templates/buff/art/gallery-6.svg - https://pagelemon.com/templates/buff/art/gallery-7.svg - https://pagelemon.com/templates/buff/art/gallery-8.svg ## Notes for Buff (its `customise` rules) - Replace every data-pl-fill fact: name, address, phone, email, hours, prices, durations, technician names and bios, reviews and policy wording. Use one identical business name, address and phone throughout, including the JSON-LD. - The example business is Halo Nail Studio at 9 Quill Street, Larkhollow QT4 7LP; phone 01632 960 830; email hello@halonails.example.com; owner Jun Achterberg; technicians Mai Thornbury (nail art), Delphine Oyelaran (gel and BIAB) and Rosa Kettering (lashes and brows); open Tuesday to Saturday, late on Thursday. - Verify the cancellation policy (24 hours), the late-cancellation charge, the lash patch-test rule (48 hours), parking, bus and station times, step-free access and aftercare advice before publishing. - The price list is a List (services) and the team is a List (team): edit the items, not the markup. Update the JSON-LD NailSalon block (openingHoursSpecification, priceRange, geo) to the real business. - There are no reviews in the template. Add a reviews section only with reviews the owner supplies. The gallery is drawn design ideas, not the studio's work: replace it with photos of real sets before describing it as recent work. - **Colours:** Edit the commented :root tokens at the top of styles.css. Keep milky pink for the page, lacquer red for the one primary action and chrome only as accents. Change the palette object here to match. - **Fonts:** Cormorant Garamond 600 for headings and Manrope 400 and 700 for text, three font files in total. Change the Google Fonts link in every page head and the two :root font tokens together; at most two families and four files. - **Sections:** All pages share the header, the footer and the mobile Call / Book / Directions bar. Nail-shape swatches are the recurring device. The price list and team are Lists. The gallery and services filters are small script.js enhancements; without JS every item shows. The booking slot shows the inert picker in this design: ask for the treatments, technicians, days and hours, add the booking, confirm the summary with the owner, then build the picker from the template (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. - **Images:** The art is self-hosted SVG drawn in this direction. Replace art/hero-set.svg with a finished nail set on a hand or plinth, 1600×1000; art/gallery-1..8.svg with real nail-set photos, 1200×1500 (4:5); art/team-*.svg with each technician's work-station or hands, 800×1000; art/shopfront.svg with the entrance, 1600×1000. Keep img width, height, alt and data-pl-photo, and the 4:5 and 16:10 aspect ratios. Prefer WebP under 300 KB for photos. 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 including the late Thursday, treatment names, groups, durations and prices, technician names, roles and specialities, cancellation policy (24 hours) and lash patch-test rule, parking, transport and access, aftercare advice for gel, BIAB and lashes, privacy practices). If they can't answer one, remove that element rather than inventing it. - What is the salon called and what is its full address? - What phone number and email should clients use? - What are your opening hours, including any late night? - Which treatments do you offer, and what do they cost? - Who are your technicians and what does each one specialise in? - What is your cancellation and patch-test policy? 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: "buff"` (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.