# Stacks: a Page Lemon website template > An app template: a paid community’s members’ library. Members sign in with their email, find vetted guides, templates and talks, save them to their shelf, log the quotes they send to see their real rates by size, and ask the organiser for a resource or an answer, following each request from Received to Answered with the organiser’s reply. £8 a month or £80 a year. A public page, six member screens under /app (Home, Library, three guides, Shelf, Ask, Account) and a privacy notice with blanks. You are reading this because the user wants their own website made from the Stacks template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Stacks": 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: "stacks"` 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:** Library stacks in deep green and brass, with resources filed as index cards (light, calm, classic) - **Pages:** Home (`index.html`): The public page: The Inkwell Guild for freelance illustrators, what is in the members’ library, how asking works, the price and the way in; Home (app) (`app/index.html`): The member’s home: new in the library, their shelf, their open request with its status, the members’ call and quick actions; Library (`app/library.html`): Every guide, template, tool and talk as covers, by kind, with what each is for; Guide: pricing (`app/guides/pricing.html`): G-01, pricing an editorial illustration, members only, with Save to my shelf; Guide: licensing (`app/guides/licensing.html`): G-02, the licensing checklist, members only, with Save to my shelf; Guide: late invoices (`app/guides/invoices.html`): G-03, chasing late invoices, members only, with Save to my shelf; Rates (`app/rates.html`): The member’s private quote log: each quote with size, use, fee and outcome, what they won this month, their average fee by size against the Guild floors, and the form to log a quote; Shelf (`app/shelf.html`): The resources the member saved, newest first, with their own note; Ask (`app/ask.html`): Ask the organiser for a resource or an answer, and every request with its status and the organiser’s reply; Account (`app/account.html`): The account block (email, devices, billing, leaving) and the monthly and yearly plans; Privacy (`privacy.html`): The privacy notice, with blanks the Site Owner fills in - **Fonts:** Libre Baskerville, Special Elite (Google Fonts) - **Live demo:** https://try-stacks.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Stacks in a browser land there). The template's own files: https://pagelemon.com/templates/stacks/; the page about it: https://pagelemon.com/tp/Stacks/use - **Manifest:** https://pagelemon.com/templates/stacks/template.json (machine-readable: files, customise, facts, interview) ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "stacks"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/stacks/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/stacks/index.html - https://pagelemon.com/templates/stacks/app/index.html - https://pagelemon.com/templates/stacks/app/library.html - https://pagelemon.com/templates/stacks/app/guides/pricing.html - https://pagelemon.com/templates/stacks/app/guides/licensing.html - https://pagelemon.com/templates/stacks/app/guides/invoices.html - https://pagelemon.com/templates/stacks/app/rates.html - https://pagelemon.com/templates/stacks/app/shelf.html - https://pagelemon.com/templates/stacks/app/ask.html - https://pagelemon.com/templates/stacks/app/account.html - https://pagelemon.com/templates/stacks/privacy.html - https://pagelemon.com/templates/stacks/styles.css - https://pagelemon.com/templates/stacks/app.js - https://pagelemon.com/templates/stacks/kit.css - https://pagelemon.com/templates/stacks/kit.js - https://pagelemon.com/templates/stacks/kit-icons.svg - https://pagelemon.com/templates/stacks/site.webmanifest - https://pagelemon.com/templates/stacks/favicon.svg - https://pagelemon.com/templates/stacks/art/cabinet.svg - https://pagelemon.com/templates/stacks/og.png - https://pagelemon.com/templates/stacks/apple-touch-icon.png - https://pagelemon.com/templates/stacks/icon-192.png - https://pagelemon.com/templates/stacks/icon-512.png - https://pagelemon.com/templates/stacks/icon-512-maskable.png ## Notes for Stacks (its `customise` rules) - The Inkwell Guild and Remi Achterberg in the header, footer, guides and titles: replace every data-pl-fill fact with the owner’s own; keep short_name in site.webmanifest as Inkwell or the owner’s app name. - Fill in every highlighted blank on privacy.html with the Site Owner before members use the site (not legal advice: https://pagelemon.com/agents/member-app-legal) - setup_app with signup open, then save_app_list for saved and requests exactly as memberApp.lists says (requests with its status_options and reply on). The saved list’s resource options are the library’s titles: when the owner adds or renames a resource, change the options, the library card, the guide’s Save form and the TITLES map in app.js together. - The quotes list (Rates) is private to each member: make it with save_app_list exactly as memberApp.lists says. Keep the job options in step with the size table in app/guides/pricing.html. Outcome changes (Won, Lost, Waiting) use update_app_rows on the existing row, never a new row. - Set the plans with save_plan: member (£8 a month) and annual (£80 a year). Guides are wrapped in data-pl-if="plan:member" and "plan:annual" so only paying members read them; change the prices on index.html and app/account.html together. - The organiser answers in the Dashboard (Apps → Requests): set the status (Received, Researching, Added to library, Answered) and write a reply members read under their request. - A professional library only: never add health, payment card, bank or ID fields, and never collect anything about children. - **Colours:** Edit the palette tokens in the body.k-app[data-k-type="slab"] blocks at the end of styles.css (light, then dark). - **Fonts:** Libre Baskerville and Special Elite, loaded from Google Fonts on every page; your AI can self-host them on request. - **Sections:** Member pages live under /app on the shared app kit (kit.css, kit.js, kit-icons.svg; never edit the copies). app/guides/*.html are full guides behind the plans, each with a Save form for the saved list; app/shelf.html lists saved rows (app.js turns a saved title into a link to its guide); app/ask.html holds the requests add form and the member’s requests with status and reply; app/account.html the account block and join buttons. index.html holds no member blocks. - **Images:** art/cabinet.svg is the drawn oak card catalogue on the public page and the members’ welcome screens. Library resources are index cards drawn in styles.css, with no cover art: add a resource as one card, with its reference code. ## Set up the app This is an app template: the home page and privacy notice are public, and the pages under `/app` are for signed-in users, each seeing only their own entries and the entries the Site Owner assigns to them. Users sign in with a code sent to their email. The full guide is https://pagelemon.com/agents/member-app; read it before you set this up, and its legal notes at https://pagelemon.com/agents/member-app-legal. - **Needs:** a kept site on App or above, and the Site Owner signed in to Page Lemon with two-step sign-in (they turn the app on themselves, at the approve link `setup_app` returns). - **Never:** health, mood or therapy records, accounts for children, or fields for card, bank or ID numbers (Acceptable Use: https://pagelemon.com/acceptable-use#member-app). Users pay through Stripe. - **Then:** `setup_app` with these settings, the join questions and note in the user's own words, then `save_app_list` once for each list below, exactly as written, so the field names match the pages. ```json {"site":"","signup":"open","profile_fields":[{"name":"name","type":"text","label":"First name"}],"display_field":"name","path":"/app"} ``` - **Shelf** (`saved`): users add these rows themselves on the pages. ```json {"site":"","list":"saved","label":"Shelf","fields":[{"name":"resource","type":"choice","label":"Resource","required":true,"options":["Pricing an editorial illustration","The licensing checklist","Chasing late invoices","Quote and licence template","Usage fee calculator","Book contracts, an hour with an agent"]},{"name":"memo","type":"text","label":"Why you saved it"}]} ``` - **Requests** (`requests`): users add these rows themselves on the pages. ```json {"site":"","list":"requests","label":"Requests","fields":[{"name":"title","type":"text","label":"What do you need?","required":true},{"name":"kind","type":"choice","label":"Kind","required":true,"options":["Guide","Template","Tool","Talk or video","An answer to a question"]},{"name":"details","type":"long_text","label":"Details"}],"status_options":["Received","Researching","Added to library","Answered"],"reply":true} ``` - **Rates** (`quotes`): users add these rows themselves on the pages. ```json {"site":"","list":"quotes","label":"Rates","fields":[{"name":"client","type":"text","label":"Client","required":true},{"name":"job","type":"choice","label":"Size or job","required":true,"options":["Spot","Half page","Full page","Double-page spread","Cover","Book jacket","Packaging","Other"]},{"name":"usage","type":"choice","label":"Use","required":true,"options":["Print and online","Online only","Book","Advertising"]},{"name":"fee","type":"number","label":"Fee (£)","required":true},{"name":"sent","type":"date","label":"Sent on","required":true},{"name":"outcome","type":"choice","label":"Outcome","required":true,"options":["Waiting","Won","Lost"]},{"name":"memo","type":"text","label":"Note"}]} ``` - **Plans** (`save_plan`; the pages use `data-pl-if="plan:"` and join buttons): `member` "Monthly membership" (paid, sample price 8.00 GBP a month; ask the user for theirs); `annual` "Yearly membership" (paid, sample price 80.00 GBP a year; ask the user for theirs). Paid plans need Starter or Scale and the Site Owner's Stripe account connected; `save_plan` returns the onboarding link if it isn't. ## 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 (community name, organiser’s name, contact email, monthly and yearly price, members’ call day and time, the library’s guides, templates, tools and talks). If they can't answer one, remove that element rather than inventing it. - What is the community called, and who is it for? - Who runs it, and what email should members write to? - What does membership cost each month, and what do members get for it? - When is the next members' call or meet-up, if you hold one? - Which guides, templates and talks should be in the library first, and which deserve a full page? - What should your first two or three posts to members say? 2. **Get the files.** If you have the Page Lemon tool (the MCP connector with a `deploy` tool; https://pagelemon.com/docs/connect sets it up), call `deploy` with `template: "stacks"` (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.** The sample town, street and people's names also appear in ordinary sentences, `aria-label`s and image `alt` text: replace them there too. 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. Delete each whole review, with its name or caption, and the section and its nav link when none is left. 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, `geo` coordinates (delete them unless you have the real ones), hours, phone, `url`). - Photos: this template is drawn art, not photos. If the user wants their own photos, add them where they fit (compressed, WebP or JPEG under about 300 KB, real `alt`). Ask for photos; never hot-link. - Make a new `og.png` (1200×630) of the new home page if you can, with its `og:image` tags; otherwise delete the sample one and its `og:image` tags (a template deploy has already left both out). 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 Site 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 and Booking: any paid plan; staff and rooms only on some, and each plan has a limit of online bookings a day), set the form up as a list (`save_list`) or the service (`save_service`), put the matching markup 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`, the template's fictional business name and its sample phone, email and street, in links too (`tel:` and `mailto:` hrefs, and map links, where the street is written like `18+Linden+Walk`): 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. 7. **Turn on the app** as "Set up the app" above says: `setup_app`, then `save_app_list` for each list, `save_plan` for each plan, the approve link to the Site Owner, `invite_users`, a test with `preview_as_user` and `get_app` with `check: true` before you say it's ready. ## 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. (at most 100 files and 1 MB in all, `index.html` at the root): ```bash node -e 'const fs=require("fs"),p=require("path"),d=process.argv[1],files=[];(function w(x){for(const e of fs.readdirSync(x,{withFileTypes:true})){const f=p.join(x,e.name);e.isDirectory()?w(f):files.push({path:p.relative(d,f).split(p.sep).join("/"),content_base64:fs.readFileSync(f).toString("base64")})}})(d);console.log(JSON.stringify({files}))' <dir> \ | curl -sS --fail-with-body -H "Content-Type: application/json" --data-binary @- https://api.pagelemon.com/v2/anonymous-sites ``` If the user gave you an API key (`plak_…`) or `~/.config/pagelemon/credentials` exists, publish into their account instead (see "Updating a site" in https://pagelemon.com/agents). 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/mcp`): call its `publish_site` tool with every file. See "No shell: the MCP connector" in https://pagelemon.com/agents. 3. **Neither (a chat app without the Page Lemon connector):** say once that they can connect Page Lemon to this AI app (steps at https://pagelemon.com/docs/connect) so you can publish and change the site for them. In the Gemini app or Grok (free plan included) it takes about a minute: Gemini at gemini.google.com/customize/connectors (**Custom**), Grok at grok.com/connectors (**New Connector**, **Custom**), with the link `https://mcp.pagelemon.com/mcp`; then they sign in and click **Allow**. Give those steps in plain words. If they can't or would rather not (for example ChatGPT's free plan), don't ask them to save or upload files. Put the whole site in ONE complete page: CSS and JavaScript inline, images as https links or small data URIs, from `<!DOCTYPE html>` to `</html>`. Show it as one code block, then tell them: "Tap Copy on the code, open pagelemon.com/publish, tap Paste and publish." Only if you can really give them a downloadable .zip (a file they tap to download, not code to save): "Download this zip, open pagelemon.com/publish, tap Drop or choose a file." They get a live link with no account, online for 72 hours unless they tap **Keep it free**. 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.