# 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 — Literary Journal and Publishing Platform 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/folio-literary-journal-publishing-platform-template_ --- ## 1. Project Build a **Editorial** named **Literary Journal and Publishing Platform**. One-line description: _Editorial platform for literary journals_ **What it is:** This template gives you a literary journal and publishing platform that looks professional and you don't need design skills or development experience to make it work. Fiction, poetry, essays, author profiles—it's all structured and ready to fill with your content. The technical parts are already handled. Subscription tiers with payment processing, a multi-step manuscript submission system, mobile-responsive layouts, and an editorial-quality reading experience—all done. You can focus on curating work and building a readership. The typography alone sets this apart. Zodiak headings and Sentient body text give your journal the kind of editorial presence that takes publishers months to develop from scratch. A warm orange accent color ties everything together without overwhelming the writing. ## 2. Target audience - Literary journal founders building a digital publication from the ground up - Small press publishers who need a professional platform for fiction, poetry, and essays - Writing community organizers launching a publication to showcase member work - MFA programs and university departments creating a home for student and faculty writing - Independent editors curating themed issues and managing contributor submissions - Agencies building publishing platforms for literary clients on tight timelines ## 3. Core value propositions Surface these clearly through copy, visual emphasis, and section ordering — they are the reasons users pick this product. - **Editorial-Quality Typography** — Zodiak headings and Sentient body text give your journal the polish of established publications. - **Complete Subscription System** — Three pricing tiers with Stripe checkout and subscription management ready to monetize from day one. - **Guided Manuscript Submissions** — Four-step wizard walks contributors through genre selection, details, and file upload seamlessly. - **Genre-Specific Content Display** — Fiction, poetry, and essays each get layouts designed for how readers engage with that form. - **Professional Reading Experience** — Scroll progress bar, adjustable font sizes, and drop caps create a print-quality reading environment. ## 4. Features to build **Product features:** Production-ready features built with modern tech stack for exceptional performance and user experience - Multi-Step Submission Wizard - Three-Tier Pricing Page - Adjustable Reading View - Author Profile System - Genre-Tailored Layouts - Stripe Payment Integration - Animated Navigation - Current Issue Showcase - Dark Mode Ready - Skeleton Loading States - Responsive Grid System - Authentication System ## 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. - **Literary Journals and Magazines** — Publish fiction, poetry, and essays in a format that treats each genre with care. Stories get list-style layouts with excerpts and reading times. Poems display with left-border accents and italic verse lines. Essays appear in card grids that invite browsing. The structure matches how readers actually engage with different literary forms. - **Subscription-Based Publications** — Monetize your journal with three subscription tiers—Reader, Supporter, and Patron—with both monthly and annual billing. The pricing page includes a monthly/annual toggle, a recommended badge for your mid-tier plan, and active subscription status for logged-in readers. Stripe checkout and subscription verification are built into the template from the start. - **Open Submissions Platforms** — Accept manuscript submissions through a guided four-step wizard that walks contributors from selecting their genre through uploading their manuscript file. Writers choose between fiction, poetry, and essay categories, fill in their details and cover letter, then drag and drop their document. The submission system keeps everything organized and tied to authenticated accounts. - **Author Showcases** — Feature your contributors with dedicated author profile pages that include bios and published works. The authors grid displays your roster across responsive columns, and each individual author page links back to their pieces in the journal. It's a practical way to build community and give writers a professional presence alongside their published 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. 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 *Literary Journal and Publishing Platform* — a template for Editorial platform for literary journals." - 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:** Quarto · "A quarterly journal of new fiction, poetry, essay, and translation." · founded 2014 · print + digital **Current issue (hero):** "Quarto №42 — Spring 2026 — 'After the Storm'" - 124 pages · 14 stories · 22 poems · 6 essays · 4 translations - Featured: Lauren Groff (new story) · Ocean Vuong (poem cycle) · Kapka Kassabova (essay) - Cover art: Hana Kim **Contributors in this issue:** - Fiction: Lauren Groff, Marlon James, Lydia Davis, Catherine Lacey, Joy Williams, Brandon Taylor, Maya Reyes (debut) - Poetry: Ocean Vuong, Layli Long Soldier, Aria Aber, Diane Seuss, Kaveh Akbar - Essays: Kapka Kassabova, Hisham Matar, Hilton Als - Translations: Olga Tokarczuk (from Polish), Andrés Neuman (from Spanish), Yoko Tawada (from Japanese) **Subscription:** - Print + digital: $48/year (4 issues) - Digital only: $24/year - Lifetime: $480 **Submissions strip:** "Open year-round for fiction, poetry, essay · 8-week response · pays $250/story, $50/poem" **Past issues archive:** "Issues 1-41 available · selected pieces free; subscribers full access" **Sample pull-quote:** "The most beautifully edited journal in America." — *The Paris Review* (the fantasy) ## 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 - **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 `