# MUST OBEY — Mobile-first build requirements

This app's PRIMARY surface is a mobile phone. Build it impeccably on mobile FIRST, then verify on tablet and desktop. Treat the rules below as non-negotiable hard constraints, not suggestions.

## Viewports to verify (every screen, every state)
- 320 px, 360 px, 375 px, 390 px, 414 px, 480 px
- 768 px, 834 px (iPad portrait / Pro 11)
- 1024 px, 1280 px, 1440 px, 1920 px, 2560 px
- Plus: 200% browser zoom, landscape orientation on every mobile width, iPhone with safe-area insets visible

## Hard layout rules
- Mobile-first CSS. Default styles target mobile; `@media (min-width: ...)` for larger viewports.
- Use `dvh` and `svh` instead of `vh` for full-height surfaces (iOS Safari URL-bar bug).
- Use `clamp()` for fluid typography across all viewports.
- Prefer container queries (`@container`) over media queries for component-level responsiveness.
- Use `min(100%, ...)` widths so content never overflows. Zero horizontal overflow at any viewport.
- Add `<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">` to every page.
- Apply `padding: max(safe-area-inset-X, fallback)` on every edge-bleeding container so notched iPhones in landscape never clip content.
- Wide tables and code blocks scroll INSIDE their container (`overflow-x: auto`), never push the body.
- Use `background-attachment: scroll` on mobile, not `fixed` (iOS Safari repaint bug).
- Avoid `backdrop-filter` on animated elements. Use it sparingly on static surfaces only.
- **Canvas Scaling**: Canvases must dynamically scale with window resize events and properly handle high-DPI screens (`window.devicePixelRatio`). Set physical dimensions (`canvas.width`/`canvas.height`) using pixel ratio and render relative to this grid, using CSS to control responsive viewport scaling.
- **Robust Storage**: Every access to `localStorage`/`sessionStorage` (especially `JSON.parse` of loaded state or writes) MUST be wrapped in a `try-catch` block to handle disabled storage, private browsing mode, quota limits, or corrupted JSON gracefully. Fall back to a robust in-memory object store.

## Touch & accessibility
- Tap targets ≥ 44 × 44 px on touch (Apple HIG). Increase to 48 px under `@media (hover: none) and (pointer: coarse)`.
- All interactive controls reachable by keyboard with a visible focus ring; respect `:focus-visible`.
- Color contrast ≥ 4.5:1 for body text, 3:1 for UI components.
- All images have meaningful `alt`. Decorative images use `alt=""`.
- Respect `prefers-reduced-motion: reduce` — zero animation durations under that query.
- Forms validate inline; error messages are specific, not "Invalid input".
- Modals: focus trap, `Esc` closes, `role="dialog"`, `aria-modal="true"`, focus restored on close.

## Performance bar (Lighthouse mobile, throttled 3G/4G)
- LCP < 2.5 s · INP < 200 ms · CLS < 0.1
- JS bundle gzip < 200 KB mobile-first; lazy-load non-critical screens via `React.lazy` / dynamic imports.
- No render-blocking resources above the fold.
- Images: WebP/AVIF preferred, `loading="lazy"`, explicit `width`/`height` attributes (zero CLS), `srcset` for retina.
- Videos: `preload="metadata"`, low-resolution poster, max 720p mobile fallback. Never autoplay with audio.
- Fonts: `font-display: swap`; preload only the one used above the fold.
- Smooth scroll honoured via CSS `scroll-behavior: smooth` with reduced-motion fallback.

## Pre-ship mobile checklist (the deployer MUST verify before declaring done)
1. Open at 375 px in DevTools — every screen scrolls vertically only; zero horizontal scroll.
2. Browser zoom 200% — layout reflows without overlap.
3. iPhone Safari with the URL bar visible AND landscape — no content under the home indicator; no notch clipping.
4. iPad portrait (768 px) and landscape (1024 px) — no awkward gaps; tablet-specific breakpoints land cleanly.
5. Tap every interactive element with a thumb at real-device size — every target is easy to hit.
6. `prefers-reduced-motion: reduce` — every transition / animation skips cleanly, scroll-behavior becomes instant.
7. Lighthouse mobile score ≥ 90 across all 4 categories.
8. Zero `console.error` and zero CLS shift in real-device testing on a mid-tier Android (e.g. Pixel 6a) and an iPhone SE.

