# Plinth: a Page Lemon website template > A small architecture practice portfolio in board-marked concrete grey and soft terracotta, carried by precise line drawings: a filterable project index with live previews and plan, section and axonometric toggles on every case study. You are reading this because the user wants their own website made from the Plinth template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Plinth": 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: "plinth"` 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:** Concrete and terracotta drawing sheets (light, calm, modern) - **Pages:** Home (`index.html`): Hero axonometric sheet with live grid readout, four typologies, two featured projects, a short project index with hover previews, four-stage process, client quote and enquiry call to action; Projects (`work.html`): Full project index table filtered by typology (houses, civic, retrofit, interiors) with a pinned drawing preview that follows hover, focus or scroll; Weir Cottage (`case-weir-cottage.html`): House case study: facts, main photo, plan / section / axonometric toggle with title block, brief, numbers, interior photo, quote, credits; Corn Exchange Library (`case-corn-exchange.html`): Civic case study with the same structure as Weir Cottage; Practice (`about.html`): Studio photo, how the practice works, four principles, four people with portraits, awards table; Contact (`contact.html`): Project enquiry slot (email and phone fallback, inert enquiry form), what happens next, studio address, hours and directions - **Fonts:** Lexend Giga, Host Grotesk (Google Fonts) - **Colours:** `--bg` #E4E0DA, `--sheet` #F1EFEB, `--ink` #2B2825, `--accent` #A9533A, `--dark` #34302C - **Live demo:** https://pagelemon.com/templates/plinth/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Plinth/preview) - **Manifest:** https://pagelemon.com/templates/plinth/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made All art is original SVG. Line drawings use a 30/60 plan-oblique axonometric with hatched shadows, plans with solid poché walls, door swings, grid bubbles and dimension strings, and sections with earth hatching and level markers. Existing fabric is drawn in warm graphite, new work in terracotta. Photo placeholders are flat duotone dusk elevations, one-point interiors and abstract portraits in the same palette. To sketch similar art: "Draw a precise architectural axonometric in 30/60 plan-oblique of a stone cottage with a new timber extension, thin warm-graphite lines on pale warm grey, new work filled in soft terracotta, hatched shadows, small human figures and lollipop trees, no text." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "plinth"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/plinth/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/plinth/index.html - https://pagelemon.com/templates/plinth/work.html - https://pagelemon.com/templates/plinth/case-weir-cottage.html - https://pagelemon.com/templates/plinth/case-corn-exchange.html - https://pagelemon.com/templates/plinth/about.html - https://pagelemon.com/templates/plinth/contact.html - https://pagelemon.com/templates/plinth/404.html - https://pagelemon.com/templates/plinth/privacy.html - https://pagelemon.com/templates/plinth/styles.css - https://pagelemon.com/templates/plinth/script.js - https://pagelemon.com/templates/plinth/favicon.svg - https://pagelemon.com/templates/plinth/og.png - https://pagelemon.com/templates/plinth/apple-touch-icon.png - https://pagelemon.com/templates/plinth/art/hero-weir.svg - https://pagelemon.com/templates/plinth/art/weir-axo.svg - https://pagelemon.com/templates/plinth/art/weir-plan.svg - https://pagelemon.com/templates/plinth/art/weir-section.svg - https://pagelemon.com/templates/plinth/art/weir-photo.svg - https://pagelemon.com/templates/plinth/art/weir-interior.svg - https://pagelemon.com/templates/plinth/art/corn-axo.svg - https://pagelemon.com/templates/plinth/art/corn-plan.svg - https://pagelemon.com/templates/plinth/art/corn-section.svg - https://pagelemon.com/templates/plinth/art/corn-photo.svg - https://pagelemon.com/templates/plinth/art/corn-interior.svg - https://pagelemon.com/templates/plinth/art/tanners-axo.svg - https://pagelemon.com/templates/plinth/art/kiln-axo.svg - https://pagelemon.com/templates/plinth/art/pavilion-axo.svg - https://pagelemon.com/templates/plinth/art/larder-axo.svg - https://pagelemon.com/templates/plinth/art/mill-axo.svg - https://pagelemon.com/templates/plinth/art/sedge-axo.svg - https://pagelemon.com/templates/plinth/art/orchard-axo.svg - https://pagelemon.com/templates/plinth/art/gatehouse-axo.svg - https://pagelemon.com/templates/plinth/art/studio.svg - https://pagelemon.com/templates/plinth/art/person-hester.svg - https://pagelemon.com/templates/plinth/art/person-dev.svg - https://pagelemon.com/templates/plinth/art/person-ruth.svg - https://pagelemon.com/templates/plinth/art/person-sol.svg ## Notes for Plinth (its `customise` rules) - Practice name 'Plinth Architects' (wordmark 'plinth') in every , the header, the footer title block, JSON-LD and privacy.html - Keep name, address 'Unit 4, Saltmill Yard, Harrowfold QH4 7LN' and phone '01632 960 952' identical in the footer, contact.html and the JSON-LD in index.html - Project rows live in work.html and index.html (data-p, data-type, data-name, data-meta on each <tr>); each data-p needs a matching <figure data-p> in the preview and, for hover without JavaScript, a line in the ':has(tr[data-p=...])' block of styles.css - Case pages: facts, drawings (art/<key>-plan.svg, -section.svg, -axo.svg), title block text, notes, story, stats, quote and credits - Every data-pl-fill element is a placeholder fact; sample quotes (data-pl-fill=review) must be replaced with real ones or removed - **Colours:** Edit the commented :root tokens at the top of styles.css. The drawings in art/ use the same greys and terracotta; recolour them with a find-and-replace on #B35A3C, #8E4329, #E3B8A4 and #F0DDD2. - **Fonts:** Lexend Giga 200/300 (display) and Host Grotesk 400/500 (body). Change the Google Fonts <link> in every page head and --font-display / --font-body. - **Sections:** Every <section> is self-contained; reorder or delete freely. The drawing toggle and the index filter are radio inputs styled with :has(), so they work without script.js; script.js adds counts, keyboard shortcuts (P, S, A), arrow-key row navigation and scroll-linked previews on phones. - **Images:** Photo frames: art/weir-photo.svg, corn-photo.svg, weir-interior.svg, corn-interior.svg and studio.svg are landscape 1600×1000; person-*.svg are portrait 800×1000. Drawings: replace art/*-plan.svg, *-section.svg and *-axo.svg with your own drawings exported as SVG (or PNG/WebP) on a light background, 3:2 for case pages and 4:3 for index previews. Keep width, height and data-pl-photo; WebP under 300 KB. og.png and apple-touch-icon.png are generated by the pipeline. ## 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 (practice name, studio address, telephone, email, studio hours, project names, places, years and typologies, case study facts, fees and credits, people and roles, awards, feasibility fee, social links, registered practice number). If they can't answer one, remove that element rather than inventing it. - What is the practice called and where is the studio? - Which telephone number and email should enquiries go to? - Which 6 to 12 projects should be in the index, with place, year and typology? - Which two projects deserve full case studies, and do you have a plan, a section and a 3D view of each? - Who works at the practice and what does each person do? - Which awards or publications should be listed? - What does a first meeting or feasibility study cost? 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: "plinth"` (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.