# Rally: a Page Lemon website template > A poster-style campaign site: solid orange and ultramarine fields, a giant stencil headline, megaphone shapes and a petition that counts. You are reading this because the user wants their own website made from the Rally template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Rally": 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: "rally"` 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:** Poster campaign: solid orange and ultramarine fields, stencil type, megaphone art (light, bold, modern) - **Pages:** Home (`index.html`): Giant stencil headline, slogan ticker, three issues, petition count, next events, update signup; Issues (`issues.html`): Three issue pages: problem, what we want, what the council says, how to help; Act (`act.html`): Petition and volunteer forms (slots), plus three quick actions; Events (`events.html`): Dated event list with RSVP by email; Press (`press.html`): Press kit: fact sheet, spokespeople, coverage quote, media contact; About (`about.html`): Campaign story, team and quarterly donation transparency - **Fonts:** Big Shoulders Stencil Display, Archivo (Google Fonts) - **Colours:** `--paper` #FFFFFF, `--ink` #0D0D10, `--orange` #FF5A1F, `--ultra` #1C2AB8, `--grey` #E9EAF2 - **Live demo:** https://pagelemon.com/templates/rally/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Rally/preview) - **Manifest:** https://pagelemon.com/templates/rally/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Solid colour fields, a giant stencil headline set in CSS, a looping slogan ticker that stops under reduced motion, megaphone SVG art drawn in one ink colour, and issue rows that flip to orange on hover. The petition count is a native progress element. To sketch similar art: "Draw a bold flat SVG megaphone in solid black with three curved sound lines, on a plain background, with simple geometric shapes and no gradients." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "rally"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/rally/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/rally/index.html - https://pagelemon.com/templates/rally/issues.html - https://pagelemon.com/templates/rally/act.html - https://pagelemon.com/templates/rally/events.html - https://pagelemon.com/templates/rally/press.html - https://pagelemon.com/templates/rally/about.html - https://pagelemon.com/templates/rally/404.html - https://pagelemon.com/templates/rally/privacy.html - https://pagelemon.com/templates/rally/styles.css - https://pagelemon.com/templates/rally/script.js - https://pagelemon.com/templates/rally/favicon.svg - https://pagelemon.com/templates/rally/og.png - https://pagelemon.com/templates/rally/apple-touch-icon.png - https://pagelemon.com/templates/rally/art/megaphone.svg - https://pagelemon.com/templates/rally/art/bus.svg - https://pagelemon.com/templates/rally/art/crossing.svg - https://pagelemon.com/templates/rally/art/ticket.svg ## Notes for Rally (its `customise` rules) - Replace Move Brackenholt, Brackenholt, Beacon Lane and the Route 14 wording in the title, meta, JSON-LD, header, footer and every page - Replace every data-pl-fill fact: petition count, goal, dates, team names, donation totals and social links. Remove the sample press quote and the donor quote unless you have the real ones - Set the invented Unit 4 address, 01632 960 813 phone and example.com emails to the campaign's own details, identically in the footer, JSON-LD and press page - Make the issue text specific: the three issue pages are sample cases, not facts - **Colours:** Edit the commented :root tokens at the top of styles.css. Orange fields take ink text; ultramarine fields take white text. Keep both pairs above 4.5:1 - **Fonts:** Change the Google Fonts link in every HTML head and --font-display/--font-body. Stencil headlines use Big Shoulders Stencil Display 900 and Archivo 400/700/800 - **Sections:** Each section is self-contained and uses a field class (field-orange, field-ultra, field-ink) or the plain paper ground. Reorder or delete sections freely; keep one h1 per page - **Images:** Replace art/*.svg frames with campaign photos: issue frames 1200×900 landscape 4:3 (art/bus.svg, art/crossing.svg, art/ticket.svg); the hero megaphone is 420×300. WebP under 300 KB each - **Slots:** Petition, volunteer and update forms are inert until a forms plugin is connected; the mailto links work today. Add the forms privacy paragraph and retention details in privacy.html when enabling forms ## Offer these Page Lemon features - **Co-edit:** Campaign volunteers update issues, events and press together ## 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 (campaign and organisation name, address, phone and email, office hours, petition count and goal, and the closing date, event dates, times and venues, spokesperson and team names, press quotes (real coverage only), donation totals and donor counts, social links). If they can't answer one, remove that element rather than inventing it. - What is the campaign called and what does it want changed? - Where is it, and who is it for? - What is the petition goal and when does it close? - What events are coming up, with dates and places? - Who speaks for the campaign and how can press reach them? - Which email and phone 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: "rally"` (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.