# Primer: a Page Lemon website template > A maths and physics tutor's site like a geometry set: squared paper, ink navy, marigold set squares and compass arcs, a worked example you step through, a subjects-by-level filter, clear prices and lesson booking. You are reading this because the user wants their own website made from the Primer template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Primer": 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: "primer"` 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:** Geometry set: squared paper, ink navy, marigold set squares and tomato compass arcs (light, bold, modern) - **Pages:** Home (`index.html`): Subjects by level, a step-through worked example, how a first lesson starts, reviews, quick answers and the book CTA; Subjects (`subjects.html`): Subjects and levels with a filter that works without JavaScript, and what a lesson covers; About (`about.html`): The tutor, qualifications, DBS and safeguarding, the study room and online lessons; Prices & FAQ (`prices.html`): Prices for one-to-one, A level, groups and the free chat, blocks, cancellation rules and the full FAQ; Contact (`contact.html`): Enquiry form slot, address with map link, lesson times, phone and email; Book a lesson (`book.html`): Booking slot (free chat, lessons, group taster) with the picker design, and what happens after booking - **Fonts:** Epilogue, Kalam (Google Fonts) - **Colours:** `--ink` #16224a, `--paper` #f4f7fa, `--sun` #f5b82e, `--tomato` #d9442b, `--mint` #9fdcc8, `--sky` #cfe0f2 - **Live demo:** https://pagelemon.com/templates/primer/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Primer; the page about it is https://pagelemon.com/tp/Primer/use) - **Manifest:** https://pagelemon.com/templates/primer/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Flat geometric SVGs in art/: squared-paper grounds, ink navy outlines, marigold protractors and set squares, tomato compass arcs, mint and sky fills, worked sums in a handwriting face. CSS adds squared-paper panels, protractor angle badges as section labels, set-square corners on cards and offset marigold shadows. To sketch similar art: "Draw a flat geometric SVG of a desk from above on squared paper: an ink-navy compass, a marigold protractor, a mint set square, a pencil and a worked equation in handwriting, with a tomato-red compass arc." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "primer"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/primer/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/primer/index.html - https://pagelemon.com/templates/primer/subjects.html - https://pagelemon.com/templates/primer/about.html - https://pagelemon.com/templates/primer/prices.html - https://pagelemon.com/templates/primer/contact.html - https://pagelemon.com/templates/primer/book.html - https://pagelemon.com/templates/primer/privacy.html - https://pagelemon.com/templates/primer/404.html - https://pagelemon.com/templates/primer/styles.css - https://pagelemon.com/templates/primer/script.js - https://pagelemon.com/templates/primer/favicon.svg - https://pagelemon.com/templates/primer/og.png - https://pagelemon.com/templates/primer/apple-touch-icon.png - https://pagelemon.com/templates/primer/art/hero-desk.svg - https://pagelemon.com/templates/primer/art/portrait.svg - https://pagelemon.com/templates/primer/art/study-room.svg - https://pagelemon.com/templates/primer/art/online.svg - https://pagelemon.com/templates/primer/art/tile-maths.svg - https://pagelemon.com/templates/primer/art/tile-physics.svg - https://pagelemon.com/templates/primer/art/tile-reasoning.svg ## Notes for Primer (its `customise` rules) - Replace every data-pl-fill fact on every page, including metadata and JSON-LD. Keep Ines Tremlett Tutoring, 1st floor, 14 Station Parade, Pellingham QN4 7PE and 01632 960 827 identical in the footer, contact.html and the JSON-LD. - Rewrite the subjects board (subjects.html) to the subjects and levels taught; each card's class (ks3, gcse, alevel, eleven) must match a filter input, or remove that filter and its label. - Change the worked example on index.html to a problem from the tutor's own subject. - Delete the sample reviews (data-pl-fill="review") unless the tutor gives real ones; never invent qualifications or results. - **Colours:** Edit the :root tokens at the top of styles.css. --tomato-text is the darker tomato used for text; keep it at 4.5:1 on --paper. Also replace matching palette hex values in art/*.svg, favicon.svg and inline wordmark SVGs, and update every theme-color meta. Keep --tomato-text at 4.5:1 on each background where it appears. - **Fonts:** Change the Google Fonts link on every page and --font-display / --font-hand. Current files: Epilogue 400/700/800 and Kalam 700 (handwriting for worked steps). - **Sections:** Keep the header, footer and mobile Call / Book / Directions bar on every page. The subjects filter is radio inputs and CSS; JavaScript only announces the count. Booking slot (book.html, id lessons): ask the person for their services, hours and rules, 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), render any booking questions (such as the pupil's year group) as the q_ fields slots_url returns and keep its link to booking_url for visitors without JavaScript. Set the booking's confirmation_message to the lesson address or the video link, so the confirmation email carries what book.html's 'What happens next' promises (without it the email has only the time), or change that line. Test with one test booking before calling it live. Form slot (contact.html, id enquiry): ask what the form should ask, send the form as form_html to add_plugin (kind forms), show the person the whole setup_summary and save only after their yes (confirm_token), put the snippet_html form in the slot in the template's classes, then send one test message (test_plugin) and tell them the result before calling it live. When either slot goes live, copy the privacy paragraph from privacy.html's template into the page. Replace privacy.html's first paragraph with 'This website sets no cookies. There are no analytics or advertising scripts.' Remove 'and no personal data collected' from both descriptions, insert the privacy template paragraph, then delete its template. - **Images:** Replace art/hero-desk.svg (1200×1000, the tutor at work or their desk), art/portrait.svg (800×1000 portrait of the tutor), art/study-room.svg and art/online.svg (1600×1000, the teaching room and an online lesson), art/tile-maths.svg, art/tile-physics.svg and art/tile-reasoning.svg (800×600 lesson materials). Keep the frame ratios 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 (tutor's name and business name, subjects and levels taught, prices for each lesson type and any blocks, lesson times, study room address, or online only, phone, email, qualifications and DBS, cancellation rules, reviews from families (only real ones), social link). If they can't answer one, remove that element rather than inventing it. - What is your name, and what should the business be called? - Which subjects and levels do you teach? - What do you charge for each kind of lesson, and do you offer a free first chat? - When do you teach, and where: a room, pupils' homes or online? - What qualifications and checks (such as DBS) should parents see? - What is your cancellation rule? - Do you want people to book lessons online, send you a message, or both? 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: "primer"` (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.