# Docket: a Page Lemon website template > A cool white paper site for legal and contract software: ink-blue type, red strike-throughs and blue insertions, and a hero clause that redlines itself and gets approved. You are reading this because the user wants their own website made from the Docket template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Docket": 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: "docket"` 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:** Cool white paper with live redline marks (light, bold, modern) - **Pages:** Home (`index.html`): Redlining clause hero, customer names, three steps, playbook table, before/after figures, quote, trust band, demo CTA; Product (`features.html`): Interactive accept/reject clause, what the product checks, workspace screenshot, approval routing diagram; Pricing (`pricing.html`): Three plans per reviewer seat with a monthly/annual switch, comparison table, pricing questions; Security (`security.html`): Trust schedule: data location, access, audit log, retention, sub-processors, reporting an issue; About (`about.html`): Founding story, team, house rules as amended, contact details and the demo request slot - **Fonts:** Schibsted Grotesk, Spectral (Google Fonts) - **Colours:** `--paper` #f6f8fb, `--ink` #13284d, `--red` #c8262f, `--blue` #1f4fd1 - **Live demo:** https://pagelemon.com/templates/docket/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Docket/preview) - **Manifest:** https://pagelemon.com/templates/docket/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made No raster art. Hero is an HTML clause on a sheet with pleading-paper line numbers: text is struck in red, insertions arrive in blue, a margin comment and reply slide in, then an Approved stamp lands (CSS keyframes, final state static under reduced motion). Inner pages reuse strikes and insertions in headings, a dot-leader table of contents and a contract-style trust schedule. To sketch similar art: "Draw a minimal SVG: a white contract page on a cool grey ground, two lines struck through in red, a blue inserted line with a pale blue highlight, a small margin comment bubble and a tilted blue double-ruled APPROVED stamp." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "docket"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/docket/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/docket/index.html - https://pagelemon.com/templates/docket/features.html - https://pagelemon.com/templates/docket/pricing.html - https://pagelemon.com/templates/docket/security.html - https://pagelemon.com/templates/docket/about.html - https://pagelemon.com/templates/docket/404.html - https://pagelemon.com/templates/docket/privacy.html - https://pagelemon.com/templates/docket/styles.css - https://pagelemon.com/templates/docket/script.js - https://pagelemon.com/templates/docket/favicon.svg - https://pagelemon.com/templates/docket/og.png - https://pagelemon.com/templates/docket/apple-touch-icon.png - https://pagelemon.com/templates/docket/art/workspace.svg - https://pagelemon.com/templates/docket/art/team-mara.svg - https://pagelemon.com/templates/docket/art/team-tobiah.svg - https://pagelemon.com/templates/docket/art/team-isla.svg ## Notes for Docket (its `customise` rules) - Product name 'Docket' and company 'Docket Software Ltd' in , header, footer and JSON-LD - The hero clause, margin comment and stamp in #sheet on index.html (keep <del> for removed text and <ins> for added text) - Playbook rows in .rulebook and the before/after figures in .figure-list on index.html - The interactive clause and change list in [data-review] on features.html - Plan names, prices (data-month / data-year on .amt) and features on pricing.html - Hosting, retention and sub-processors on security.html - Team, story and contact details on about.html; address, phone and email in every footer - **Colours:** Edit the :root tokens at the top of styles.css. Keep --red for deletions and --blue for insertions only; they are the whole visual language. - **Fonts:** Change the Google Fonts <link> in each page and --sans / --serif in styles.css - **Sections:** Each section is self-contained with its own heading; delete or reorder freely. The hero animation is pure CSS (classes d1, i1, i2, d2 and the delays under .sheet.run); script.js only adds Replay and the clean-copy switch. - **Images:** Replace art/workspace.svg (product screenshot, 1600×1000, 16:10) and art/team-*.svg (portraits, 800×800 square) with real images; WebP under 300 KB ## 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, pricing per seat, data location and retention, customer names and quotes, team names and roles). 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? - Who is it for: legal teams, ops, founders, or all three? - How is it priced: per seat, per contract or flat, and what are the three plans? - Where is customer data hosted, and how long is it kept by default? - Which customers can be named, and may we quote one of them? - Who are the founders or key people, and what are their roles? 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: "docket"` (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.