# Ticket: a Page Lemon website template > An app template for a one-person IT support business: client offices sign in, pick the area and raise a ticket with a screenshot, follow each one through New, Looking into it, Waiting on you, Visit booked and Fixed with the owner's reply, read every update in a thread and see booked visits. The owner answers each ticket with one status tap and a reply. A public page, six member pages under /app and a privacy notice with blanks. You are reading this because the user wants their own website made from the Ticket template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Ticket": 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: "ticket"` 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:** Dark server rack: mono asset labels, LEDs that step green per ticket stage and terminal logs (light, calm, modern) - **Pages:** Home (`index.html`): The public page: what the support covers, how a ticket works in three steps, a sample screenshot, the owner and the client sign-in; Home (`app/index.html`): The client's home: open tickets by stage, the next visit, Raise a ticket, the urgent phone line, the latest tickets and Ossie's latest updates; a welcome screen when signed out; Tickets (`app/tickets.html`): Every ticket newest first with its area, stage timeline, screenshot and the owner's reply, Same problem again, and what the stages mean; Ticket (`app/ticket.html`): One ticket (opened from any ticket card): its stage, details, screenshot and Ossie's reply, his updates on it, your answers, a reply box and It's working again or Still broken; New (`app/new.html`): The ticket form with area tiles, urgency, details and a screenshot, and quick checks per area; Updates (`app/updates.html`): Reply to Ossie (an answer on a ticket), your answers, and every update Ossie posted (date, ticket, stage, note, visit date and time) as a thread; Visits (`app/visits.html`): Booked on-site visits from the updates' visit dates, and what to expect; Account (`app/account.html`): The client's first name, the account block (sign-in, devices, leaving) and contacts; Privacy (`privacy.html`): The privacy notice, with blanks the owner fills in - **Fonts:** JetBrains Mono, Inter (Google Fonts) - **Live demo:** https://try-ticket.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Ticket in a browser land there). The template's own files: https://pagelemon.com/templates/ticket/; the page about it: https://pagelemon.com/tp/Ticket/use - **Manifest:** https://pagelemon.com/templates/ticket/template.json (machine-readable: files, customise, facts, interview) ## Files With the Page Lemon connector you don't need to fetch these: `deploy` with `template: "ticket"` copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/ticket/ and save it with the same relative path (including `art/`). Fetch nothing else: templates have no external images or scripts. - https://pagelemon.com/templates/ticket/index.html - https://pagelemon.com/templates/ticket/privacy.html - https://pagelemon.com/templates/ticket/app/index.html - https://pagelemon.com/templates/ticket/app/tickets.html - https://pagelemon.com/templates/ticket/app/ticket.html - https://pagelemon.com/templates/ticket/app/new.html - https://pagelemon.com/templates/ticket/app/updates.html - https://pagelemon.com/templates/ticket/app/visits.html - https://pagelemon.com/templates/ticket/app/account.html - https://pagelemon.com/templates/ticket/styles.css - https://pagelemon.com/templates/ticket/app.js - https://pagelemon.com/templates/ticket/kit.css - https://pagelemon.com/templates/ticket/kit.js - https://pagelemon.com/templates/ticket/kit-icons.svg - https://pagelemon.com/templates/ticket/icons.svg - https://pagelemon.com/templates/ticket/site.webmanifest - https://pagelemon.com/templates/ticket/favicon.svg - https://pagelemon.com/templates/ticket/art/router.svg - https://pagelemon.com/templates/ticket/art/printer-offline.svg - https://pagelemon.com/templates/ticket/art/printer.svg - https://pagelemon.com/templates/ticket/og.png - https://pagelemon.com/templates/ticket/apple-touch-icon.png - https://pagelemon.com/templates/ticket/icon-192.png - https://pagelemon.com/templates/ticket/icon-512.png - https://pagelemon.com/templates/ticket/icon-512-maskable.png ## Notes for Ticket (its `customise` rules) - Stoneygate IT, Ossie Brandt, Larchway Lettings (the sample client office), the phone, email and £95 a month: replace them on every page and in site.webmanifest. - Fill in every highlighted blank on privacy.html before clients sign in (not legal advice: https://pagelemon.com/agents/member-app-legal). - setup_app with signup invite, the profile field name (First name) and display_field name; invite_users with each client's work email. - Make the tickets list exactly as memberApp.lists says, with status_options New, Looking into it, Waiting on you, Visit booked, Fixed and Closed (Fixed tickets close after 7 days unless the client says Still broken; a ticket Waiting on you closes after 14 days without an answer) and reply on. The owner sets the stage with one tap and writes a short reply in the Dashboard (Apps, Entries); the client sees both on Home and Tickets, with the stage timeline. - Make the updates list (by owner) exactly as memberApp.lists says: one row per update, assigned to the client, with the ticket's subject, stage, note and an optional visit date. Visits shows the rows with a visit date from today. - Make the messages list (by member) exactly as memberApp.lists says: a client answers Ossie's question on a ticket from app/updates.html (the Reply to Ossie button on a Waiting on you ticket fills in the subject). Read them in the Dashboard (Apps, Entries). - Change the areas together: the area options in the list, the select and the tiles on app/new.html, and the quick checks there. - Never ask for passwords, PINs or sign-in codes, and never collect card, bank, ID or health details. Screenshots should be cropped of personal details. - **Colours:** Edit the :root tokens at the top of styles.css: the --t-* rack colours (dark in both schemes) and the room colours, which follow the device (aluminium in light, terminal in dark). - **Fonts:** JetBrains Mono (display, ticket labels, LED labels, dates) with Inter (text), from Google Fonts by one in every page head; ask to self-host them if you prefer no font service. - **Sections:** Public: index.html and privacy.html. Member pages under /app on the shared app kit (kit.css, kit.js, kit-icons.svg; never edit them): index.html (home: the rack, one unit per open ticket with its asset label and five status LEDs, totals per stage on the rack display), tickets.html, ticket.html (one ticket: app.js shows the ticket named in ?subject= with its updates and answers), new.html (the add form as a blank asset label; the area tiles are patch-panel ports, kit product cards that pick the area), updates.html (the updates list as a thread), visits.html (updates with a visit date), account.html (the account block). Tabs: Home, Tickets, New, Updates, Visits. Template pieces are the t-* classes in styles.css (t-rack, t-unit, t-label, t-panel and its LEDs, t-log, t-svc); the LEDs follow the status through data-k-status on .t-panel and the area code through data-k-status-field="area" on .t-tag. - **Images:** art/router.svg (900×900) is the line drawing of a printer and router on the signed-out screens; art/printer-offline.svg (800×500) is a sample error screenshot on the sample ticket and the public page. Both are drawn SVG; replace the router drawing with a photo of the owner at work if they have one. icons.svg holds the extra icons (printer, wifi, laptop, key). ## 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":"invite","profile_fields":[{"name":"name","type":"text","label":"First name"}],"display_field":"name","path":"/app"} ``` - **Tickets** (`tickets`): users add these rows themselves on the pages. ```json {"site":"","list":"tickets","label":"Tickets","fields":[{"name":"subject","type":"text","label":"What's wrong?","required":true},{"name":"area","type":"choice","label":"Area","required":true,"options":["Printer","Wi-Fi","Email","Laptop or PC","Phone","Sign-in problems","Other"]},{"name":"urgency","type":"choice","label":"How urgent?","required":true,"options":["When you can","This week","Today","Stopping work"]},{"name":"details","type":"long_text","label":"Details","required":true},{"name":"screenshot","type":"photo","label":"Screenshot or photo of the screen"}],"status_options":["New","Looking into it","Waiting on you","Visit booked","Fixed","Closed"],"reply":true} ``` - **Ticket updates** (`updates`): the Site Owner adds these rows in the Page Lemon Dashboard (Apps tab) and assigns each to one user, who only reads it. ```json {"site":"","list":"updates","label":"Ticket updates","fields":[{"name":"date","type":"date","label":"Date","required":true},{"name":"ticket","type":"text","label":"Ticket","required":true},{"name":"stage","type":"choice","label":"Stage","required":true,"options":["New","Looking into it","Waiting on you","Visit booked","Fixed","Closed"]},{"name":"memo","type":"long_text","label":"Note"},{"name":"visit","type":"date","label":"Visit booked for"},{"name":"visit_time","type":"choice","label":"Visit time","options":["09:00 to 10:00","11:00 to 12:00","14:00 to 15:00","16:00 to 17:00"]}]} ``` - **Answers to Ossie** (`messages`): users add these rows themselves on the pages. ```json {"site":"","list":"messages","label":"Answers to Ossie","fields":[{"name":"subject","type":"text","label":"Ticket","required":true},{"name":"message","type":"long_text","label":"Your answer","required":true}]} ``` ## 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 (business name, who answers the tickets, contact email, phone number for urgent problems, reply time for a new ticket, privacy contact and address). If they can't answer one, remove that element rather than inventing it. - What is your IT support business called, and who answers the tickets? - Which offices or businesses do you look after, and roughly how many people in each? - What do clients usually ask you about (email, laptops, printers, Wi-Fi, phones)? - How quickly do you reply to a new ticket, and how fast for one marked Stopped working? - Which email address and phone number should clients use when something is urgent? - What address and privacy contact should the privacy notice show? 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: "ticket"` (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, 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.