# Lemma: a Page Lemon website template > A typeset-paper portfolio for a computer scientist: crisp white, a math serif, numbered theorems and figures, and a hero figure that steps through Dijkstra's algorithm. You are reading this because the user wants their own website made from the Lemma template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Lemma": 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: "lemma"` 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:** Typeset computer science paper: white page, STIX serif, numbered Theorem/Figure/Algorithm blocks, one link-blue and a highlighter yellow (light, calm, classic) - **Pages:** Home (`index.html`): Paper-style title block with abstract, interactive Dijkstra figure with Algorithm 1, selected theorems, recent papers, software table, two-column about with margin notes, news and upcoming talks; Research (`research.html`): Full publication list with topic and year filters, a dot-plot figure that follows the filter, PDF/preprint/code links and copyable BibTeX; Projects (`projects.html`): Four open-source projects with screenshot frames, facts, code listings and the release rules; Teaching & talks (`teaching.html`): Courses table, PhD group and an open position, upcoming and past talks with slides; CV (`cv.html`): Printable HTML CV with @media print styles: positions, education, awards and grants, selected papers, service, skills; Contact (`contact.html`): Contact form slot with mailto fallback, office details and hours, what to include in a PhD enquiry - **Fonts:** STIX Two Text, JetBrains Mono (Google Fonts) - **Colours:** `--paper` #ffffff, `--ink` #14161b, `--blue` #1b3db4, `--mark` #ffe37a, `--mute` #545a66 - **Live demo:** https://pagelemon.com/templates/lemma/ (people can preview it with the Page Lemon bar at https://pagelemon.com/tp/Lemma/preview) - **Manifest:** https://pagelemon.com/templates/lemma/template.json (machine-readable: files, customise, slots, facts, interview) ## How the visuals were made No raster art. Flat SVG figures in the style of a CS paper: white ground, ink lines, link-blue fills and one highlighter-yellow element per figure. Project frames are benchmark plots, heap and proof outlines, source-to-page panes and sorting bars; the portrait is a flat illustration at a chalkboard; the talk frame is a lecture hall with a graph slide. To sketch similar art: "Draw a flat SVG figure as if from a computer science paper: thin ink lines on white, nodes and bars filled in deep link blue (#1b3db4), one element highlighted in yellow (#ffe37a), serif italic labels, no gradients or shadows." ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "lemma"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/lemma/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/lemma/index.html - https://pagelemon.com/templates/lemma/research.html - https://pagelemon.com/templates/lemma/projects.html - https://pagelemon.com/templates/lemma/teaching.html - https://pagelemon.com/templates/lemma/cv.html - https://pagelemon.com/templates/lemma/contact.html - https://pagelemon.com/templates/lemma/privacy.html - https://pagelemon.com/templates/lemma/404.html - https://pagelemon.com/templates/lemma/styles.css - https://pagelemon.com/templates/lemma/script.js - https://pagelemon.com/templates/lemma/favicon.svg - https://pagelemon.com/templates/lemma/og.png - https://pagelemon.com/templates/lemma/apple-touch-icon.png - https://pagelemon.com/templates/lemma/art/kestrel.svg - https://pagelemon.com/templates/lemma/art/tallow.svg - https://pagelemon.com/templates/lemma/art/quire.svg - https://pagelemon.com/templates/lemma/art/stepwise.svg - https://pagelemon.com/templates/lemma/art/portrait.svg - https://pagelemon.com/templates/lemma/art/talk.svg ## Notes for Lemma (its `customise` rules) - Replace Ilse Brede in the wordmark, titles, metadata, footer, CV and JSON-LD; keep name, address and phone identical in the footer, contact page and JSON-LD. - Publications live in research.html as
  • entries: keep data-year and data-topics (space-separated ids matching the topic chips), the id p-, and the 
     that the copy button reads. Update the chip counts and the dot plot circles (one per paper, data-id = key) when papers change.
- Home: rewrite the three theorem boxes as real results with links to the matching paper anchors; the four recent papers repeat the top of research.html without BibTeX.
- Figure 1 is a working demo of Dijkstra's algorithm. Keep it for any algorithms or CS person; for another field, replace the SVG and Algorithm 1 with a static figure and remove the .fig-tools block.
- Replace projects, courses, students, talks (upcoming talks need future dates) and CV entries. Remove the open PhD position callout if there is none.
- Replace all data-pl-fill stats (stars, student numbers, grant amount) with real values or delete them.
- Confirm the privacy wording and the email retention period.
- **Colours:** Edit the :root tokens at the top of styles.css. Keep one link colour (--blue) and one highlighter (--mark); the paper look depends on everything else being ink on white.
- **Fonts:** STIX Two Text (400, 400 italic, 600) and JetBrains Mono (400): four files. Replace the Google Fonts link in every HTML head and --serif/--mono in styles.css; a math-style serif keeps the paper look.
- **Sections:** Every section is self-contained and numbered like a paper (1, 2, 3); renumber the .secno spans if you remove one. Keep the closing correspondence box and its CTA at the end of each page. Filters, BibTeX copy, the figure player and the CV print button are added by script.js and the page works without them.
- **Images:** Replace art/kestrel.svg, art/tallow.svg, art/quire.svg and art/stepwise.svg with project screenshots (landscape 16:10, 1600×1000), art/talk.svg with a talk photo (1600×1000) and art/portrait.svg with a portrait (4:5, 800×1000), WebP under 300 KB, keeping width, height and data-pl-photo. Figure 1 and Figure 4 are inline SVG drawn from the page's data.

## 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, job title and institution, office address, phone, email, office hours, publication list with authors, venues, years, topics and links, BibTeX for each publication, open-source projects with language, licence, stars and latest release, courses taught with terms and student numbers, students supervised and any open position, upcoming and past talks with dates and places, CV entries: positions, education, awards, grants, service, privacy retention period). If they can't answer one, remove that element rather than inventing it.
   - What is your name, job title and institution?
   - What do you research, in one sentence a non-specialist would follow?
   - Which papers should be listed, with authors, venue, year and topic (or a link to a BibTeX file)?
   - Which two or three results would you state as theorems on the home page?
   - Which software projects do you maintain, and where does the code live?
   - Which courses do you teach, and which talks are coming up?
   - Which email, phone and office address should people 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: "lemma"` (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.