# Aisle: a Page Lemon website template > A playful wedding site on a white ground, with tangerine, bubblegum and cobalt colour blocks, a fat display serif, confetti shapes and a tap-for-confetti moment on the home page. You are reading this because the user wants their own website made from the Aisle template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Aisle": 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: "aisle"` 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:** Bold, joyful colour blocks with a fat serif display and confetti (light, bold, modern) - **Pages:** Our story (`index.html`): Save the date hero with a tap-for-confetti moment, the couple's story, the day at a glance and the reply call to action; The day (`details.html`): Full schedule, venue and access, travel by train and car, nearby rooms and the dress code (the Protect-ready details page); Registry (`registry.html`): Two gift lists and a honeymoon fund with fixed amounts and a custom-amount link; Questions (`faq.html`): Six answered questions (plus-ones, children, access, rain, changing an RSVP, dietary needs) in open accordions; RSVP (`rsvp.html`): Reply page with the RSVP form slot, a mailto and phone fallback, and a reply-by date - **Fonts:** Abril Fatface, Nunito Sans (Google Fonts) - **Colours:** `--paper` #FFFFFF, `--ink` #1B1340, `--tangerine` #FF6B2C, `--pink` #FF9ACB, `--cobalt` #1D3FD1, `--sun` #FFD23F - **Live demo:** https://pagelemon.com/templates/aisle/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Aisle/preview) - **Manifest:** https://pagelemon.com/templates/aisle/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Flat SVG illustrations in four colours on white: a tangerine sky with a bubblegum arch and two silhouetted people (hero), a bench scene under a sun stripe (story), the barn with bunting (venue), and a confetti tile of small shapes used as a background on the hero. To sketch similar art: "Draw flat SVG illustrations in tangerine, bubblegum pink, cobalt and sunshine yellow with ink outlines: two silhouetted people under an arch, a barn with triangle bunting, and a repeating confetti tile of circles, rectangles, squiggles and triangles." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "aisle"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/aisle/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/aisle/index.html - https://pagelemon.com/templates/aisle/details.html - https://pagelemon.com/templates/aisle/registry.html - https://pagelemon.com/templates/aisle/faq.html - https://pagelemon.com/templates/aisle/rsvp.html - https://pagelemon.com/templates/aisle/404.html - https://pagelemon.com/templates/aisle/privacy.html - https://pagelemon.com/templates/aisle/styles.css - https://pagelemon.com/templates/aisle/script.js - https://pagelemon.com/templates/aisle/favicon.svg - https://pagelemon.com/templates/aisle/og.png - https://pagelemon.com/templates/aisle/apple-touch-icon.png - https://pagelemon.com/templates/aisle/art/hero.svg - https://pagelemon.com/templates/aisle/art/story.svg - https://pagelemon.com/templates/aisle/art/venue.svg - https://pagelemon.com/templates/aisle/art/confetti.svg ## Notes for Aisle (its `customise` rules) - Couple names 'Noor & Ansel' (and 'Noor Haddad', 'Ansel Marlowe') in every , meta description, header wordmark, hero, story signature, JSON-LD and footer - Date '19 June 2027' and venue 'The Dairy Barn, Dairy Lane, Corbel Green, QG4 7QX' in the hero chip, the home schedule, #venue, the Event JSON-LD and every footer; the same characters everywhere - Schedule times and titles in index.html #day and details.html #schedule; the RSVP reply-by date '1 May 2027' appears in the eyebrows, buttons and footers - Travel, hotels and dress code copy in details.html; the three colour names in the swatches - Gift list names, honeymoon fund amounts and links in registry.html; every example.com URL is a placeholder to replace - Email hello@example.com and phone 01632 960 800 are placeholders; replace them in every footer, rsvp.html fallback and faq.html - **Colours:** Edit the :root tokens at the top of styles.css. Keep text on the pink and tangerine blocks in ink, and white on cobalt. Re-check contrast after changing a block colour. - **Fonts:** Abril Fatface (one weight) and Nunito Sans 400/700. Change the Google Fonts link in every page head and the --font-display and --font-body tokens. - **Sections:** Each page is built from colour blocks (.block-white, .block-pink, .block-tangerine, .block-cobalt). Reorder or remove blocks freely; keep the reply call to action at the end of each page. The RSVP form lives in the template inside rsvp.html; the demo shows the mailto and phone fallback. - **Images:** Replace art/hero.svg (landscape 1600x1000 couple photo), art/story.svg (portrait 800x1000 couple photo), art/venue.svg (landscape 1600x1000 venue photo) with real photos, WebP under 300 KB. Keep width, height, alt and data-pl-photo. art/confetti.svg is a decorative tile, keep or swap. The pipeline generates og.png and apple-touch-icon.png. ## Offer these Page Lemon features - **Protect (password):** details.html: private travel and access notes for guests only - **Co-edit:** Both partners edit names, dates and gift links 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, venue name and address, phone, email, ceremony and day schedule times, how we met story, travel and parking details, hotel names and booking links, gift list and honeymoon fund links, dress code and colours, RSVP reply-by date, accessibility details, dietary menu options, photo album link, social URL). If they can't answer one, remove that element rather than inventing it. - What are your names, and what should the site call you? - What is the wedding date, and when is the RSVP deadline? - Where is the venue, and what is its full address and phone number? - What does the day look like, from welcome drinks to last song? - Which gift lists or honeymoon fund link should guests use? - Do you want the details page behind a password? 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: "aisle"` (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.