Otto: independent designer website template

A playful designer's desk with notebook grids, oversized type, movable stickers and tactile project previews, split into a home page, work, case studies, services, about and contact.

Built from: Pages · Lists: forms

To use it, paste this into your AI chat:

Use template pagelemon.com/tp/Otto

Copy the prompt Preview (opens in a new tab)

Who it suits

Made for: independent designer, developer, creative, freelancer, illustrator, web developer, brand consultant, copywriter. In the gallery under Freelancer.

Its 7 pages

Home: Hero with movable desk stickers, selected work, a short about, services at a glance, a note from a client and the contact call to action
Work: Three recent projects as a list with thumbnails; links to each case study
Fold Supply case: Case study: the brief, what was done, the result and a client quote
Lilt Radio case: Case study: a community radio identity, schedule and programme archive
Services: Three services with starting prices, the four-step process and a planning note
About: The designer, a portrait, notes and the desk: record, reading and a working theory
Contact: Enquiry form slot with an email and phone fallback, the studio address and hours

Look: Notebook desk: graph paper, ink black, grass-green and bubblegum stickers, marker-underlined notes; light, bold, modern; fonts Schibsted Grotesk and Fragment Mono.

Ready for: a form that sends to your inbox, 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 designer's name and studio name, studio address, phone and email, working hours, starting prices for each service, client projects, results and quotes (only real ones) and availability line), 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 Otto template and published with Page Lemon (PageLemon.com). They may have pasted only "Use template pagelemon.com/tp/Otto": 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: "otto" 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: Notebook desk: graph paper, ink black, grass-green and bubblegum stickers, marker-underlined notes (light, bold, modern)
Pages: Home (index.html): Hero with movable desk stickers, selected work, a short about, services at a glance, a note from a client and the contact call to action; Work (work.html): Three recent projects as a list with thumbnails; links to each case study; Fold Supply case (case-fold.html): Case study: the brief, what was done, the result and a client quote; Lilt Radio case (case-lilt.html): Case study: a community radio identity, schedule and programme archive; Services (services.html): Three services with starting prices, the four-step process and a planning note; About (about.html): The designer, a portrait, notes and the desk: record, reading and a working theory; Contact (contact.html): Enquiry form slot with an email and phone fallback, the studio address and hours
Fonts: Schibsted Grotesk, Fragment Mono (Google Fonts)
Colours: --bg #F2F2EE, --ink #161616, --accent #00A86B
Live demo: https://pagelemon.com/templates/otto/ (people see it with the Page Lemon bar at https://pagelemon.com/tp/Otto; the page about it is https://pagelemon.com/tp/Otto/use)
Manifest: https://pagelemon.com/templates/otto/template.json (machine-readable: files, customise, slots, facts, interview)

How the visuals were made

Project images are free stock photos (Unsplash, see PHOTOS.md): art/fold.webp (canvas tote), art/fold-detail.webp (hands mending fabric), art/lilt.webp (broadcast microphone in a pink-lit studio) and art/common.webp (restaurant tables). The designer portrait (art/portrait.svg, a cartoon with a pink tape strip, kept so the named designer is not shown as a stranger) and the Lilt schedule screen (art/lilt-detail.svg, a UI mockup) stay flat SVG on graph-paper grounds with ink outlines. CSS and inline SVG add the draggable desk stickers, the spinning record, the orbit window and the marker-underlined section notes.

To sketch similar art: "Draw a flat playful SVG cartoon portrait of a designer on graph paper, with thick black outlines, bubblegum and grass fills and a slight offset shadow."

Files

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

Notes for Otto (its `customise` rules)

Business name 'Otto Bell' in every <title>, the header wordmark, the footer and the Person JSON-LD on index.html
Projects: work.html, case-fold.html and case-lilt.html (and the Supper Room entry on work.html); replace the names, sub-lines, facts and quotes, keep one project per row
Services and starting prices in services.html and the summary on index.html (data-pl-fill="price")
Address, phone and email, identical in the footer, contact.html and the JSON-LD (data-pl-fill="address", "phone", "email")
Delete any sample quote (data-pl-fill="review") unless the client gives a real one
Colours: Edit the :root tokens at the top of styles.css. Keep --grass-ink at 4.5:1 on --bg for green text and update the theme-color meta on every page.
Fonts: Change the Google Fonts link on every page and --font-display / --font-mono in styles.css. Current files: Schibsted Grotesk 400/600/800 and Fragment Mono 400.
Sections: Each page has its own <main> sections, so delete or reorder inside a page. The header nav and footer are the same on every page: change them together. The enquiry form is a slot (id enquiry); the designed form stays inert in its template until a form plugin is added.
Images: Replace the sample frames: portrait art/portrait.svg 430x410 (near-square, the designer), project images 1000x750 (4:3, art/fold.webp, art/lilt.webp, art/common.webp), case detail images 16:10 (art/fold-detail.webp, art/lilt-detail.svg). WebP under 300 KB. Keep each img.photo frame's width, height and data-pl-photo note. The pipeline generates og.png and apple-touch-icon.png.

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 (designer's name and studio name, studio address, phone and email, working hours, starting prices for each service, client projects, results and quotes (only real ones), availability line, social link). If they can't answer one, remove that element rather than inventing it.
- What is your name, and what should your studio be called?
- What do you make, and for whom: brands, websites, or both?
- What do your starting prices look like for each service?
- Which three to five projects are your strongest, and can you name the clients?
- Do you want people to email, call or use a form to get in touch?
- When are you free to take on work, and how do you want that shown?
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: "otto" (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.

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.