---

The original template starts below. All rules above apply on TOP of whatever this template specifies.

---

# Build Prompt — Event Platform

Paste this into Google AI Studio's **Build** function. It is self-contained — every section below is part of the instructions.

_Source reference: https://lovable.dev/templates/websites/events/event-platform-1_

---

## 1. Project
Build a **Events** named **Event Platform**.
One-line description: _Launch a professional event platform with registration, maps, and real-time countdowns. Complete event management and discovery—go live in hours, not weeks._

**What it is:**
This template gives you a professional event platform that works without technical setup. Registration forms, event listings, and mobile-ready layouts are already built. You focus on organizing events and getting people in the room—the infrastructure is handled.

## 2. Target audience
- Event organizers running conferences, workshops, or community gatherings
- Community builders hosting recurring meetups
- Conference teams needing registration and attendee management
- Workshop facilitators selling tickets and managing enrollments
- Corporate teams running internal events or training sessions
- Creators hosting webinars or virtual sessions

## 3. Core value propositions
Surface these clearly through copy, visual emphasis, and section ordering — they are the reasons users pick this product.

- **Launch Events in Hours** — Complete event platform with registration, maps, and real-time countdowns—ready immediately, no coding required
- **Professional Event Discovery Experience** — Auto-scrolling carousels, geolocation filtering, and responsive grids that make every event look premium
- **Real-Time Engagement Features** — Live countdown timers, instant registration updates, and dynamic event status badges keep attendees engaged
- **Google Maps Integration Built-In** — Location autocomplete, embedded maps, and directions links—professional navigation without complex technical setup
- **Enterprise-Grade Security Ready** — Row-level security, role-based access control, and secure authentication protect your events and user data

## 4. Features to build
**Product features:**
Production-ready features built with modern tech stack for exceptional performance and user experience

- One-Click Event Creation
- Dynamic Countdown Timers
- Smart Event Discovery
- Instant Registration System
- Auto-Scrolling Event Carousel
- Full-Screen Event Pages
- Role-Based Admin Dashboard
- Creator Event Management
- Mobile-Optimized Responsive Design
- Supabase Real-Time Backend
- SEO-Optimized Event Pages
- Professional Typography System

## 4b. Required services & integrations
List the back-end services this template needs to function. If a service is not needed, say so explicitly — silence is ambiguous.

- **Auth — Optional.** Account-less ticket purchase by email is the default; full accounts only for ticket-holder dashboards.
- **Database — Required.** Events, ticket types, attendees, RSVPs, dietary/accessibility notes.
- **File storage — Optional.** Event photos, speaker headshots, downloadable schedule PDFs.
- **Payments — Required.** Stripe Checkout with tax + fee handling. Refund flow.
- **Transactional email — Required.** Ticket confirmation with QR, calendar invite (.ics), 7-day-before reminder, day-of reminder.
- **External APIs / third-party services:**
  - Stripe Connect for organizer payouts
  - Apple/Google Wallet for tickets
  - Custom subdomain per event

**Environment variables to expose in the build:** mark every secret (API key, DB URL, JWT secret, Stripe key, S3 credential) as a clearly named `.env` variable — never hard-code. Include a `.env.example` with the full list.

**Auth + data privacy reminders:** never log secrets · never store passwords in plain text · use HTTPS everywhere · hash + salt with bcrypt or argon2 · refresh tokens with rotation · honor a 'delete my account' request inside the UI.

## 5. Use cases & content to include
Build dedicated UI sections or pages for each of these — they tell you what content the page must support.

- **Conference Management** — Run multi-day events with speaker lineups, session schedules, and attendee registration. Participants can browse the agenda and sign up for sessions that interest them.
- **Community Meetups** — Host recurring meetups without rebuilding registration each time. Members see upcoming events, RSVP, and access all essential details.
- **Workshop Sales** — Sell tickets for classes or training sessions. The platform handles registration while you focus on delivering strong content.
- **Corporate Events** — Manage internal gatherings, client functions, or training sessions. The clean presentation works across small team events and larger company-wide programs.

