# Brasa: a Page Lemon website template > A warm, confident live-fire grill: big expanded type, a glowing ember-sun hero, a cream paper menu with prices and an ember-orange Sunday lunch band. You are reading this because the user wants their own website made from the Brasa template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Brasa": 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: "brasa"` 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:** Warm live-fire grill (dark, bold, modern) - **Pages:** Home (`index.html`): Ember-sun hero, signature plates, menu preview with prices, Sunday lunch, booking, hours, location and contact; Menu (`menu.html`): Full Fire, Sea, Garden and Sweet menu with prices, dietary key and wine list; Visit (`visit.html`): Hours, location, access, parking, dogs and FAQ; Our hearth (`about.html`): Open hearth, chef portraits and sourcing; Book a table (`book.html`): Booking fallback and private dining enquiries - **Fonts:** Archivo, Fraunces (Google Fonts) - **Colours:** `--bg` #15100C, `--ink` #F4EADB, `--ember` #F26A24, `--amber` #FFB547, `--paper` #F4EADB - **Live demo:** https://pagelemon.com/templates/brasa/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Brasa/preview) - **Manifest:** https://pagelemon.com/templates/brasa/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made All art is flat SVG in art/ on a dark-to-ember palette with radial heat glows. fire.svg is an ember sun cut by grill bars; dishes are geometric plates (rib, bream, hispi cabbage) on a faint grate; hearth is a brick arch with logs; portraits are arch frames with a flame or leaf emblem. Embers and the ticker are CSS-animated. Icons are inline line SVGs. To sketch similar art: "Flat geometric SVG on near-black: a glowing orange-to-amber sun cut by horizontal charcoal grill bars, soft radial heat halo, a few amber ember dots." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "brasa"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/brasa/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/brasa/index.html - https://pagelemon.com/templates/brasa/menu.html - https://pagelemon.com/templates/brasa/visit.html - https://pagelemon.com/templates/brasa/about.html - https://pagelemon.com/templates/brasa/book.html - https://pagelemon.com/templates/brasa/404.html - https://pagelemon.com/templates/brasa/privacy.html - https://pagelemon.com/templates/brasa/styles.css - https://pagelemon.com/templates/brasa/script.js - https://pagelemon.com/templates/brasa/favicon.svg - https://pagelemon.com/templates/brasa/og.png - https://pagelemon.com/templates/brasa/apple-touch-icon.png - https://pagelemon.com/templates/brasa/art/fire.svg - https://pagelemon.com/templates/brasa/art/grain.svg - https://pagelemon.com/templates/brasa/art/dish-short-rib.svg - https://pagelemon.com/templates/brasa/art/dish-bream.svg - https://pagelemon.com/templates/brasa/art/dish-cabbage.svg - https://pagelemon.com/templates/brasa/art/hearth.svg - https://pagelemon.com/templates/brasa/art/teo-marsh.svg - https://pagelemon.com/templates/brasa/art/lucia-ferrer.svg ## Notes for Brasa (its `customise` rules) - Brasa in metadata, wordmark, footer and JSON-LD; replace all data-pl-fill facts - Keep name, address and phone identical in footer, visit page and JSON-LD - Edit menu items, prices and dietary tags in menu.html and the two-column preview on index.html - Replace chef biographies, suppliers, access, parking, hours and coordinates with verified facts - Booking slot uses tel; optionally add the owner’s external booking link marked data-pl-fill="link"; private dining uses mailto with subject - **Colours:** Edit the :root tokens at the top of styles.css - **Fonts:** Change the Google Fonts link in every page and --font-display/--font-body/--font-accent; Archivo uses its width axis (font-stretch), Fraunces italic is the accent - **Sections:** Every page shares header, footer and the mobile Call / Book / Directions bar. Menu tabs enhance anchors; all categories stay visible without JS. Forms stay inert in their slot templates until a real plugin is connected. The ticker and embers stop under prefers-reduced-motion. - **Images:** art/fire.svg is the decorative ember-sun hero (keep, or replace with a square fire photo). Replace dish-short-rib, dish-bream, dish-cabbage and hearth (landscape 1600x1000) and teo-marsh, lucia-ferrer (portraits 800x1000) with WebP photos under 300 KB, keeping data-pl-photo and dimensions. Keep decorative art/grain.svg. 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, menu items and prices, dietary suitability, chefs, suppliers, access and parking, geographic coordinates, service charge). If they can't answer one, remove that element rather than inventing it. - What is the restaurant called? - What is the full address? - What phone number should diners use to book? - What are the kitchen opening hours? - Which dishes, prices and dietary tags belong on the menu? - Who are the chefs? - Which email address should private dining enquiries use? 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: "brasa"` (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.