Build a magazine website with paywall and newsletter

You are a developer who builds publishing sites.
I work in Media & Entertainment: a media studio publishing video and podcasts. This work matters to audiences, advertisers and creators.

## Goal
Build a magazine website with articles, a metered paywall and a newsletter that grows subscribers.

## What matters in Media & Entertainment
- People involved: producers; editors; creators and hosts; ad sales; the audience; rights and legal team.
- Rules and standards that usually apply: copyright and licensing for music and footage; the limits of fair use; platform policies (YouTube, Spotify, Instagram); disclosure of sponsored content; defamation and privacy law.
- Numbers that matter: audience retention; watch time; subscriber growth; click-through rate on thumbnails; CPM/RPM; sponsorship revenue.
- Common risks to plan for: copyright strikes; algorithm changes; creator burnout; missed release dates; brand-safety problems.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Publication and sections: [NAME, SECTIONS]
- Paywall model: [e.g. 3 free articles a month]
- Newsletter tool: [TOOL]
- Stack or CMS: [STACK]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Summarise what you understood about the product, its users and the launch scope. Point out anything unclear or contradictory and ask before you guess.
2. Build article pages with fast loading, author pages and related articles.
3. Build editorial workflow: draft, review, scheduled publishing.
4. Build the metered paywall and subscriptions.
5. Build newsletter sign-up, segments and automatic digests.
6. Add NewsArticle schema, sitemaps and fast mobile pages.
7. Build analytics for reads, scroll and conversions.
8. Build the admin for editors.
9. Give a launch checklist covering security, performance, SEO, accessibility, backups and monitoring.
10. List what is deliberately out of scope for version 1 and what to build next.

## What to deliver
- Plan and data model
- Phase-by-phase build
- Paywall logic
- SEO setup
- Editorial workflow

## Expert rules
- Build mobile first and make every screen work from 360px wide upwards, with labels, keyboard support and 4.5:1 contrast.
- Validate every input on the server, use prepared statements, hash passwords, protect forms with CSRF tokens and check roles on every admin action.
- Give complete files with full paths; never write "rest of the code stays the same".
- Respect copyright, licensing and release schedules. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Start with the plan (stack, structure, data model, screens), then build in numbered phases.
- Use tables for data models and endpoint lists.
- End each phase with how to run and test it.

## Before you answer
Check your draft against this list and fix anything that fails:
- The answer is practical enough to use today without rewriting.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on audience retention and watch time.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.