Desk: Membership & community website template

An app template for a coworking space: members check in at the door by showing a code the host scans, see their desk days this month, ask for a meeting room the host confirms, send front-desk requests (guest passes, parcels, lockers) and pick a plan. A public page with the day pass, six member screens under /app and a privacy notice with blanks.

Built from: Pages · Lists · Sign-in: users · Actions: pay, scan

To use it, paste this into your AI chat:

Use template pagelemon.com/tp/Desk

Copy the prompt Preview (opens in a new tab)

Who it suits

Made for: coworking spaces and hot-desk clubs, shared offices with meeting rooms, flexible workspaces run by a host, shared office, hot desk rental, meeting room hire, flexible office, members' lounge, day pass sales. In the gallery under Membership & community.

Its 8 pages

Home: The public page: the floor, the three plans with prices, the £18 day pass (payment slot), the two meeting rooms, how check-in works and the join link
Home (app): Signed out: the welcome and join. Signed in: the membership card with desk days this month against the plan, Show my pass, the next room booking with its status, the open front-desk request and quick actions
Pass: The member's code the host scans at the door (one check-in a day), wallet buttons where on, opening hours, wifi and house rules
Rooms: The Snug and The Long Room with photos and what's in them, the room request form (date, start, length, purpose, guests) and the member's bookings with the host's confirmation
Front desk: Guest passes, parcels, lockers, printing and faults: the request form and the member's requests with status and the host's reply
Plan: The member's plan and what it includes, the three plans with join buttons, and how renewal and cancelling work
Account: The account block (email, profile, plan, billing, devices, leaving)
Privacy: The privacy notice, with highlighted blanks the owner fills in

Look: Printworks ink black and paper, magenta and cyan accents from letterpress, real photos of the floor and both rooms, a membership card with a days-this-month meter; light, bold, modern; fonts Syne and Azeret Mono.

Ready for: payments, once you ask your AI to turn it on.

What you can change

Everything, by asking your AI: the name, words, photos, colours, fonts and pages. Your AI first asks you a few questions (such as your space name, address, phone, email, host name and what the host does and opening hours), then replaces every piece of sample text with your own details. Later you can add a contact form, bookings or a password by asking again.

The rest of this page is for your AI: it says what the template is, where its files are, and how to build your site from it and publish it.

You are reading this because the user wants their own website made from the Desk template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Desk": 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: "desk" 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: Printworks ink black and paper, magenta and cyan accents from letterpress, real photos of the floor and both rooms, a membership card with a days-this-month meter (light, bold, modern)
Pages: Home (index.html): The public page: the floor, the three plans with prices, the £18 day pass (payment slot), the two meeting rooms, how check-in works and the join link; Home (app) (app/index.html): Signed out: the welcome and join. Signed in: the membership card with desk days this month against the plan, Show my pass, the next room booking with its status, the open front-desk request and quick actions; Pass (app/pass.html): The member's code the host scans at the door (one check-in a day), wallet buttons where on, opening hours, wifi and house rules; Rooms (app/rooms.html): The Snug and The Long Room with photos and what's in them, the room request form (date, start, length, purpose, guests) and the member's bookings with the host's confirmation; Front desk (app/requests.html): Guest passes, parcels, lockers, printing and faults: the request form and the member's requests with status and the host's reply; Plan (app/plan.html): The member's plan and what it includes, the three plans with join buttons, and how renewal and cancelling work; Account (app/account.html): The account block (email, profile, plan, billing, devices, leaving); Privacy (privacy.html): The privacy notice, with highlighted blanks the owner fills in
Fonts: Syne, Azeret Mono (Google Fonts)
Live demo: https://try-desk.pagelemon.dev/ (a working copy with sample data; people opening https://pagelemon.com/tp/Desk in a browser land there). The template's own files: https://pagelemon.com/templates/desk/; the page about it: https://pagelemon.com/tp/Desk/use
Manifest: https://pagelemon.com/templates/desk/template.json (machine-readable: files, customise, slots, facts, interview)

Files

With the Page Lemon connector you don't need to fetch these: deploy with template: "desk" copies them all (step 2). Otherwise fetch each file from https://pagelemon.com/templates/desk/ and save it with the same relative path (including art/). Fetch nothing else: templates have no external images or scripts.

Notes for Desk (its `customise` rules)

