# 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 — Gallery Vows Wedding Site

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/wedding-template-2_

---

## 1. Project
Build a **Events** named **Gallery Vows Wedding Site**.
One-line description: _Create a gallery-quality wedding website that looks custom-designed, not template-generic. Launch in hours with elegant photo showcases, timeline stories, and RSVP collection._

**What it is:**
This template gives you a wedding website that looks professional and you don't need design skills to make it work. The gallery-inspired aesthetic with museum-style labeling and intentional negative space makes your wedding presentation feel like a curated exhibition—intentional and elevated, not generic.
Everything wedding professionals and couples struggle with—making galleries look curated on mobile, collecting RSVPs without multiple forms, presenting your story timeline with visual impact—already works. You won't lose clients because the mobile experience looks broken, or waste hours debugging form logic. You can focus on adding your photos and personalizing the content while the template handles presentation and functionality.
Your portfolio doesn't look like everyone else's. Gallery-quality presentation differentiates your service and justifies premium pricing when you're competing against photographers with generic portfolios. Navigation works smoothly whether guests are on phones or computers. The gallery presents your images with the polish of a professional exhibition, giving your wedding presentation the elevated feel you want.

## 2. Target audience
- Wedding photographers showcasing their work with gallery-quality presentation
- Agencies delivering custom-looking wedding sites on template timelines
- Couples creating sophisticated wedding sites without hiring developers

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

- **Contemporary Art Gallery Aesthetic** — Museum-quality design with curatorial language and minimalist typography that commands attention
- **Scroll-Triggered Visual Storytelling** — Immersive narrative experience with alternating timeline layouts and progressive reveal animations
- **Professional Image Gallery System** — Bento grid layout with museum-style hover labels for elegant photo showcases
- **Mobile-First Responsive Experience** — Touch-optimized navigation and layouts that adapt beautifully across all device sizes
- **Zero-Code Customization Ready** — CSS variables and component architecture enable complete rebranding without technical expertise

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

- 12 Custom Animations
- Intelligent Navigation System
- Museum-Style Gallery Labels
- Alternating Timeline Layout
- Conditional RSVP Form
- Full-Screen Mobile Menu
- Premium Typography System
- Infinite Marquee Component
- Three-Column Event Schedule
- Dark Mode Infrastructure
- Accessibility-First Architecture

## 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 — Not needed.**
- **Transactional email — Required.** Ticket confirmation with QR, calendar invite (.ics), 7-day-before reminder, day-of reminder.
- **External APIs / third-party services:**
  - Calendar (Google/iCal) for .ics generation
  - Maps for venue
  - Apple Wallet / Google Wallet for tickets

**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.

- **Wedding Invitations and Guest Information** — Create a complete wedding invitation website with event details, venue information, schedule, and RSVP collection. Your wedding presentation stands out from generic templates with an intentional, sophisticated feel that reflects your style. Guests view your timeline, browse photos, and submit RSVPs. The form shows guest count and dietary fields only when they confirm attendance.
- **Wedding Service Provider Portfolios** — Wedding photographers, planners, and designers can showcase their work with gallery-quality presentation. Win the client pitch with a gallery showcase in their brand colors before competitors submit static mockups. You're not delivering another template—you're showing curatorial expertise that justifies your rates. Document wedding day stories or client project progressions with timeline layouts that guide viewers through the narrative you're crafting.
- **Personal Wedding Sites That Feel Custom** — Couples who want their wedding website to feel unique, not cookie-cutter, can launch this gallery-inspired design without hiring developers. You're not settling for generic templates that thousands of other couples use—you're choosing a sophisticated aesthetic that can be personalized with your colors, photos, and story. Launch early with your engagement photos and save-the-date information, then add event details and RSVP collection as your wedding planning progresses.
- **Early Site Launch with Progressive Enhancement** — Launch your wedding website early with your core information and photo gallery. The minimalist design with electric blue accents creates visual impact without overwhelming visitors. As your wedding approaches, you can add event details, venue information, timeline stories, and RSVP collection to the same site, allowing it to grow with your celebration without requiring a platform change.

## 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 *Gallery Vows Wedding Site* — a template for Create a gallery-quality wedding website that looks custom-designed, not template-generic. Launch in hours with elegant photo showcases, timeline stories, and RSVP collection."
   - 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.

**Couple:** Petra Sandström & Aanchal Gupta
**Date:** Friday, May 8, 2026
**Venue:** "Stockholm City Hall + Fotografiska Museum reception"

**The story (told through galleries):**
- "How we met" — 12-image gallery, Berlin café, 2019
- "First trip" — Lofoten Islands, 2020
- "The proposal" — Stockholm archipelago, 2024
- "Engagement" — Diego Oviedo's portrait series, 2025

**Schedule:**
- 13:00 · Civil ceremony · Stadshuset · Blue Hall
- 14:00 · Champagne + photos at Riddarholmen
- 17:00 · Reception · Fotografiska Museum
- 18:30 · Seated dinner · 60 guests · 5 courses by Magnus Nilsson
- 21:30 · Speeches
- 22:30 · Dancing · DJ Lena Willikens
- 01:30 · Late-night fika + carriages

**Dress code:** "Black tie · all-genders any silhouette · no fur"

**RSVP form:** Name · Pronouns · Plus-one · Dietary needs · A favorite gallery you've visited (we'll print these into the menu)
**Travel info:** "Arlanda 20 min by Arlanda Express · ferries from Slussen · suggested hotels: Ett Hem, Lydmar, Berns"
**Gift policy:** "Donations to UN Women in our name · or simply your presence"
**Hashtag:** #PetraAndAanchal · curated photo wall post-event

## 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 wedding photograph of the couple named in section 8a at the venue described in section 8a, dress code and mood from section 8a respected, palette consistent with section 7. Couple in motion or partially turned to keep the moment universal. No on-image text, no logos, no readable signage. Real-photo aesthetic, 35mm or medium-format look."
- **Schedule moment images (one per agenda row in section 8a)** → `/public/generated/schedule/{slug}.webp` · 1200×1200 · prompt: "per-row prompt built from the row's literal description, e.g. "first dance" → "first-dance close-up under tungsten string-lights, brass band in shadow, motion blur, 35mm look, no readable signage""
- **Venue exterior** → `/public/generated/venue.webp` · 1800×1200 · prompt: "Wide editorial photograph of the venue described in section 8a at the event's time-of-day, no readable signage, no on-image text."
- **Gallery tiles (12 images)** → `/public/generated/gallery/g-01.webp … g-12.webp` · 1600×1200 · prompt: "Editorial documentary wedding photograph at the venue described in section 8a, in the register of section 7. Subject: pick one from [ring exchange · vow close-up · couple walking · long communal table · bouquet detail · first dance · sparkler send-off · plated-course detail · linen detail · guests laughing · band or DJ in shadow · empty venue at end of night]. No on-image text."
- **Wordmark / monogram** → `/public/generated/wordmark.svg` · prompt: "A simple two-letter monogram for the couple named in section 8a, set in the display serif of section 7, no flourishes." 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-rsvp.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of an empty RSVP card on a flat surface, single-stroke outline, no colour fill."
- `/public/samples/empty-state-gallery.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of an empty photo album with one photo corner exposed, 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 `weddings/{coupleSlug}/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.