Page Lemon
English
Start free

Lineup

A music festival site styled as a gig poster: acid green on black, overprinted condensed type, rotating sticker badges and a scrolling artist ticker.

To use it, paste this into your AI chat:

Use template pagelemon.com/tp/Lineup
Copy the prompt Preview (opens in a new tab)

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 Lineup template and published with Page Lemon (pagelemon.com). They may have pasted only "Use template pagelemon.com/tp/Lineup": 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: "lineup" 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

How the visuals were made

Poster-style SVG art in flat acid green, hot magenta and off-white on black, with halftone dots and wave lines. Placeholders for performer, stage, crew and site map photos. The hero is type-led, with CSS halftone dots and a rotating SVG sticker.

To sketch similar art: "Draw a flat SVG gig poster illustration: a black background, a spotlit singer silhouette in acid green, a magenta disc, halftone dots and thick wave lines."

Files

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

Notes for Lineup (its customise rules)

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, address, phone, email, hours, dates, artist names and set times, stage names, ticket prices and passes, ticket link, early bird date, sponsor names, sample review, social URL, shuttle and station details). If they can't answer one, remove that element rather than inventing it.
    • What is the festival called and what are its dates?
    • Where is it held, and what is the postcode and nearest station?
    • Which acts are playing, and on which stage and day?
    • How many stages are there, and what are they called?
    • What do the day and weekend tickets cost, and when does early bird end?
    • Which link should the tickets buttons open?
    • Who should volunteer and press emails go to?
  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: "lineup" (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 <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, 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:

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.