# Taper: a Page Lemon website template > A candlelit evening wedding in midnight plum and burnished gold, with candle-glow gradients, a lit-candle order of the evening, an arched venue frame, music requests and an RSVP form. You are reading this because the user wants their own website made from the Taper template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Taper": 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: "taper"` 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:** Midnight plum, candle-glow light, high-contrast serif (dark, bold, classic) - **Pages:** Our story (`index.html`): Names, date, story in three beats, the evening at a glance, venue teaser, RSVP close; The evening (`day.html`): Timeline of the order of the evening that lights up on scroll, dinner note; Venue (`venue.html`): Venue address, map search, getting there, parking, access, rooms for the night; Music (`music.html`): Playlist direction and the music request form (inert slot); RSVP (`rsvp.html`): RSVP form with meal, guests and dietary needs (inert slot) and phone or email fallback - **Fonts:** Bodoni Moda, DM Sans (Google Fonts) - **Colours:** `--night` #1D0E1E, `--plum` #2E1430, `--gold` #C9A455, `--ivory` #F7EEDC, `--lilac-paper` #F4EEF3 - **Live demo:** https://pagelemon.com/templates/taper/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Taper/preview) - **Manifest:** https://pagelemon.com/templates/taper/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Four SVG files in art/: hero-tapers (five lit tapers over a plum table), venue-arch (arched window over brick), dinner-table (a long table with three candles), music-record (a gold-labelled record). Glows are radial gradients in the SVG and the CSS background. To sketch similar art: "A dark, candlelit wedding illustration: a row of five lit tapers over a deep plum table, gold hairline frame, warm radial glow, flat shapes with no outlines beyond the frame." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "taper"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/taper/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/taper/index.html - https://pagelemon.com/templates/taper/day.html - https://pagelemon.com/templates/taper/venue.html - https://pagelemon.com/templates/taper/music.html - https://pagelemon.com/templates/taper/rsvp.html - https://pagelemon.com/templates/taper/404.html - https://pagelemon.com/templates/taper/privacy.html - https://pagelemon.com/templates/taper/styles.css - https://pagelemon.com/templates/taper/script.js - https://pagelemon.com/templates/taper/favicon.svg - https://pagelemon.com/templates/taper/og.png - https://pagelemon.com/templates/taper/apple-touch-icon.png - https://pagelemon.com/templates/taper/art/hero-tapers.svg - https://pagelemon.com/templates/taper/art/venue-arch.svg - https://pagelemon.com/templates/taper/art/dinner-table.svg - https://pagelemon.com/templates/taper/art/music-record.svg ## Notes for Taper (its `customise` rules) - Couple names 'Ines Adair' and 'Tomas Vell' in , meta description, hero h1, footer and JSON-LD name - Date 'Saturday 18 September 2027' and the start time in the hero, day page, JSON-LD startDate and footer - Venue 'The Dipping House, Garrick Yard, Burnside Moor QM4 2TL' in the hero, venue teaser, venue page, footer and JSON-LD location - Timeline times and steps in day.html (the seven items) - Phone 01632 960 820 and hello@example.com in the footer, venue, RSVP and music pages - Room block line and parking note in venue.html; RSVP deadline in the header button and CTAs - **Colours:** Edit the :root tokens at the top of styles.css. Keep --gold on --night for buttons and text; keep text on --lilac-paper in --ink - **Fonts:** Change the Google Fonts <link> in each page and --font-display / --font-body in styles.css - **Sections:** Each <section> has an id or aria-labelledby and is self-contained. The timeline is an ordered list in day.html. The RSVP and music forms live in <template data-pl-slot-form> - **Images:** Replace the four art/*.svg frames: hero 4:5 on desktop and 16:10 on phones (1600×1000), venue 16:10 (1600×1000), dinner 16:10 (1600×1000), music square (1200×1200). WebP under 300 KB each ## Offer these Page Lemon features - **Protect (password):** Not built in: fits a private details page for guests behind a password or invite link - **Co-edit:** The couple edits the site 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 (couple names, wedding date and start time, venue name and address, order of the evening times, phone and email, RSVP deadline, meal options and dietary wording, room block for guests who stay over, music request deadline). If they can't answer one, remove that element rather than inventing it. - What are your names as you want them printed on the invitation? - What date is the wedding, and what time do guests arrive? - Which venue is it, and what is its full address? - What is your RSVP deadline, and which phone number and email should guests use? - What are the main course choices and how many courses are served? - Which songs must be played, and which must never be played? 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: "taper"` (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.