# Rota: a Page Lemon website template > A bright, friendly site for a staff-scheduling app: tomato, sky and mint shift pills on white, a live rota grid in the hero where a shift swap plays out, and a phone notification mock. You are reading this because the user wants their own website made from the Rota template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Rota": 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: "rota"` 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:** Bright shift pills on white with a live swapping rota (light, bold, modern) - **Pages:** Home (`index.html`): Live rota hero with an animated shift swap and phone notification, proof stats, how a swap works, rota builder, venue tabs, customer quote, pricing teaser, demo CTA; Features (`features.html`): Rota builder flags, swap cover rules with switches, holiday calendar, clock-in timesheet, wage-vs-takings chart, integrations; Pricing (`pricing.html`): Three illustrative plans per location with a locations calculator, one highlighted, comparison table and FAQ; Stories (`stories.html`): Three customer stories with figures and quotes, plus a before-and-after of one shift swap; Contact (`contact.html`): Demo booking slot with mailto and phone fallback, what happens on the call, support contacts - **Fonts:** Rubik, Patrick Hand (Google Fonts) - **Colours:** `--paper` #ffffff, `--ink` #1e2235, `--tomato` #f0533a, `--sky` #45a8f0, `--mint` #3fcf9b - **Live demo:** https://pagelemon.com/templates/rota/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Rota/preview) - **Manifest:** https://pagelemon.com/templates/rota/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made No raster art. The hero is an HTML table rota: Mo's Thursday shift is offered, Priya taps 'Take shift' on the phone mock (or the script taps after a pause) and the pill flies to her row. Without JS the request state shows; with reduced motion the swap happens instantly on tap. Pills have slightly uneven corners and tilts for a hand-made feel. To sketch similar art: "Flat friendly SVG illustration on a pale sky, mint or tomato wash: rounded shapes, thick navy-ink outlines on key objects, tomato red, sky blue and mint accents, simple faces with dot eyes." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "rota"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/rota/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/rota/index.html - https://pagelemon.com/templates/rota/features.html - https://pagelemon.com/templates/rota/pricing.html - https://pagelemon.com/templates/rota/stories.html - https://pagelemon.com/templates/rota/contact.html - https://pagelemon.com/templates/rota/404.html - https://pagelemon.com/templates/rota/privacy.html - https://pagelemon.com/templates/rota/styles.css - https://pagelemon.com/templates/rota/script.js - https://pagelemon.com/templates/rota/favicon.svg - https://pagelemon.com/templates/rota/og.png - https://pagelemon.com/templates/rota/apple-touch-icon.png - https://pagelemon.com/templates/rota/art/scribble.svg - https://pagelemon.com/templates/rota/art/tick.svg - https://pagelemon.com/templates/rota/art/scene-cafe.svg - https://pagelemon.com/templates/rota/art/scene-kitchen.svg - https://pagelemon.com/templates/rota/art/scene-shop.svg - https://pagelemon.com/templates/rota/art/app-week.svg - https://pagelemon.com/templates/rota/art/avatar-dani.svg - https://pagelemon.com/templates/rota/art/avatar-wen.svg - https://pagelemon.com/templates/rota/art/avatar-ruth.svg ## Notes for Rota (its `customise` rules) - Product name 'Pinny' and company 'Pinny Rotas Ltd' in , header, footer and JSON-LD - The sample rota (people, shifts, the Thursday swap) in .stage on index.html, and the status messages in script.js - Stats in .proof on index.html and stories.html - Plans, prices and data-per values on pricing.html (the calculator reads data-per, data-min, data-max) - Customer names, quotes and figures on stories.html and the quote on index.html - **Colours:** Edit the :root tokens at the top of styles.css: tomato (Kitchen), sky (Floor), mint (Till and done states). Keep the -d shades for text on white. - **Fonts:** Rubik (everything) and Patrick Hand (handwritten notes only). Change the Google Fonts <link> in each page and --font / --hand in styles.css. - **Sections:** Every section is self-contained with its own heading; delete or reorder freely. Shift pills (.pill--floor, --kitchen, --till) are the shared device: reuse them for roles, prices or tags. - **Images:** Replace art/scene-cafe.svg, scene-kitchen.svg and scene-shop.svg (venues, 1600×1000), art/app-week.svg (product screenshot, 1600×1000) and art/avatar-*.svg (customer portraits, 800×800 square) with real images; WebP under 300 KB. The hero rota and phone are HTML, not images. ## 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 (product name, company name and address, phone, email, support hours, prices per location, customer names, quotes and figures). If they can't answer one, remove that element rather than inventing it. - What is the product called and what does it do in one sentence? - Which kinds of business is it for: cafés, restaurants, shops or others? - How is it priced: per location, per user or flat, and what are the plans? - Which features matter most: rotas, swaps, holidays, timesheets or wage costs? - Which customers can be named and quoted, with what figures? - What phone, email and support hours should people use? 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: "rota"` (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 `<title>`, 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.