================ ONE-SHOT BUILD CONTRACT (read first) ================ Build this in Google AI Studio "Build" in ONE shot — a complete, working app, no follow-up turns. These are hard rules, not suggestions: 1. TARGET = Full-Stack Web (Node server runtime, secrets, Firebase allowed). If you target Native Android instead, you MUST drop all server/DB/Workspace/ secrets and persist locally (Room / SharedPreferences) only. 2. PIN EVERY MODEL CALL — never let the agent auto-select (it downgrades on quota): - Reasoning / text -> gemini-3.5-flash (thinkingLevel: minimal|low|medium|high) - 4K image + legible text -> gemini-3-pro-image (image_size "4K", up to 14 refs) - High-volume image -> gemini-3.1-flash-image - Expressive TTS -> gemini-3.1-flash-tts-preview (inline tags e.g. [whispers]) - Realtime audio/video (WebSocket) -> gemini-3.1-flash-live-preview - Sandboxed agent -> antigravity-preview-05-2026 3. DIVISION OF LABOR — the model ONLY parses/extracts to a strict responseSchema. ALL math, money (store currency as integer minor units / cents), sorting, balancing and graph logic run in deterministic TypeScript/Python. The model must never compute totals, splits or balances itself. 4. responseSchema sanitation — no regex patterns, no fixed-length tuples, no format validators in the schema (they crash the OpenAPI engine). Enforce those in server-side code AFTER parsing the JSON. 5. responseSchema and google_search grounding are MUTUALLY EXCLUSIVE in one call. 6. CODEGEN — split large output into modular, single-responsibility files so no file is truncated by the output-token cap. 7. Every external call gets a graceful fallback (e.g. manual paste if a Workspace read fails). Never a silent dead end. 8. ROBUST STORAGE & CANVAS — Wrap all `localStorage`/`sessionStorage` operations (especially JSON parsing and writes) in `try-catch` blocks to prevent crashes in private windows or quota overflows. Canvas drawing elements must dynamically handle window resize and scale pixel density (`window.devicePixelRatio`) to avoid blurry graphics on retina displays. ===================================================================== # 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 — Financial Trade Publication 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/editorial/ledger-financial-trade-publication-template_ --- ## 1. Project Build a **Editorial** named **Financial Trade Publication**. One-line description: _Professional industry news publication_ **What it is:** This template gives you a full-scale trade publication website that looks like an established media property—and you don't need a development team or editorial platform experience to make it work. Sixteen ready-to-use pages cover everything from articles and category archives to research reports, events, and job listings. The technical parts are already handled. Responsive layouts, article category systems, skeleton loading states, mobile navigation—all done. You can focus on publishing the market analysis and industry coverage your readers actually need. From a membership pricing page with monthly and annual toggling to a contributor profiles section and newsletter signup forms, this template covers the full scope of a modern trade publication. Dark mode support and smooth scroll-triggered animations give it a polished editorial feel from day one. ## 2. Target audience - Industry professionals launching a niche trade publication to monetize their expertise - Solopreneurs building media businesses around market analysis and sector-specific news - Agency teams delivering publication websites for clients in finance, technology, or specialized industries - Consultants and analysts establishing thought leadership through long-form editorial content - Small teams creating membership-driven research and intelligence platforms - Business owners who need an authoritative content hub to attract enterprise clients ## 3. Core value propositions Surface these clearly through copy, visual emphasis, and section ordering — they are the reasons users pick this product. - **Complete Publication Infrastructure** — Sixteen ready-to-use pages covering articles, research reports, events, job boards, and membership pricing. - **Professional Editorial Design** — Three-tier navigation, category systems, and polished layouts that establish immediate industry credibility. - **Membership Revenue Ready** — Built-in pricing page with monthly and annual toggles to monetize your expertise from day one. - **Mobile-Optimized Experience** — Responsive layouts and animated mobile navigation ensure readers engage on any device. - **Full Dark Mode Support** — Complete light and dark color schemes give your publication a polished, modern editorial feel. - **Smooth Editorial Animations** — Scroll-triggered animations and hover effects create an engaging, high-end reading experience. ## 4. Features to build **Product features:** Production-ready features built with modern tech stack for exceptional performance and user experience - Five Editorial Categories - Research Reports Section - Events and Job Board - Contributor Profiles - Newsletter Signup Forms - Three-Tier Header Navigation - Article Detail Pages - Skeleton Loading States - Premium Typography Pairing - Membership Pricing Page - Article Card Hover Effects - Latest News Sidebar ## 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 — Required for paywalled content.** Email + magic link or password. Subscriber tiers. - **CMS — Required.** Headless CMS (Sanity / Strapi) or in-house. Articles, authors, sections, tags, issue archives, paywall metadata. - **Image CDN — Required.** Editorial-grade imagery, captioned, sized via srcset. - **Payments — Required for subscriptions.** Stripe Billing (monthly + annual + lifetime). Gift subscriptions. Receipt PDFs. - **Newsletter + transactional — Required.** Daily/weekly newsletters, paywall metering email, sub renewal email. - **External APIs / third-party services:** - Analytics (Plausible/Fathom) - Push notifications (web push) for breaking stories **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. - **Industry News Publications** — Publish categorized articles across five editorial sections—Market Analysis, Industry News, Technology, Venture Capital, and Regulation. The three-tier header navigation, category pages, and article detail layouts give your publication the structure readers expect from a credible news source. - **Research and Intelligence Platforms** — Showcase downloadable research reports with page counts, download statistics, and free or premium access badges. The research reports page, combined with the membership pricing tiers, lets you build a subscription-based intelligence service that justifies premium pricing for your deep expertise. - **Event and Community Hubs** — Promote upcoming events and webinars with registration status indicators alongside a job board featuring salary ranges and company details. The events and job board pages turn your publication into a community destination—not just a place people read and leave. - **Membership-Driven Media** — Convert readers into paying subscribers using the built-in membership page with a monthly-to-annual pricing toggle and a highlighted recommended tier. Combined with multiple newsletter signup forms and contributor profiles that showcase your editorial team's credibility, the template supports the full reader-to-subscriber journey. ## 6. Recommended page structure Generate the following sections in this order. Adjust labels to fit the brand voice, but keep the structural intent. 1. Front-page masthead with publication name and date. 2. Lead story large; secondary stories in a grid below. 3. Section navigation (Politics / Culture / etc.). 4. Article detail with editorial-grade typography. 5. Newsletter signup. 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 *Financial Trade Publication* — a template for Professional industry news publication." - 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:** Newspaper / magazine. Type-driven, rule lines, hierarchical headlines. - **Typography:** Editorial serif headline + sans body or vice-versa. Use a clear modular scale (e.g. 12 / 14 / 16 / 20 / 24 / 32 / 48 / 64 px) and tight tracking on display sizes. - **Palette:** Paper + ink + 1 accent (often red, navy, or amber). - **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:** Editorial photography, illustration, archival textures. - **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. **Publication identity:** Tabula · "The trade publication for institutional finance." · founded 2016 · daily online · weekly print **Lead story (front page):** "Inside the European Central Bank's Quiet Pivot on Climate-Risk Loans" by Aanchal Gupta · published May 12, 2026 · 5,800 words · subscribers only **Front-page columns:** - **Today's Markets** — S&P 5,184 (-0.4%) · STOXX 50 4,892 (+0.2%) · 10Y Treasury 3.84% · Bitcoin $94,200 (+2.1%) - **Top Stories** 1. "ECB's Quiet Pivot on Climate-Risk Loans" — Aanchal Gupta · subscriber 2. "How JPMorgan Lost $1.4B on a Single CDS" — Aanchal Gupta + Marcus Tate · 8,400 words 3. "The Fed Minutes — Three Questions for the August Meeting" — Karim H. · analysis 4. "European Carbon Markets — A Buyer's Guide" — Maya R. · how-to 5. "What the New SEC Disclosure Rules Mean for IPOs in Q3" — Petra S. · regulation **Newsletters:** - The Morning Tabula — Mon-Fri 6:00 ET — free — 84k subs - The Pivot — daily 16:30 close newsletter — paid — 14k subs - The Long Read — Saturday — paid — 24k subs **Subscription:** $390/yr individual · $4,800/yr enterprise (≤10 seats) · custom for institutions **Trust strip:** "All sources verified · no display ads · 6-year recipient of NAFCU Excellence in Reporting" ## 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 newspaper-style lead-story photograph illustrating the top story named in section 8a. Documentary aesthetic, real-photo look (or, where section 8a calls for it, a black-and-white archival photograph or an editorial illustration). No on-image text overlay, no readable signage that wasn't part of the scene. Subject framed for a broadsheet front page (room for headline at top)." - **Below-the-fold story thumbnails (one per story listed in section 8a)** → `/public/generated/stories/{story-slug}.webp` · 1200×800 · prompt: "per-story prompt built from each story title/section in section 8a, e.g. "The Algorithm Took My Job, Then Hired Me Back" → "newsroom-grade portrait of a worker at a kitchen table with a laptop, fluorescent overhead light, papers spread out, 35mm documentary look, no readable signage". One image per story." - **Author / byline portraits (one per named writer in section 8a)** → `/public/generated/authors/{author-slug}.webp` · 640×640 · prompt: "Newsroom-grade head-and-shoulders editorial portrait of the bylined writer named in section 8a, neutral background, natural light, slight smile or neutral expression, no on-image text." - **Section-page illustration banners (one per nav section in section 8a — Politics, Business, Climate, Tech, Culture, Science, Books, Opinion, Sports, Obituaries, Crossword)** → `/public/generated/sections/{section}.webp` · 2000×600 · prompt: "Wide horizontal editorial illustration banner representing the section's domain — e.g. Politics → marble columns at dusk in monochrome ink; Climate → wind turbines through fog. Print-illustration aesthetic, restrained palette, no on-image text." - **Wordmark / monogram** → `/public/generated/wordmark.svg` · prompt: "A simple wordmark for the publication named in section 8a, set in the display serif of section 7, broadsheet-masthead character, suitable for top of a front page." 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-archive.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of an empty newspaper archive box, single-stroke outline, no colour fill." - `/public/samples/empty-state-search.webp` — 1024×1024 — prompt: "Minimal hand-drawn line illustration of a magnifying glass over a folded broadsheet, 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 `publications/{publicationSlug}/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 `