# 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 `` 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 — Desert 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/juniper-desert-wedding-website-template_ --- ## 1. Project Build a **Events** named **Desert Wedding Site**. One-line description: _Desert-botanical aesthetic wedding site_ **What it is:** This template gives you a multi-page wedding website that looks polished and intentional—and you don't need design skills or coding knowledge to make it work. Five pages cover everything your guests need to know, from your love story to travel details to registry links. The technical parts are already handled. Mobile responsiveness, smooth scroll animations, form validation, a live countdown timer—all built in and ready to go. You can focus on filling in your details and sharing your story instead of wrestling with layouts and code. The design draws from a desert-botanical aesthetic—sage and cream tones, elegant script and serif typography, and smooth scroll animations that give the whole site an organic, refined feel. A masonry photo gallery, tabbed schedules, a live countdown, an FAQ accordion, and a validated RSVP form round out the experience. ## 2. Target audience - Ambitious solopreneurs planning their own weddings who want a professional, custom-looking site without hiring developers or paying for web design - Resourceful product builders and marketing professionals prototyping event websites and guest management experiences quickly - Small business owners running wedding planning services who need custom platforms for client portals and event coordination - Agency professionals delivering wedding website solutions to clients as part of broader event package services - Technical builders who want full control to customize and extend the template for specific wedding scenarios, with clean, well-organized code they can modify directly ## 3. Core value propositions Surface these clearly through copy, visual emphasis, and section ordering — they are the reasons users pick this product. - **Complete Five-Page Wedding Site** — Every detail covered—home, travel, activities, registry, and RSVP pages ready to customize. - **Polished Guest Experience** — Scroll animations, live countdown, photo lightbox, and tabbed schedules create an elegant impression. - **Built-In RSVP Collection** — Validated form with accept/decline options eliminates chasing responses through texts and emails. - **Mobile-Perfect on Every Device** — Responsive design adapts beautifully across phones, tablets, and desktops without extra work. - **Destination Wedding Ready** — Dedicated pages for travel info, hotel recommendations, and local activities keep guests informed. ## 4. Features to build **Product features:** Production-ready features built with modern tech stack for exceptional performance and user experience - Masonry Photo Gallery - Live Countdown Timer - Tabbed Three-Day Itinerary - FAQ Accordion Section - Validated RSVP Form - Wedding Party Showcase - Love Story Timeline - Hotel Cards with Booking Links - Scroll-Triggered Animations - Copy-to-Clipboard Hashtag - Desert-Botanical Design System - Fixed Navigation with Mobile Menu ## 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** (use Honeyfund link as third-party). - **Transactional email — Required.** Ticket confirmation with QR, calendar invite (.ics), 7-day-before reminder, day-of reminder. - **External APIs / third-party services:** - Optional Honeyfund/Zola integration **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. - **Destination Wedding Hubs:** — Organize every detail of a multi-day celebration across dedicated pages for travel, accommodations, and local activities. The tabbed three-day itinerary and hotel cards with booking links give guests everything they need in one place—no group chat chaos required. - **RSVP Collection:** — Collect guest responses through a built-in RSVP form with field validation, accept/decline options, and space for personal messages. The form handles the structure so you're not chasing replies through texts and emails. - **Love Story and Wedding Party Showcases:** — Share your love story through a narrative layout with a timeline of key moments, and introduce your wedding party in a tabbed showcase with photos of groomsmen and bridesmaids. The photo gallery creates an intentional visual flow, and sections animate into view as guests browse—keeping visitors engaged from start to finish. - **Guest Information and FAQs:** — Answer the questions guests always ask—dress code, parking, gifts—through an eight-item FAQ accordion on the RSVP page. Pair that with travel info covering airports, driving directions, and nearby activities so guests stop texting you for logistics. ## 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 *Desert Wedding Site* — a template for Desert-botanical aesthetic wedding site." - 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 `
`) 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:** Maya Reyes & Tomás García **Date:** Saturday, October 17, 2026 · Sunset ceremony **Venue:** "El Mirador — private property, Joshua Tree, California" **Hashtag:** #MayaAndTomásJT **Schedule:** - Friday Oct 16 · 18:00 · welcome drinks at La Copine restaurant (29 Palms) - Saturday Oct 17 · 16:30 · ceremony at El Mirador (shuttle from hotels at 15:30) - Saturday Oct 17 · 18:00 · cocktail hour + golden-hour photos - Saturday Oct 17 · 19:30 · dinner under the stars · family-style menu - Saturday Oct 17 · 21:00 · dancing + bonfire until midnight - Sunday Oct 18 · 10:00 · farewell brunch at Pioneertown Motel **Dress code:** "Desert formal — long flowing fabrics, earth tones, sneakers + boots welcome. Bring a wrap for the night." **Accommodations:** - Pioneertown Motel · room block · $260/night · 12 rooms held until Sept 1 - Sacred Sands · $390/night · 3 rooms held - Joshua Tree Inn · $180/night · use code MAYATOMAS **Travel:** "Fly into Palm Springs (PSP) — 45 min · LAX 2.5 hrs · Shuttles from Pioneertown 15:30 + 16:00" **RSVP form:** Full name · Plus-one name · Dietary restrictions · Song you want played **Registry:** "We are honored by your presence. If you wish to give: Honeyfund link · Habitat for Humanity Joshua Tree" ## 9. Media & assets Every ``, `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. - **Hero image** → `/public/generated/hero.webp` · 2400×1500 · prompt: "Wide editorial photograph of a desert wedding at the location named in section 8a, late-afternoon sun, dry brush and rock formations in the background, the couple referenced in section 8a small in-frame to keep the landscape the hero, neutral palette of bone / rust / sage, no on-image text, no logos, faces partially turned. Real-photo aesthetic, 35mm look." - **Schedule moment images (one per row in section 8a's schedule)** → `/public/generated/schedule/{slug}.webp` · 1200×1200 · one prompt per row derived from the section 8a schedule (e.g. ceremony under a desert oak → "low-angle shot of a small ceremony under a desert tree at golden hour, no signage rendered as readable letters, 35mm look"). - **Venue exterior** → `/public/generated/venue.webp` · 1800×1200 · prompt: "Wide editorial photograph of the desert venue described in section 8a, mid-afternoon sun, mesa silhouette in the distance, no on-image text or readable signage." - **Gallery tiles (12 images)** → `/public/generated/gallery/g-01.webp` … `g-12.webp` · 1600×1200 · per-tile prompt template: "Editorial documentary photograph at the desert wedding described in section 8a. Subject: [one of: ring-exchange close-up · couple walking through sage at sunset · long communal table outdoors at dusk · cactus detail · guests dancing on sand · bouquet of pampas and protea · sun flare through a felt hat · stargazing after dinner · campfire embers · linen napkin detail · guitarist in shadow · empty lantern-lit tent at midnight]. 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, suggesting desert quietude — thin line weights, 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 by a real couple) Onboarding modal offers "Replace with your photos". 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 `` tag MUST have a `src` that resolves to a path listed above. Any `` 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 `` 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 `