# Carte: a Page Lemon website template > A night-blue trattoria menu for the table: a printable table card with a QR code opens a fast phone menu with sections, prices, allergen letters and tonight's specials, which you change by asking your AI. You are reading this because the user wants their own website made from the Carte template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Carte": 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: "carte"` 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:** Firefly trattoria (dark, calm, classic) - **Pages:** Menu (`index.html`): The menu first: today's specials, sticky section tabs, every dish with price, one-line description and allergen letters, a folded 14-letter key, order with your server; Wine (`wine.html`): Wines by the glass, carafe and bottle, with colour, region and a line on how the house pours; Allergens (`allergens.html`): The 14 UK allergens key with letters and how to ask the team before ordering; About (`about.html`): Short story of the osteria with the dining-room picture, the chef and front of house, opening hours, address and booking by phone; Table card (`table-card.html`): Owner page, not in the menus: printable A6 card with restaurant name, Scan for today's menu, a framed square for the printed QR code, Wi-Fi from the team - **Fonts:** Cormorant Garamond, Figtree (Google Fonts) - **Colours:** `--night` #0D1730, `--night-2` #15223F, `--cream` #F5ECDA, `--amber` #F4B045, `--basil` #86C685 - **Live demo:** https://pagelemon.com/templates/carte/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Carte; the page about it is https://pagelemon.com/tp/Carte/use) - **Manifest:** https://pagelemon.com/templates/carte/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made One illustration (art/hero.svg) on the About page: a lit arched trattoria window at night, fireflies in amber and basil green, a printed menu card on a laid table. The body carries a firefly-dot pattern in CSS, not an image. No raster images: the owner adds a dining-room photo to the hero frame later. To sketch similar art: "Flat illustration on deep night blue: an arched warm-lit window, a candle glow in amber, small fireflies in amber and basil green, a cream printed menu card on a table in the foreground with two basil leaves." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "carte"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/carte/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/carte/index.html - https://pagelemon.com/templates/carte/wine.html - https://pagelemon.com/templates/carte/allergens.html - https://pagelemon.com/templates/carte/about.html - https://pagelemon.com/templates/carte/table-card.html - https://pagelemon.com/templates/carte/404.html - https://pagelemon.com/templates/carte/privacy.html - https://pagelemon.com/templates/carte/styles.css - https://pagelemon.com/templates/carte/script.js - https://pagelemon.com/templates/carte/favicon.svg - https://pagelemon.com/templates/carte/og.png - https://pagelemon.com/templates/carte/apple-touch-icon.png - https://pagelemon.com/templates/carte/art/hero.svg - https://pagelemon.com/templates/carte/art/qr-frame.svg ## Notes for Carte (its `customise` rules) - Osteria Lucciola in metadata, wordmark, footer and JSON-LD; replace every data-pl-fill fact - Keep name, address and phone identical in the footer, about page and JSON-LD - The menu is a List: sections (Today's specials, Antipasti, Pasta, Secondi, Contorni, Dolci, Soft drinks), menu (dishes with price, allergen letters, vegetarian and special flags) and wines. Change them as list items once the site is kept, or ask your AI in chat - Allergen letters and the vegetarian flag on each dish must match the kitchen's recipes (parmesan, pecorino and panna cotta are not vegetarian unless the recipe says so); allergens.html states the 14 UK allergens and how to ask the team - Hours, the chef and front-of-house names and the Wi-Fi line on table-card.html are placeholders until the owner checks them - **Colours:** Edit the :root tokens at the top of styles.css (night blue, candle amber, basil green, cream) - **Fonts:** Change the Google Fonts link in every page and --font-display / --font-body in styles.css; Cormorant Garamond sets the printed-card headings, Figtree the menu text - **Sections:** Every page shares the header, footer and the mobile Menu / Wine / Allergens bar; the call to book sits in the Pages menu, the About page and the footer. The table card page is for the owner to print and is not linked from the menus. The menu tabs are built by script.js from the sections, and every section stays readable stacked without JavaScript. The QR code on table-card.html is a sample that points at this template's own address: make one with any QR generator that points at the owner's menu address, then replace art/qr-frame.svg with it at 1:1 before printing - **Images:** art/hero.svg sits on the About page (the menu page has no image, so dishes come first): replace it with a 3:2 photo of the dining room at night (960×640 or larger, WebP under 200 KB). art/qr-frame.svg on table-card.html is the QR code printed on the card: replace it with the owner's own code at 1:1, kept square and at least 3 cm wide when printed ## 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, menu sections, dishes, prices and allergen letters, wines, regions and prices, chef and front-of-house names, Wi-Fi arrangement). If they can't answer one, remove that element rather than inventing it. - What is the restaurant called and where is it? - What phone number should guests call to book? - What are the opening hours for lunch and dinner? - Which dishes, prices and allergen letters go on the menu? - Which wines do you pour by the glass, carafe and bottle? - Who are the chef and the front-of-house lead? 2. **Get the files.** If you have the Page Lemon tool (the MCP connector with a `deploy` tool; https://pagelemon.com/docs/connect sets it up), call `deploy` with `template: "carte"` (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.** The sample town, street and people's names also appear in ordinary sentences, `aria-label`s and image `alt` text: replace them there too. 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. Delete each whole review, with its name or caption, and the section and its nav link when none is left. 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, `geo` coordinates (delete them unless you have the real ones), 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. - Make a new `og.png` (1200×630) of the new home page if you can, with its `og:image` tags; otherwise delete the sample one and its `og:image` tags (a template deploy has already left both out). 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 Site 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 and Booking: any paid plan; staff and rooms only on some, and each plan has a limit of online bookings a day), set the form up as a list (`save_list`) or the service (`save_service`), put the matching markup 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`, the template's fictional business name and its sample phone, email and street, in links too (`tel:` and `mailto:` hrefs, and map links, where the street is written like `18+Linden+Walk`): 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. (at most 100 files and 1 MB in all, `index.html` at the root): ```bash node -e 'const fs=require("fs"),p=require("path"),d=process.argv[1],files=[];(function w(x){for(const e of fs.readdirSync(x,{withFileTypes:true})){const f=p.join(x,e.name);e.isDirectory()?w(f):files.push({path:p.relative(d,f).split(p.sep).join("/"),content_base64:fs.readFileSync(f).toString("base64")})}})(d);console.log(JSON.stringify({files}))' <dir> \ | curl -sS --fail-with-body -H "Content-Type: application/json" --data-binary @- https://api.pagelemon.com/v2/anonymous-sites ``` If the user gave you an API key (`plak_…`) or `~/.config/pagelemon/credentials` exists, publish into their account instead (see "Updating a site" in https://pagelemon.com/agents). 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/mcp`): call its `publish_site` tool with every file. See "No shell: the MCP connector" in https://pagelemon.com/agents. 3. **Neither (a chat app without the Page Lemon connector):** say once that they can connect Page Lemon to this AI app (steps at https://pagelemon.com/docs/connect) so you can publish and change the site for them. In the Gemini app or Grok (free plan included) it takes about a minute: Gemini at gemini.google.com/customize/connectors (**Custom**), Grok at grok.com/connectors (**New Connector**, **Custom**), with the link `https://mcp.pagelemon.com/mcp`; then they sign in and click **Allow**. Give those steps in plain words. If they can't or would rather not (for example ChatGPT's free plan), don't ask them to save or upload files. Put the whole site in ONE complete page: CSS and JavaScript inline, images as https links or small data URIs, from `<!DOCTYPE html>` to `</html>`. Show it as one code block, then tell them: "Tap Copy on the code, open pagelemon.com/publish, tap Paste and publish." Only if you can really give them a downloadable .zip (a file they tap to download, not code to save): "Download this zip, open pagelemon.com/publish, tap Drop or choose a file." They get a live link with no account, online for 72 hours unless they tap **Keep it free**. 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.