## 6. Recommended page structure
Generate the following sections in this order. Adjust labels to fit the brand voice, but keep the structural intent.

1. Hero with event name, date, location, primary CTA.
2. Schedule / agenda.
3. Speakers or guests (if applicable).
4. Venue / location section with map.
5. RSVP or ticketing form.
6. Gallery (if appropriate).
7. Footer.

## 6b. First-visit onboarding

Show a **first-visit onboarding** the first time a visitor lands on the site
(detect via `localStorage` flag; do not show on return visits). Keep it
short — three steps maximum — and respectful: visitors can dismiss at any
time and revisit later from a `?` icon in the header.

**Format:** a polished modal *or* a 3-step inline tour, designed to match the
overall visual style of the template (don't bolt on a generic stepper UI).
On mobile, full-screen sheet that slides up.

**Required content — three slides:**

1. **What this is.**
   - One-line headline: "Welcome to *Event Platform* — a template for Launch a professional event platform with registration, maps, and real-time countdowns. Complete event management and discovery—go live in hours, not weeks."
   - One paragraph (max 60 words) explaining what the template demonstrates,
     who it's for, and what you'd typically use it for.
   - Visual: a small annotated screenshot of the page they're about to see,
     OR a 4-frame storyboard of key sections.

2. **What to try.**
   - 2–3 specific things the visitor should look at to understand the design
     (e.g. "Open a section to see the booking flow", "Hover the gallery for
     captions", "Resize the window — every layout is fluid").
   - Reference real elements on the actual page so the visitor learns by doing,
     not by reading.

3. **How to remix this.**
   - A direct CTA: "Use this template" → links to Lovable / AI Studio Build
     remix entry point.
   - Below: 3 short bullets on how to make it yours — e.g.
     • "Swap the copy in `data/content.{ts,json}` for your own."
     • "Replace the imagery in `/public/images/` (we use AVIF + WebP)."
     • "Connect your services using the env-var list in section 4b above."
   - Plus a quieter secondary action: "Just looking — close" (closes modal,
     remembers preference in localStorage, never auto-shows again).

**Persistent re-entry point:**
A small "?" icon in the top-right header next to the primary nav. Click → reopens the onboarding from slide 1. Tooltip: "How this template works".

**Accessibility:**
- Trap focus inside the modal while open
- `Esc` closes
- All controls reachable by keyboard, visible focus ring
- Heading hierarchy: modal title is `h1` inside the dialog
- `role="dialog"` + `aria-modal="true"` + `aria-labelledby`
- Restore focus to the trigger (or to `<main>`) on close
- Respect `prefers-reduced-motion` — fade in/out only, no large transforms

**Copy tone:**
Warm and direct, not corporate. Avoid "Welcome to your dashboard" language.
Avoid all caps. Use the same voice as the rest of the template's copy.

**Don't:**
- Don't gate content behind the modal. The page below must be fully scrollable.
- Don't show the modal again on return visits. Use `localStorage['onboarding-seen']`.
- Don't include marketing CTAs unrelated to remixing (no newsletter signup, no
  "follow us on X" — those live elsewhere).

## 7. Design language
- **Mood:** Celebratory or focused depending on event type; always image-first.
- **Typography:** Display serif or expressive sans for event name; clean body sans. Use a clear modular scale (e.g. 12 / 14 / 16 / 20 / 24 / 32 / 48 / 64 px) and tight tracking on display sizes.
- **Palette:** Aligned with event vibe — warm for weddings, technical for conferences.
- **Spacing:** consistent 4-px base. Generous whitespace — let the content breathe.
- **Radius:** consistent token set (e.g. 6 / 12 / 20 px). Don't mix arbitrary values.
- **Shadows:** subtle, layered. Avoid heavy drop-shadows.
- **Imagery:** Aspirational hero imagery matching the event genre.
- **Motion:** purposeful — entrance fades, hover lifts, page transitions. Respect `prefers-reduced-motion`. No bouncing splash animations.

## 8. Content generation rules
- Write **realistic, specific copy**. NO Lorem Ipsum. NO generic placeholders like 'Your tagline here'.
- Invent plausible names, dates, locations, prices, quotes, testimonials and product details that fit the domain.
- Tone should match the audience above — confident, specific, free of buzzwords.
- Headlines: punchy and concrete. No 'Empower your business' filler.
- Body copy: short paragraphs (2–4 sentences). Use lists where appropriate.
- All numbers, stats, and metrics must look plausible for the domain.

## 8a. Seed content (use these specific examples)
Anchor the generated copy in the concrete data below. Use these names, numbers, dates, and snippets verbatim where helpful, or generate close variants that sit in the same world.

**Platform identity:** Gather · "From RSVP to recap — events, simplified."

**Currently running on Gather (showcase strip):**
1. "Studio Vela Pop-up — May 22" · Paris · 240 RSVP'd · launching
2. "Maker Faire — Berlin Edition" · June 8-9 · 1,200 attendees · live
3. "Designer Dinner Series Vol. 4" · Lisbon · 32/40
4. "Yoga in the Park — Summer Series" · Brooklyn · weekly · 4,200 across season

**Use cases (cards):**
- **Pop-ups & openings** — RSVP, waitlist, day-of QR check-in
- **Workshops & classes** — recurring schedules, capacity, drop-in passes
- **Conferences & summits** — multi-day, multi-track, ticketing tiers
- **Private parties** — invite-only, guest list, plus-ones
- **Markets & festivals** — vendor management, vendor map, attendee app

**Plans:**
- Free: 1 event, up to 100 attendees
- Pro: $39/mo · unlimited events, custom branding, integrations
- Business: $129/mo · ticketing, vendor tools, white-label
- Enterprise: contact sales

**Features strip:** "Beautiful event pages · attendee check-in · ticketing via Stripe · day-of attendee app · post-event recap site auto-generated"
**Testimonial:** "We replaced four tools with Gather and our event team stopped working Sundays." — Petra S., Studio Vela

## 9. Media & assets

Every `<img>`, `background-image`, gallery tile, thumbnail, and decorative figure on the page must come from ONE of the three buckets below. Do NOT reference any image path that is not specified here. Do NOT ship stock-photo placeholders.

### Bucket 1 — Runtime-generated via Nano Banana Pro (`gemini-3-pro-image`)

Generate at build time, cache to Firebase Storage at the path listed, serve via signed URL. Each call uses model `gemini-3-pro-image`, output format `image/webp`, dimensions as listed. The visual register matches section 7 (Design language) and the specific seed content in section 8a.

- **Hero image** → `/public/generated/hero.webp` · 2400×1500 · prompt: "Editorial hero photograph of the event named in section 8a at the venue described in section 8a, palette and tone consistent with section 7. For a conference: keynote-room atmosphere with lighting rig and front-row audience silhouettes; for a charity auction: gala-room atmosphere with table service and chandelier light. No on-image text, no readable signage rendered as letters. Real-photo aesthetic, 35mm look."
- **Schedule moment images (one per row in section 8a's agenda)** → `/public/generated/schedule/{slug}.webp` · 1200×1200 · prompt: "per-row prompt built from each agenda row literal text (e.g. "keynote: AI safety" → "speaker on stage in dimmed auditorium, single key light, audience silhouetted, 35mm look, no readable signage")."
- **Speaker / guest headshots (one per name in section 8a's speaker list)** → `/public/generated/speakers/{speaker-slug}.webp` · 800×800 · prompt: "Per-speaker prompt: editorial head-and-shoulders portrait of the named speaker, neutral background consistent with section 7's palette, natural light, slight smile or neutral expression, no on-image text."
- **Venue photograph** → `/public/generated/venue.webp` · 1800×1200 · prompt: "Wide editorial photograph of the venue described in section 8a, no readable signage, no on-image text."
- **Past-event gallery tiles (8 images, if section 6 includes a gallery)** → `/public/generated/gallery/g-01.webp … g-08.webp` · 1600×1200 · prompt: "Per-tile prompt template: editorial documentary photograph at a past edition of the event. Subject: [stage close-up · audience laughter · networking-break candid · keynote applause · sponsor booth detail in soft focus · panel discussion · empty auditorium at dawn · closing-night drink]. No on-image text."
- **Wordmark / monogram** → `/public/generated/wordmark.svg` · prompt: "A simple event wordmark for the event named in section 8a, set in the display font of section 7, suitable for badge headers and email subjects." Favicon export to `/public/generated/favicon-256.webp` (256×256).

### Bucket 2 — Seed assets shipped with the deliverable

Static files committed to `/public/samples/` as fallbacks when generation fails. Generated once via Nano Banana 2 (`gemini-3.1-flash-image`), 1024×1024 WebP unless noted.

- `/public/samples/empty-state-tickets.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of a single perforated ticket stub, single-stroke outline, no colour fill."
- `/public/samples/empty-state-schedule.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of an empty schedule grid with one row dashed, single-stroke outline, no colour fill."
- `/public/samples/hero-fallback.webp` — 1600×1000 — same prompt as the Bucket-1 hero, encoded once at build and committed so the page renders identically if Gemini quota is exhausted.

### Bucket 3 — User-supplied (when the template is remixed)

Onboarding modal surfaces a "Replace with your photos" hint. Uploads land via the file input → Firebase Storage path `events/{eventSlug}/uploads/`. The build ships with Bucket-1 + Bucket-2 only; no user-supplied images at first paint.

### Hard rules

- Every `<img>` tag MUST have a `src` that resolves to a path listed above. Any `<img>` referencing a path not in this section is a build error.
- No bare `image.jpg` / `hero.jpg` / `placeholder.png` references anywhere in the code.
- Icons: `lucide-react` only; use sparingly and consistently — never decorative-only.
- Optimisation: WebP or AVIF, `loading="lazy"` on everything below the fold, explicit `width`/`height` to prevent layout shift.

## 10. Interactivity & states
- Every interactive element has a hover, focus, active, and disabled state.
- Forms validate inline and show specific error messages.
- Loading states (skeletons, not spinners where possible).
- Empty states with helpful next-action guidance.
- Smooth scroll for in-page anchors.

## 11. Tech & responsive requirements

- **File downloads on Safari / Firefox:** when offering local-disk save of any export (PDF, CSV, MP3, ZIP, JSON, image, `.ics` calendar invite), fall back to `<a download>` with a blob URL — the File System Access API (`showSaveFilePicker()`) is Chromium-only. Detect with `'showSaveFilePicker' in window`; otherwise use the anchor-download path.
- **Stack:** React + TypeScript + Tailwind CSS. Use functional components and hooks.
- **Mobile-first.** Verify layouts at 375 px (iPhone SE), 768 px (iPad), 1024 px, 1440 px+.
- Use `clamp()` for fluid typography where appropriate.
- Prefer container queries over media queries for component-level responsiveness.
- Use `dvh` / `svh` units instead of `vh` to handle mobile viewport chrome.
- Zero horizontal overflow at any width. Zero layout shift on load.
- Respect safe-area insets on iOS.

## 12. Accessibility (WCAG 2.2 AA)
- Semantic HTML — `header`, `nav`, `main`, `section`, `article`, `footer`.
- All interactive controls reachable by keyboard with a visible focus ring.
- Color contrast ≥ 4.5:1 for body, 3:1 for large text and UI components.
- All images have meaningful `alt` text. Decorative images use `alt=""`.
- Form fields have associated `<label>`s; errors announced via `aria-describedby`.
- Respect `prefers-reduced-motion`.
- Tap targets ≥ 44 × 44 px on touch.

## 13. Quality bar — avoid AI clichés
Do **not** ship any of the following unless the design explicitly calls for it:
- Hero with a gradient background and floating geometric / orb shapes.
- A row of 4 'by the numbers' stat cards (e.g. '10k+ users / 99.9% / 24/7 / 4.9★') below the hero.
- Emoji bullets in body copy.
- 'Lorem ipsum' or 'Your headline here' placeholders.
- A pricing table with three identical-looking tiers when the product has no real pricing.
- Faux testimonials with stock-photo headshots that all look like the same person.
- Generic 'features grid' of 6 cards with the same icon style and 1-line description each.
- Hero CTA labelled 'Get started' with no second action.

Aim for the polish of a hand-crafted production site — specific, considered, with real domain knowledge in the copy.

## 14. Deliverables
A single working site that I can preview immediately, with all sections populated, all images placed, all interactions wired up, and no TODOs.