# Muster: a Page Lemon website template > A light dotted whiteboard canvas for collaboration software: saturated sticky notes, hand-drawn connectors and named live cursors that drift and work on the hero board. You are reading this because the user wants their own website made from the Muster template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Muster": 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: "muster"` 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:** Dotted whiteboard canvas with sticky notes and live cursors (light, bold, modern) - **Pages:** Product (`index.html`): Live board hero with draggable notes and working cursors, teams strip, three-frame session flow, annotated product shot, facilitator kit wall, numbers, quotes, template teaser and a sign-up call to action; Templates (`templates.html`): Filterable workshop templates (retro, planning, discovery, warm-up) with timings and steps, plus a minute-by-minute workshop agenda; Pricing (`pricing.html`): Three illustrative plans per editor with one highlighted, monthly/yearly toggle, editor cost calculator, comparison table and pricing questions; Integrations (`integrations.html`): Before/after flow diagram, filterable directory of placeholder integrations and a webhook example; Contact (`contact.html`): Free board sign-up slot with an email fallback, what happens next, office details and a walkthrough call to action - **Fonts:** Lexend, Shantell Sans (Google Fonts) - **Colours:** `--canvas` #f2f3f7, `--ink` #16171f, `--coral` #ff7a5c, `--lemon` #ffd84a, `--mint` #52e0a2, `--lilac` #b59dff - **Live demo:** https://pagelemon.com/templates/muster/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Muster/preview) - **Manifest:** https://pagelemon.com/templates/muster/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made No raster art. The page itself is a dotted canvas. The hero is an HTML board: six sticky notes in marker type, hand-drawn SVG connectors that draw in, a round timer and four named cursors that drift between notes, nudge them and drop vote dots (static under reduced motion or without JS). Notes on the board are draggable. To sketch similar art: "Draw a flat SVG whiteboard on a pale grey dotted canvas: square sticky notes in coral, lemon, mint, pink, lilac and aqua with dark scribble lines, loose hand-drawn black arrows, and small coloured cursor arrows with name tags." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "muster"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/muster/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/muster/index.html - https://pagelemon.com/templates/muster/templates.html - https://pagelemon.com/templates/muster/pricing.html - https://pagelemon.com/templates/muster/integrations.html - https://pagelemon.com/templates/muster/contact.html - https://pagelemon.com/templates/muster/404.html - https://pagelemon.com/templates/muster/privacy.html - https://pagelemon.com/templates/muster/styles.css - https://pagelemon.com/templates/muster/script.js - https://pagelemon.com/templates/muster/favicon.svg - https://pagelemon.com/templates/muster/og.png - https://pagelemon.com/templates/muster/apple-touch-icon.png - https://pagelemon.com/templates/muster/art/board-retro.svg - https://pagelemon.com/templates/muster/art/tpl-retro.svg - https://pagelemon.com/templates/muster/art/tpl-planning.svg - https://pagelemon.com/templates/muster/art/tpl-discovery.svg - https://pagelemon.com/templates/muster/art/tpl-warmup.svg - https://pagelemon.com/templates/muster/art/tpl-roadmap.svg - https://pagelemon.com/templates/muster/art/tpl-mapping.svg - https://pagelemon.com/templates/muster/art/avatar-1.svg - https://pagelemon.com/templates/muster/art/avatar-2.svg ## Notes for Muster (its `customise` rules) - Product name 'Muster' in , header wordmark, footer and JSON-LD - Hero board notes, column labels and cursor names in .board on index.html - Team names in .teams and the stats in .nums on index.html - Plan names, prices (data-month / data-year) and the .calc rates on pricing.html - Integration names and descriptions in .tiles on integrations.html - Company address, phone and email in the footer, contact.html and JSON-LD - **Colours:** Edit the :root tokens at the top of styles.css: canvas, dot, ink and the six note colours (coral, lemon, mint, pink, lilac, aqua). Keep --coral-ink dark enough for text on the canvas. - **Fonts:** Lexend (variable, 400 to 700) for the interface and Shantell Sans (500 to 700) for handwriting. Change the Google Fonts <link> in every page and --sans / --hand in styles.css. - **Sections:** Each <section> is self-contained; delete or reorder freely. The hero board positions notes and cursors with --x / --y in board-width units (cqw), with a tall layout under 540px board width and a wide one above. script.js only enhances: notes drag, cursors move and vote, the timer counts. - **Images:** Replace art/board-retro.svg (product screenshot, 1600×1000), art/tpl-*.svg (template screenshots, 1200×900, 4:3) and art/avatar-1.svg, art/avatar-2.svg (customer headshots, 800×800 square) with real images; WebP under 300 KB. Keep width, height, alt and data-pl-photo. ## 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 (product name, company name and address, phone, email, plan names and prices, integrations offered, customer names and quotes, beta statistics). If they can't answer one, remove that element rather than inventing it. - What is the product called, and what does it do in one sentence? - Which kinds of sessions do your users run on it most? - How is it priced: per editor, per seat or flat, and is there a free plan? - Which tools does it integrate with today? - Which customers can be named, and may we quote them? - What email address and phone number should sign-ups 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: "muster"` (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.