# 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 — Elegant Wedding Invitation 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/evermore-elegant-wedding-invitation-template_ --- ## 1. Project Build a **Events** named **Elegant Wedding Invitation**. One-line description: _Elegant wedding invitation site_ **What it is:** This template gives you a wedding invitation website that looks polished and personal—and you don't need coding experience to make it work. Most couples struggle to build a site that feels custom without hiring a designer or learning to code, and this template solves that problem from the first click. The technical parts are already handled. Mobile responsiveness, smooth scroll animations, an RSVP form that adjusts based on guest responses, and a multi-page layout for hotel and registry details—all done. You can focus on filling in your story, your photos, and the details your guests actually need. The monochromatic color palette and editorial typography give the site a refined, gallery-quality look without requiring you to make a single design decision. You don't need to agonize over color combinations or font pairings—the system is already cohesive, so your content looks polished the moment you add it. ## 2. Target audience - Couples planning a wedding who want their invitation site to look custom, not cookie-cutter - Wedding planners building digital experiences for clients without relying on developers - Event coordinators who need a professional online hub for ceremony and reception details - Design-minded couples who care about typography, spacing, and visual consistency - Agencies delivering wedding or event websites to clients on tight timelines - Engaged partners replacing paper invitations with a site that handles RSVPs, travel information, and accommodations in one place ## 3. Core value propositions Surface these clearly through copy, visual emphasis, and section ordering — they are the reasons users pick this product. - **Gallery-Quality Design System** — Monochromatic palette and editorial typography create a refined aesthetic without design decisions. - **Smart RSVP Collection** — Conditional form fields adapt to guest responses, keeping data organized without manual tracking. - **Complete Guest Information Hub** — Ceremony details, hotel info, and registry links in one shareable destination. - **Mobile-Perfect Experience** — Responsive layouts and touch-friendly interactions look polished on every device guests use. - **One-Click Deployment** — Go live in minutes with automatic hosting, security, and worldwide performance optimization. ## 4. Features to build **Product features:** Production-ready features built with modern tech stack for exceptional performance and user experience - Polaroid-Style Photo Layouts - Scroll-Triggered Animations - Conditional RSVP Form - Multi-Page Event Structure - Hotel Details Page - Categorized Registry Display - Three-Column Photo Gallery - Premium Typography Pairing - Responsive Layout System - Ghost-Style Navigation - Form Confirmation States - Long-Scroll Homepage ## 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:** - Optional Zola/Honeyfund/The Knot registry embed **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 Invitation Sites** — Send guests a single link that covers everything—ceremony details, reception info, hotel recommendations, and your registry. The long-scroll homepage with scroll-triggered fade-in animations guides visitors through each section naturally, so no one misses the important details. - **RSVP Collection** — The built-in RSVP form collects attendance confirmation, guest count, and dietary restrictions in one clean interface. Fields adjust based on each guest's response, keeping the form clean and your data organized. No chasing responses through group chats or spreadsheets. - **Travel and Accommodation Guides** — The dedicated hotel page displays amenities, check-in and check-out dates, booking details, and directions in a layout that looks great on any device. Guests get the information they need without digging through email threads, and the phone link lets them call the venue directly. - **Gift Registry Presentation** — Instead of scattering registry links across emails and group chats, the registry page organizes your wish list into clear categories—Kitchen, Home, Honeymoon Fund—with a personal note. The presentation feels intentional, not transactional, which matches the tone of the rest of your site. ## 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 *Elegant Wedding Invitation* — a template for Elegant wedding invitation 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:** Aisha Bello & James Okafor **Date:** Saturday, June 20, 2026 **Time:** 4:30 PM ceremony · reception to follow **Venue:** "Brookwater Estate · 1840 Brookwater Lane · Charleston, SC 29401" **Save the date message:** "With joy in our hearts and after seven years of building this life together, we ask you to share a day we'll never forget. — Aisha & James" **Schedule:** - 16:00 · Guest arrival · live string quartet - 16:30 · Ceremony · garden under the live oaks - 17:30 · Cocktail hour · veranda · oysters, low-country apps - 19:00 · Seated dinner · ballroom - 20:30 · First dance + open dancing · DJ until 23:30 - 23:30 · Sparkler send-off **Dress code:** "Formal · summer evening — pastels and florals welcomed" **RSVP details:** - RSVP by April 30 via this site - Indicate menu choice: filet, salmon, or vegetarian - Children: we love them dearly; reception is adults-only - Song requests welcome on the RSVP form **Lodging:** "The Vendue, The Mills House, Hotel Bennett — room blocks reserved · use code AISHA-JAMES" **Registry:** "Crate & Barrel · Honeyfund (honeymoon Greece) · Wildlife Charleston (in lieu)" ## 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: "Editorial photograph of the venue named in section 8a (e.g. 'Brookwater Estate, Charleston'), summer evening, live oaks and Spanish moss, palette of magnolia / cream / soft green, couple referenced in section 8a small in-frame, no on-image text, no logos. Real-photo aesthetic, medium-format look." - **Schedule moment images (one per row in section 8a's schedule)** → `/public/generated/schedule/{slug}.webp` · 1200×1200 · per-row prompt derived from the section 8a schedule (e.g. cocktail hour on the veranda → "low-light photograph of a Southern veranda with oysters and martinis on a marble table, 35mm look, no readable signage"). - **Venue exterior** → `/public/generated/venue.webp` · 1800×1200 · prompt: "Wide editorial photograph of the venue described in section 8a in summer evening light, oak canopy, no readable signage." - **Gallery tiles (12 images)** → `/public/generated/gallery/g-01.webp` … `g-12.webp` · 1600×1200 · per-tile prompt template: "Editorial Southern-summer wedding documentary photograph at the venue described in section 8a. Subject: [one of: garden ceremony under live oaks · ring exchange · first dance under string lights · plated dinner detail · low-country appetiser table · string quartet in shadow · couple under Spanish moss · sparkler send-off · bouquet of magnolia and ranunculus · linen menu card detail · guests laughing on the veranda · empty dance floor at 23:30]. 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, hairline weight, classic Southern engraving feel." 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 `