The Printworks Desk Club, its address (2nd floor, 11 Compositor Street, Inkermouth QS2 8RL), phone and email in the header, footer, titles and copy; replace every data-pl-fill fact with the owner's own. Also replace site.webmanifest name with the owner's app name and keep short_name short.
Fill in every highlighted blank on privacy.html with the Site Owner before members or visitors use the site (not legal advice: https://pagelemon.com/agents/member-app-legal)
The host checks the Flex allowance of 8 desk days a month at the door: the days-this-month count on app/index.html and app/pass.html counts check-ins this calendar month; no goal is set on the scan action.
Staff scan with their phone's camera: each is a Page Lemon collaborator. Invite them with add_people, role collaborator and permissions ["scan"] so they can scan codes but not change the site or see the member list.
Room requests are confirmed by the host in the Dashboard (Apps, Entries: Confirmed or Declined, with a reply); the pages never promise live availability. Rooms, prices (£15 and £35 an hour for non-members; Resident includes 6 room hours a month) are on index.html, app/rooms.html and app/plan.html.
Never add health, payment card, bank or ID fields, and never collect anything about children.
Colours: Edit the --k-brand, --k-hero and --k-gold tokens at the top of styles.css (light and dark); the kit (kit.css) does the rest
Fonts: Google Fonts: Syne (the wide headlines, member name and numbers) and Azeret Mono (text and labels), one <link> in every page head and --k-font-display / --k-font in styles.css. If the owner prefers no font service, download both (OFL) into a fonts/ folder and switch to @font-face.
Sections: Public page: index.html (space, plans, day pass slot, rooms, check-in). Member pages under /app use the data-pl-view markup. setup_app with memberApp.setup (open signup, name and company), save_plan for visitor (free), flex and resident (paid), then save_app_list for checkins with the scan action in memberApp.scan, bookings and requests (status_options and reply on both). The owner's path: the host scans each member's code at the door (Dashboard scan page: confirm, Undo for 10 seconds), sees Today's check-ins and Members, and answers room requests and front-desk requests in Apps, Entries by setting the status and writing a reply the member sees at once. app/index.html Home, app/pass.html the code, app/rooms.html rooms, app/requests.html the front desk, app/plan.html plans, app/account.html the account block. app.js fills the days-this-month meter.
Images: art/print-hall.webp, art/hot-desks.webp, art/the-snug.webp and art/the-long-room.webp are free stock photos from Unsplash and Pexels (PHOTOS.md): replace them with photos of your own floor and rooms, no faces. favicon.svg is the misregistered P mark; the PNG icons and manifest are made from it.

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.

{"site":"<site>","signup":"open","profile_fields":[{"name":"name","type":"text","label":"Your name","required":true},{"name":"company","type":"text","label":"Company or project"}],"display_field":"name","path":"/app"}

Day check-ins (checkins): the Site Owner adds these rows in the Page Lemon Dashboard (Apps tab) and assigns each to one user, who only reads it.
```
{"site":"<site>","list":"checkins","label":"Day check-ins","fields":[{"name":"visit","type":"text","label":"Visit","required":true}]}
```

Meeting room requests (bookings): users add these rows themselves on the pages.

{"site":"<site>","list":"bookings","label":"Meeting room requests","fields":[{"name":"room","type":"choice","label":"Room","required":true,"options":["The Snug","The Long Room"]},{"name":"date","type":"date","label":"Date","required":true},{"name":"start","type":"choice","label":"Start","required":true,"options":["09:00","10:00","11:00","12:00","13:00","14:00","15:00","16:00"]},{"name":"length","type":"choice","label":"How long","required":true,"options":["1 hour","2 hours","Half day (4 hours)"]},{"name":"purpose","type":"text","label":"What it's for","required":true},{"name":"guests","type":"number","label":"Guests from outside"}],"status_options":["Requested","Confirmed","Declined"],"reply":true}

Requests to the front desk (requests): users add these rows themselves on the pages.

{"site":"<site>","list":"requests","label":"Requests to the front desk","fields":[{"name":"kind","type":"choice","label":"What is it about?","required":true,"options":["Guest pass","Post and parcels","Locker","Printing","Something's broken","Change my plan","Cancel or move a room"]},{"name":"date","type":"date","label":"Date","required":true},{"name":"details","type":"long_text","label":"Details","required":true}],"status_options":["Received","In hand","Done"],"reply":true}

Plans (save_plan; the pages use data-pl-if="plan:<id>" and join buttons): visitor "Visitor" (free); flex "Flex" (paid, sample price 95.00 GBP a month; ask the user for theirs); resident "Resident" (paid, sample price 210.00 GBP a month; 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

Interview first. Ask the user these questions, a few at a time, in plain words, and collect every fact the site needs (space name, address, phone, email, host name and what the host does, opening hours, number of desks, rooms and booths, day pass price, plan prices and what each plan includes, room names, capacity and hourly prices, privacy contact and legal company name). If they can't answer one, remove that element rather than inventing it.
- What is the coworking space called, and where is it?
- How many desks and meeting rooms do you have, and what are they called?
- What do a day pass and each membership cost, and what does each include?
- What are your opening hours, and do residents get 24/7 access?
- Who runs the front desk and scans members' codes? Each needs a Page Lemon sign-in: invite them as collaborators with only Scan members ticked.
- Which email address and phone number should members and visitors use?
- What legal company name and privacy contact should the privacy notice show?
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: "desk" (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.
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-labels 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 <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, geo coordinates (delete them unless you have the real ones), 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.
- 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  comment.
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.
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).
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.
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:

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):
```
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.
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.
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.