# Hatch: a Page Lemon website template > A bright food truck site for a Korean fried chicken and bao stall: a weekly rota of where the bus is, a menu with prices and tags, pre-orders for collection at the pitch, and a page to book the bus for weddings and private hire. You are reading this because the user wants their own website made from the Hatch template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Hatch": 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: "hatch"` 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:** Gochujang and mint: a chilli red, mint and cream VW bus with a serving hatch (light, bold, modern) - **Pages:** Home (`index.html`): Hero with the bus, where we are this week from the rota, today’s highlights, pre-order for collection and private hire; Menu (`menu.html`): Full menu grouped by section (Chicken, Bao, Sides, Drinks) with prices, dietary tags and an allergy note; Pre-order (`preorder.html`): Pre-order for collection: pick the pitch, collection time and quantities, with the 10:00 cut-off explained; Events and hire (`events.html`): Book the bus for weddings and private hire, sample menus from £14 to £19 a head, and the date enquiry - **Fonts:** Lilita One, Nunito (Google Fonts) - **Colours:** `--chilli` #C52A1B, `--mint` #9FD8BD, `--cream` #FFF3DC, `--black` #171214 - **Live demo:** https://pagelemon.com/templates/hatch/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Hatch; the page about it is https://pagelemon.com/tp/Hatch/use) - **Manifest:** https://pagelemon.com/templates/hatch/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Flat, bright illustration with a gochujang and mint palette: a side-on VW bus with a striped awning over the serving hatch, chilli pennants, sticker-style labels and a pennant divider. Chunky Lilita One display type and friendly Nunito body text. To sketch similar art: "Flat vector side view of a mint green 1970s VW bus with a cream roof, a chilli red waistline, a serving hatch with a striped scalloped awning, and a row of chilli, mint and cream pennants on a string above it." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "hatch"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/hatch/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/hatch/index.html - https://pagelemon.com/templates/hatch/menu.html - https://pagelemon.com/templates/hatch/preorder.html - https://pagelemon.com/templates/hatch/events.html - https://pagelemon.com/templates/hatch/404.html - https://pagelemon.com/templates/hatch/privacy.html - https://pagelemon.com/templates/hatch/styles.css - https://pagelemon.com/templates/hatch/script.js - https://pagelemon.com/templates/hatch/favicon.svg - https://pagelemon.com/templates/hatch/og.png - https://pagelemon.com/templates/hatch/apple-touch-icon.png - https://pagelemon.com/templates/hatch/art/bus.svg - https://pagelemon.com/templates/hatch/art/pennants.svg - https://pagelemon.com/templates/hatch/art/dish-chicken.svg - https://pagelemon.com/templates/hatch/art/dish-bao.svg ## Notes for Hatch (its `customise` rules) - Gochu Bus in the title, wordmark, footer, JSON-LD and privacy notice; replace every data-pl-fill fact with the business’s own details - Keep the name, address (Lockkeeper’s Yard, Thornwick QX2 7HB) and phone (07700 900 731) identical in the footer, the JSON-LD and the privacy notice - The weekly rota (pitches), the menu and its sections are Lists: once the site is kept, change them as list items, and the home page and menu page fill from them - The pre-order form’s pitch options and dish quantities mirror the lists: update them when the rota or menu changes - Event sample menus and their per-head prices are data-pl-fill price facts; replace with the business’s own menus - **Colours:** Edit the :root tokens at the top of styles.css: chilli, mint, cream and black are the gochujang and mint palette - **Fonts:** Change the Google Fonts link in every page and --font-display (Lilita One) and --font-body (Nunito) in styles.css - **Sections:** Every page shares the header, footer and the mobile Call / Pre-order / Directions bar. The pennant divider is art/pennants.svg. The pre-order request and the private hire enquiry are inert until a form plugin is connected; their fallbacks are phone and email. Payment is taken at the hatch, not online. - **Images:** art/bus.svg is the side-on bus illustration with its serving hatch (hero and event pages); replace with a landscape photo of the bus at a pitch, 1600×1000, WebP under 300 KB. art/dish-chicken.svg (landscape 16:10, 1600×1000) and art/dish-bao.svg (square, 1200×1200) are photo frames for the chicken and bao; replace with real dish photos of the same shape and update width, height and alt. ## 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, weekly pitches (day, place, address, times, kind), menu items, sections, prices and dietary tags, pre-order cut-off time, private hire sample menus and prices, social links). If they can't answer one, remove that element rather than inventing it. - What is the food truck or stall called, and where is it based? - What phone number and email should customers use? - Which pitches are you at each day of the week, with times and addresses? - What is on the menu, with prices and dietary tags? - What time do pre-orders close, and how do customers collect them? - What sample menus and prices do you offer for private hire? 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: "hatch"` (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.