# 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 — Cinematic Wedding Photography Portfolio 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/portfolio/vesper-cinematic-wedding-photography-portfolio_ --- ## 1. Project Build a **Portfolio** named **Cinematic Wedding Photography Portfolio**. One-line description: _Cinematic, elegant wedding showcase_ **What it is:** This template gives you a wedding photography portfolio that looks professional and you don't need design skills to make it work. This template creates the kind of premium experience that makes couples feel confident choosing you over photographers with basic websites. The technical parts are already handled. Mobile layouts, image optimization, form setup—all done. You can focus on showcasing your best work and connecting with couples who want to hire you. Whether you're launching your first photography business or replacing a site that doesn't reflect your work quality, this template gets you online fast with everything couples expect from a professional photographer. ## 2. Target audience - Wedding photographers launching their business and booking their first clients - Established photographers who need a portfolio that showcases the quality and storytelling of their work - Agencies delivering professional photography websites to clients quickly without development bottlenecks - Solo photographers who need a portfolio that works beautifully on mobile and desktop - Photography businesses showcasing multiple packages and photographers on one platform ## 3. Core value propositions Surface these clearly through copy, visual emphasis, and section ordering — they are the reasons users pick this product. - **Cinematic Visual Storytelling** — Ken Burns effects, crossfade transitions, and editorial layouts showcase wedding photography professionally. - **Zero Setup Required** — Launch-ready portfolio with automated slideshows, inquiry forms, and mobile navigation built in. - **Luxury Brand Presence** — Premium typography, warm gold accents, and editorial spacing create high-end positioning immediately. - **Mobile-Optimized Client Experience** — Touch-friendly navigation, responsive galleries, and fast mobile performance convert inquiries into bookings. ## 4. Features to build **Product features:** Production-ready features built with modern tech stack for exceptional performance and user experience - Auto-Advancing Hero Slideshow - Story-Based Project Structure - Premium Typography System - Warm Gold Accent Palette - Touch-Optimized Mobile Menu - Client Inquiry Form - Hover-Reveal Image Effects - Scroll-Triggered Animations - About Section Framework - Dual Navigation System - Responsive Grid Layouts - Ready for Customization ## 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 — Not needed.** Portfolio sites are public. - **CMS — Light.** Optional headless CMS for case studies; static MDX-in-repo also fine. - **Image CDN — Required.** Hi-res photography served via Cloudinary/Imgix with srcset + AVIF/WebP. - **Payments — Not needed.** - **Transactional email — Required.** Inquiry form → routed to inbox + auto-acknowledge reply. - **External APIs — None required.** **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 Portfolio Showcase** — Display your best wedding stories with dedicated project pages for each couple. The image galleries let you tell the full story of each wedding day, from getting ready through the reception. Couples researching photographers want to see complete narratives, not just highlight reels. - **Client Inquiry Management** — The built-in contact form captures the details you actually need—names, wedding date, and their message. The professional presentation makes it easy for couples to reach out and creates an immediate positive impression. - **Brand Positioning** — When you're competing for premium bookings, your website needs to justify your pricing before couples even contact you. This template positions you as a professional who pays attention to details—the kind of photographer worth premium rates. The elevated design helps you compete for higher-budget weddings without losing bookings to photographers with more polished websites. - **Agency Client Delivery** — Deliver complete photography portfolio sites for your clients without custom development timelines or costs. The professional quality works for established photographers, while the fast turnaround lets you reallocate your development team to higher-value custom work. ## 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 — name, role, one-line positioning, optional portrait. 2. Selected work grid — 4–8 case studies with thumbnail + title + tags. 3. Case study detail layout — challenge, approach, outcome, large imagery. 4. About — bio, services / skills, clients list. 5. Contact — email + form, social links. 6. 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 *Cinematic Wedding Photography Portfolio* — a template for Cinematic, elegant wedding showcase." - 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:** Editorial, image-led, confident. The work is the hero — UI recedes. - **Typography:** A display serif (Fraunces, Tiempos, GT Sectra) + clean grotesque body. Use a clear modular scale (e.g. 12 / 14 / 16 / 20 / 24 / 32 / 48 / 64 px) and tight tracking on display sizes. - **Palette:** Off-white or paper backgrounds; one strong neutral; restrained accents. - **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:** Hero project image must look real and high-end. Use curated stock (Unsplash editorial) or describe a generation prompt that matches the 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. **Photographer identity:** "Vesper Photography — Lena Bremer — cinematic wedding photography — Lisbon, Paris, NYC" **Hero film + still (homepage):** "A still from Mira & Lucas — Cap Ferrat, October 2025 · ceremony at dawn · 14 sec slow-mo on autoplay" **Featured weddings (8 case study tiles):** 1. **Mira & Lucas — Cap Ferrat, France** — Oct 2025 — sunrise ceremony — 142 images · 2-min film 2. **Aisha & James — Charleston, USA** — June 2025 — Brookwater Estate — 184 images 3. **Hannah & Marcus — Cotswolds, UK** — Aug 2025 — Linden Hall — 168 images 4. **Yara & Jordan — LIC, NYC** — Aug 2025 — The Foundry — 134 images 5. **Maya & Tomás — Joshua Tree, USA** — Oct 2024 — El Mirador desert — 156 images 6. **Petra & Aanchal — Stockholm, Sweden** — May 2025 — City Hall + Fotografiska — 198 images 7. **Naomi & Karim — Bath, UK** — June 2024 — Ivory Hall — 142 images 8. **Iris & Marisa — Tuscany, Italy** — Sep 2024 — Villa di Geggiano — 188 images **Service pricing:** - Half-day (6 hr): €4,800 - Full day (10 hr): €6,800 - Weekend (Fri arrival → Sun): €9,800 - Add: 2-min cinematic film €2,400 · second photographer €1,200 · engagement session €890 · printed album from €620 **Sample testimonial:** "We were promised a photographer and Lena gave us a film. We watch our wedding back." — Mira & Lucas **Editorial features:** "Published in *Vogue Weddings*, *Magnolia Rouge*, *Once Wed*" **Inquiry form:** "Tell me about your wedding — date · venue · what matters most · please share your Pinterest if you have one" ## 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. 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 portrait or signature-project shot of the creator named in section 8a. Visual register of section 7 — typically minimal, image-led, soft natural light. If a portrait, neutral background; if a project shot, framed to feel inhabitable rather than rendered. No on-image text, no logos." - **Project thumbnails (one per case study in section 8a, typically 6-8)** → `/public/generated/projects/{project-slug}/thumb.webp` · 1600×1200 · prompt: "Per-project prompt built from the case-study title + location + year in section 8a, e.g. "Linden Hall, Cotswolds (UK) 2024, renovation + addition" → "editorial photograph of a Cotswolds country-house renovation, golden-hour exterior, stone facade with new glazed addition visible, 35mm look, no readable signage". One thumbnail per case study." - **Project case-study detail images (4-6 per project)** → `/public/generated/projects/{project-slug}/detail-01.webp … detail-06.webp` · 2000×1333 · prompt: "Per-detail prompt expanding from the case-study facts in section 8a — exterior wide, interior wide, material close-up, plan/section sketch render, scale-with-figure. No on-image text." - **About portrait** → `/public/generated/about-portrait.webp` · 1200×1500 · prompt: "Editorial portrait of the creator named in section 8a, natural light, neutral background, slight smile or neutral expression, no on-image text." - **Studio / process photographs (4 tiles for the About / Process section)** → `/public/generated/studio/s-01.webp … s-04.webp` · 1600×1200 · prompt: "Documentary photographs of the studio space described in section 8a — drawing desk, model wall, materials shelf, team in conversation. No on-image text." - **Wordmark / monogram** → `/public/generated/wordmark.svg` · prompt: "A simple personal wordmark for the creator named in section 8a, set in the display font of section 7, restrained and confident." 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-projects.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of an empty portfolio sleeve, single-stroke outline, no colour fill." - `/public/samples/empty-state-contact.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of an empty envelope with one stamp corner, 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 `portfolios/{creatorSlug}/projects/{projectSlug}/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 - **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 `