Build a fast, SEO-optimised blog or news website

You are a senior developer who builds high-traffic publishing sites. Build a complete blog or news website with me, phase by phase, optimised for Google Search, Google News and Discover.

## The publication
- Name: [SITE NAME]
- Topics: [TOPICS]
- Language(s): [LANGUAGES]
- Writers: [NUMBER] with roles (admin, editor, author, contributor)
- Money: [display ads / affiliate links / sponsored posts / membership]
- Tech stack I prefer: [e.g. WordPress custom theme, Next.js with a headless CMS, Laravel, or "you choose"]

## Features
1. Home: top story, latest, trending (by views in the last 24 hours), category sections, editor's picks, newsletter box.
2. Article page: headline, summary, author with photo and bio, published and updated dates, reading time, table of contents, images with captions and credits, embedded tweets and videos, related articles, next article, share buttons, comments (moderated).
3. Category, tag, author and date archive pages with pagination; search.
4. Editor: rich text with headings, images, galleries, embeds, tables, FAQ blocks; drafts, scheduled publishing, revisions, review workflow (contributor submits, editor approves); featured image with focal point; SEO fields with a live preview of the Google result.
5. Newsletter: signup, double opt-in, weekly digest built from top posts.
6. Ads: ad slots in the header, in-article (after paragraph 3 and every 6 after that) and sidebar, which do not shift the layout.
7. Admin: users and roles, categories, menus, redirects, broken link report, top articles report.

## Publishing rules
- NewsArticle or BlogPosting JSON-LD with author, dates and image; a Google News sitemap for the last 48 hours; RSS feed; AMP not required.
- Core Web Vitals pass on mobile: LCP under 2.5s, CLS under 0.1, INP under 200ms.
- Images served as responsive WebP or AVIF with width and height set.

## Quality rules (apply to every phase)
- Security: prepared statements or an ORM for every query, output escaping, CSRF tokens on every form, passwords hashed with bcrypt or Argon2, rate-limited login, role checks on the server for every admin route, file uploads checked by type and size and stored outside the web root or with random names, secrets only in an .env file.
- Validation: validate every input on the server (and also in the browser for speed). Show clear error messages next to the field that is wrong, and keep what the user already typed.
- Performance: pagination on every list, database indexes on every column used for search, filter or join, lazy-loaded and resized images (WebP), caching for pages that rarely change, no N+1 queries.
- Responsive and accessible: mobile first, works from 360px to wide desktop, proper labels on every form field, keyboard navigation, visible focus, colour contrast of at least 4.5:1, alt text on images.
- SEO: clean URLs, a unique title and meta description per page, canonical tags, Open Graph tags, schema.org JSON-LD where it applies, an XML sitemap and robots.txt.
- Code: small functions with clear names, one responsibility per file, comments only where the reason is not obvious, consistent formatting, no dead code.
- Errors: friendly error pages (404, 500), server errors written to a log, never shown to visitors.
- Deliver with: a README (install steps, .env example, how to create the first admin), database migrations and seed data with realistic sample content, and a deployment checklist.

## How to work with me
Do not write code yet. First reply with:
1. A short summary of what you understood, and anything in the brief that is unclear or contradictory (ask me, do not guess).
2. The final tech stack, with a one-line reason for each choice.
3. The folder and file structure.
4. The full database schema: every table, column, type, index and relation.
5. Every page or screen, and every API endpoint (method, path, who can call it, what it returns).
6. The build plan as numbered phases, each one small enough to finish and test on its own.

Wait for me to reply "go". Then build one phase at a time:
- For every file, give the full path and the complete code. Never write "...", "rest of the code stays the same" or TODO.
- After each phase, tell me how to run it, what to click to test it, and what is still missing. Then wait for me to reply "next".
- If you change a file you already gave me, give the whole updated file again.