# Atlas: a Page Lemon website template > A destination wedding styled as travel documents: a boarding pass for the couple, itinerary tickets, route-line maps, passport stamps that land as you scroll, and a departures board for things to do. You are reading this because the user wants their own website made from the Atlas template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Atlas": 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: "atlas"` 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:** Travel documents: boarding passes, route lines and passport stamps (light, bold, modern) - **Pages:** Home (`index.html`): Boarding pass hero, the three days, route, stays, activities, packing and final RSVP call; Itinerary (`itinerary.html`): Each day as a ticket with a timed list of events; Getting there (`getting-there.html`): Three routes with shuttle times, parking and a carry-on checklist; Stays (`stays.html`): Rooms and villas as a leader-dot price list, with booking links; Things to do (`activities.html`): Departures board of optional activities with places left; RSVP (`rsvp.html`): Reply by 1 July: one RSVP form with a field per event, plus the email and phone fallback - **Fonts:** Archivo, Barlow Condensed (Google Fonts) - **Colours:** `--navy` #0F2A5C, `--terra` #B4482A, `--terra-soft` #F0A884, `--sky` #E6EEF9, `--ink` #14203A - **Live demo:** https://pagelemon.com/templates/atlas/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Atlas/preview) - **Manifest:** https://pagelemon.com/templates/atlas/template.json (machine-readable: files, customise, slots, facts, interview) ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "atlas"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/atlas/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/atlas/index.html - https://pagelemon.com/templates/atlas/itinerary.html - https://pagelemon.com/templates/atlas/getting-there.html - https://pagelemon.com/templates/atlas/stays.html - https://pagelemon.com/templates/atlas/activities.html - https://pagelemon.com/templates/atlas/rsvp.html - https://pagelemon.com/templates/atlas/404.html - https://pagelemon.com/templates/atlas/privacy.html - https://pagelemon.com/templates/atlas/styles.css - https://pagelemon.com/templates/atlas/script.js - https://pagelemon.com/templates/atlas/favicon.svg - https://pagelemon.com/templates/atlas/art/route.svg - https://pagelemon.com/templates/atlas/art/villa.svg - https://pagelemon.com/templates/atlas/og.png - https://pagelemon.com/templates/atlas/apple-touch-icon.png ## Notes for Atlas (its `customise` rules) - Couple names 'Ottilie Wenlow' and 'Teo Ansari' (and 'Ottilie & Teo' as the wordmark) in every , meta description, the hero, the boarding pass and the footer - Date '18 September 2027', venue 'Casa Sollen' at 'Rua do Farol 14, Porto Vaila', and the reply-by date '1 July' in the header, hero, pass stub and footer. Name, address and phone must match in the footer, the Event JSON-LD and the venue details - Day tickets on index.html and the full timed list on itinerary.html (Friday welcome drinks, Saturday ceremony and dinner, Sunday lunch and boat) - Routes and shuttle times on getting-there.html; room names and prices on stays.html and index.html; activities and places left on activities.html (data-pl-fill stat) - Event checkboxes and the 'Arriving on' options in the RSVP form on rsvp.html - Stamp words ('Arrived', 'Stamped', 'Departed', 'Welcome') and the footer phone and email - **Colours:** Edit the :root tokens at the top of styles.css. Navy and terracotta carry the look; keep the sky wash and white grounds, and avoid cream backgrounds - **Fonts:** Change the Google Fonts <link> on each page and --display / --label in styles.css. Keep at most two families - **Sections:** Each boarding-pass ticket and departures-board row is self-contained; delete, duplicate or reorder them. Stamps are plain elements with a rotation, so they can move. The RSVP fields live in the <template data-pl-slot-form="rsvp"> block on rsvp.html - **Images:** art/villa.svg is the venue frame (landscape 16:10, 1600×1000): replace with a WebP of the venue under 300 KB. art/route.svg is the map-line frame (16:10): replace with a map or a photo of the coast, keeping the dashed route as an overlay if you like ## Offer these Page Lemon features - **Protect (password):** stays.html and itinerary.html if room blocks or addresses should stay with guests - **Co-edit:** The couple and the wedding planner edit the itinerary 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, phone and email, reply-by date, events and their times (Friday drinks, Saturday ceremony and dinner, Sunday lunch and boat), shuttle times from the airport and the coast bus, room names and nightly prices, activities, times and places left). If they can't answer one, remove that element rather than inventing it. - What are your names, and what should the wedding site be called? - Where is the wedding, and what is the venue called? - What is the date, and what time does the ceremony start? - Which events are you running (drinks, ceremony, dinner, lunch, boat, others)? - Where will guests fly or drive in from, and do you run shuttles? - Where can guests stay, and what does each place cost a night? - When do you need RSVPs by, and who should receive them? 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: "atlas"` (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.