# Ferro: a Page Lemon website template > An industrial grey and safety orange hardware site with technical drawing lines, condensed type, spec tables and a numbered product section drawing. You are reading this because the user wants their own website made from the Ferro template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Ferro": 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: "ferro"` 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:** Industrial grey and safety orange, technical drawing, spec sheet (light, bold, modern) - **Pages:** Home (`index.html`): Headline, key figures, where it fits, how it works, pilot quotes, site survey booking and a closing pilot call to action; Product (`product.html`): Numbered section drawing with callouts linked to the full spec table and an honest what-it-is-not section; How it's made (`how-its-made.html`): Four production stages with images, plus where the parts come from; Pilots (`pilots.html`): Live pilot sites, eligibility, monitoring commitment and an inert pilot request form; Press (`press.html`): Dated releases, company boilerplate and media contact; Careers (`careers.html`): Open roles, how the hiring process works and an inert application form - **Fonts:** Barlow Condensed, Barlow (Google Fonts) - **Colours:** `--bg` #E7E9EB, `--ink` #14171A, `--accent` #FF5A00, `--steel` #4B535B, `--graphite` #1D2125 - **Live demo:** https://pagelemon.com/templates/ferro/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Ferro/preview) - **Manifest:** https://pagelemon.com/templates/ferro/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made Hero is a side elevation of the store with dimension lines; product page has an inline section drawing with numbered leader lines that draw in on scroll; process images are flat line drawings with hatch fills in grey and orange. To sketch similar art: "Draw a flat SVG technical drawing of an industrial heat store in side elevation, with dimension lines, hatch fill in safety orange on a grey grid, and black line work." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "ferro"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/ferro/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/ferro/index.html - https://pagelemon.com/templates/ferro/product.html - https://pagelemon.com/templates/ferro/how-its-made.html - https://pagelemon.com/templates/ferro/pilots.html - https://pagelemon.com/templates/ferro/press.html - https://pagelemon.com/templates/ferro/careers.html - https://pagelemon.com/templates/ferro/privacy.html - https://pagelemon.com/templates/ferro/404.html - https://pagelemon.com/templates/ferro/styles.css - https://pagelemon.com/templates/ferro/script.js - https://pagelemon.com/templates/ferro/favicon.svg - https://pagelemon.com/templates/ferro/og.png - https://pagelemon.com/templates/ferro/apple-touch-icon.png - https://pagelemon.com/templates/ferro/art/hero.svg - https://pagelemon.com/templates/ferro/art/cast.svg - https://pagelemon.com/templates/ferro/art/seal.svg - https://pagelemon.com/templates/ferro/art/assemble.svg - https://pagelemon.com/templates/ferro/art/test.svg - https://pagelemon.com/templates/ferro/art/site.svg - https://pagelemon.com/templates/ferro/art/bench.svg ## Notes for Ferro (its `customise` rules) - Replace every data-pl-fill fact: business name in title, header, footer and JSON-LD; address and phone identical in footer and JSON-LD. - Replace the product spec table, callout text and the 40 kWh, 22 kW, 90 °C and 10-year figures everywhere they appear, including the meta description. - Replace pilot sites, quotes and press releases with owner-supplied real ones; remove any quote the owner cannot confirm. - Replace the example.com email addresses and the example.com LinkedIn and X links with real ones. - **Colours:** Edit the commented :root tokens at the start of styles.css; keep text on --bg at 4.5:1 or better and use --safety only as a fill. - **Fonts:** Barlow Condensed 600/700 and Barlow 400/600: four files. Edit the Google Fonts link in every HTML head and the two font tokens in styles.css. - **Sections:** The product drawing is inline SVG with four numbered parts; keep the callout numbers in step with the spec rows. Forms are inert until a plugin is connected. - **Images:** Replace art/hero.svg, art/cast.svg, art/seal.svg, art/assemble.svg, art/test.svg, art/site.svg and art/bench.svg with landscape 1600×1000 photos, WebP under 300 KB. Keep the frame aspect ratio and data-pl-photo notes. ## 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, product specifications (capacity, charge input, output temperature, hold time, footprint, weight, noise, warranty), certification status, pilot sites, dates and monitoring results, press release dates and headlines, open roles and benefits, employee count and parts sourcing share). If they can't answer one, remove that element rather than inventing it. - What is the company called and where is the factory? - What does the product do and what are its three headline numbers? - Which pilot sites can be named, and since when are they live? - What is the current certification status? - Which roles are open and where are they based? - What email address should press and pilot 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: "ferro"` (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.