# Tandem: a Page Lemon website template > A two-person design studio with split-screen identities: coral for one partner, pistachio for the other, meeting in the middle, plus a work index filterable by partner and discipline. You are reading this because the user wants their own website made from the Tandem template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Tandem": 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: "tandem"` 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:** Two-person studio, split-screen identities (light, bold, modern) - **Pages:** Home (`index.html`): Split coral/pistachio hero naming both partners, selected work, fixed-fee services, process, client quote, CTA; Work (`work.html`): Work index filterable by partner and discipline without JS; Off Beat (`case-festival.html`): Joint identity and website case study with notes from both partners; Good Kin (`case-packaging.html`): Packaging case study led by one partner; Studio (`studio.html`): Side-by-side partner profiles, principles and FAQ; Start a project (`contact.html`): Brief checklist, enquiry slot with mailto and tel fallback, studio address and hours - **Fonts:** Urbanist, Zilla Slab (Google Fonts) - **Colours:** `--bg` #f4f2e9, `--ink` #242c25, `--coral` #ee9a83, `--lime` #cfdc92 - **Live demo:** https://pagelemon.com/templates/tandem/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Tandem/preview) - **Manifest:** https://pagelemon.com/templates/tandem/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made SVG files in art/ in a flat graphic style, split coral and pistachio on dark green-black. The project mockups (festival tickets, tea packaging, bakehouse bag, lido site, voice book) are rects, paths and SVG text, and the partner portraits are flat-shape figures. All are placeholders for real project photos. To sketch similar art: "Draw a flat SVG brand-identity mockup split into a coral half and a pistachio half, showing a tilted cream poster with bold sans type and simple geometric shapes." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "tandem"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/tandem/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/tandem/index.html - https://pagelemon.com/templates/tandem/work.html - https://pagelemon.com/templates/tandem/case-festival.html - https://pagelemon.com/templates/tandem/case-packaging.html - https://pagelemon.com/templates/tandem/studio.html - https://pagelemon.com/templates/tandem/contact.html - https://pagelemon.com/templates/tandem/404.html - https://pagelemon.com/templates/tandem/privacy.html - https://pagelemon.com/templates/tandem/styles.css - https://pagelemon.com/templates/tandem/script.js - https://pagelemon.com/templates/tandem/favicon.svg - https://pagelemon.com/templates/tandem/og.png - https://pagelemon.com/templates/tandem/apple-touch-icon.png - https://pagelemon.com/templates/tandem/art/bakehouse.svg - https://pagelemon.com/templates/tandem/art/festival-detail.svg - https://pagelemon.com/templates/tandem/art/festival.svg - https://pagelemon.com/templates/tandem/art/kit.svg - https://pagelemon.com/templates/tandem/art/lido.svg - https://pagelemon.com/templates/tandem/art/mara.svg - https://pagelemon.com/templates/tandem/art/packaging-detail.svg - https://pagelemon.com/templates/tandem/art/packaging.svg - https://pagelemon.com/templates/tandem/art/voice-book.svg ## Notes for Tandem (its `customise` rules) - Tandem in titles, header, footer and JSON-LD; replace every data-pl-fill fact - Keep name, address and phone identical in the footer, contact page and JSON-LD - Partner names, roles and voices (Mara Renshaw, Kit Rowan) in index, studio and case pages - Projects in work.html: set data-partners (space-separated partner ids) and data-discipline on each .work-card - Service prices in index.html, case study facts and client quotes (remove sample reviews unless real) - **Colours:** Edit the :root tokens in styles.css; --coral is partner one, --lime is partner two - **Fonts:** Change the Google Fonts link in every page and --font-body / --font-voice; keep at most four font files - **Sections:** Every page shares the header, footer and closing CTA. The work filter is pure CSS (:has on radio inputs); if you rename partners or disciplines, update the matching selectors in styles.css. The enquiry form stays inert inside its slot template until a forms plugin is connected. - **Images:** Replace art/*.svg frames: project covers and case details landscape 1600×1000 (festival, packaging, lido, voice-book, bakehouse, festival-detail, packaging-detail); partner portraits mara and kit 800×1000. WebP under 300 KB, keep width, height and data-pl-photo. Pipeline supplies 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 (name, address, phone, email, hours, partner names and roles, services and prices, projects and case studies, client quotes). If they can't answer one, remove that element rather than inventing it. - What is the studio called and where is it based? - Who are the two partners, and what does each one lead? - Which phone number and email should clients use? - Which services do you offer, and what do they cost from? - Which projects should appear in the work index, and who made each? - Which two projects deserve full case studies? 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: "tandem"` (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.