# Cinder: a Page Lemon website template > A neo-brutalist open-source project site: pure white, 3px black borders, hard offset shadows, hot-red and yellow stickers and a big install command with a copy button. You are reading this because the user wants their own website made from the Cinder template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Cinder": 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: "cinder"` 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:** Neo-brutalist open source: hard shadows and stickers (light, bold, modern) - **Pages:** Home (`index.html`): One-line promise, big install command with copy button, feature bento, terminal demo, review, roadmap teaser and sponsor band; Install (`install.html`): Four install routes with copy buttons, a version check, a platform table and a first-build walkthrough; Docs (`docs.html`): Docs index with a sticky section list: quick start, config keys, layouts, front matter, plugins, CLI reference and deploying; Roadmap (`roadmap.html`): Now, Next and Later columns linked to issues, plus a not-planned list; Sponsors (`sponsors.html`): Three sponsor tiers with a highlighted middle tier, a logo wall and an inert sponsor enquiry form with a mailto fallback; Contributors (`contributors.html`): Maintainer cards, recent contributor chips and a three-step guide to joining - **Fonts:** Archivo Black, Azeret Mono (Google Fonts) - **Colours:** `--paper` #FFFFFF, `--ink` #000000, `--red` #FF2D1A, `--yellow` #FFD60A - **Live demo:** https://pagelemon.com/templates/cinder/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Cinder/preview) - **Manifest:** https://pagelemon.com/templates/cinder/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Flat SVG shapes only: hard-edged black offset shadows, primary red and yellow fills, white paper. The terminal illustration is a light window with a monospace transcript. Avatars are simple geometric figures. To sketch similar art: "Draw a flat neo-brutalist SVG composition of overlapping squares and circles in hot red, yellow and black on white, with hard offset black shadows and 6px black outlines." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "cinder"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/cinder/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/cinder/index.html - https://pagelemon.com/templates/cinder/install.html - https://pagelemon.com/templates/cinder/docs.html - https://pagelemon.com/templates/cinder/roadmap.html - https://pagelemon.com/templates/cinder/sponsors.html - https://pagelemon.com/templates/cinder/contributors.html - https://pagelemon.com/templates/cinder/privacy.html - https://pagelemon.com/templates/cinder/404.html - https://pagelemon.com/templates/cinder/styles.css - https://pagelemon.com/templates/cinder/script.js - https://pagelemon.com/templates/cinder/favicon.svg - https://pagelemon.com/templates/cinder/og.png - https://pagelemon.com/templates/cinder/apple-touch-icon.png - https://pagelemon.com/templates/cinder/art/hero.svg - https://pagelemon.com/templates/cinder/art/terminal.svg - https://pagelemon.com/templates/cinder/art/avatar-1.svg - https://pagelemon.com/templates/cinder/art/avatar-2.svg - https://pagelemon.com/templates/cinder/art/avatar-3.svg ## Notes for Cinder (its `customise` rules) - Replace the install command in index.html and install.html, and the copy-button data-copy attributes, so they match exactly. - Replace every data-pl-fill fact: name, email, stars, version, sponsor names, maintainers, contributor handles and issue numbers. - Replace the example.com source, releases and issue links with the real project URLs. - Rewrite the docs index sections and the CLI reference table to match your tool. - **Colours:** Edit the commented :root tokens at the start of styles.css. Keep hard black borders and check that text on red and yellow stays at 4.5:1. - **Fonts:** Archivo Black (regular) and Azeret Mono (400 and 700): two families, three files. Edit the Google Fonts link in every HTML head and the two font tokens in styles.css. - **Sections:** All pages share the header, footer and skip link. Stickers and the ticker are decorative and can be removed. Keep the install CTA in the hero, the final band and the footer. The sponsor form stays inert until a real form plugin is connected. - **Images:** Replace hero.svg with a square 800×800 illustration, terminal.svg with a real 1600×1000 terminal screenshot, and avatar-1..3.svg with square 400×400 portraits. Preserve dimensions and data-pl-photo. WebP under 300 KB each. The pipeline generates 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, email, install command, version number, star count, sponsor tiers and prices, sponsor names and logos, maintainer names and roles, contributor handles, roadmap items and issue numbers, source, releases and CONTRIBUTING links, review quotes). If they can't answer one, remove that element rather than inventing it. - What is the project called, and what does it do in one sentence? - What is the install command for your main platform? - Which licence does it use? - Who maintains it, and what is each person's role? - What are your sponsor tiers and their monthly prices? - What are the three or four items on the roadmap right now? 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: "cinder"` (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.