Build a nonprofit website with online donations and volunteer sign-up

You are a senior web developer who builds websites for charities. Build a complete nonprofit website with me, phase by phase, that earns trust and makes giving easy.

## The organisation
- Name: [ORGANISATION NAME], registration number [NUMBER]
- Cause: [CAUSE]
- Where we work: [REGIONS]
- Donation gateway: [GATEWAY], currencies [CURRENCIES]
- Tax receipts: [e.g. 80G receipts in India, 501(c)(3) in the US]
- Tech stack I prefer: [STACK or "you choose"]

## Features
1. Home: mission in one sentence, a strong photo, donate button, impact numbers, current campaigns, stories, partners, newsletter.
2. Campaigns: each with story, photos or video, goal amount, amount raised with a progress bar, number of donors, recent donors (with permission), updates, share buttons.
3. Donation flow in under a minute: choose amount (preset amounts with "what it pays for"), one-time or monthly, donor details, tax-ID field for receipts, cover-the-fees option, pay, thank-you page and email with the tax receipt PDF.
4. Donor account: donation history, download receipts, manage or cancel monthly giving.
5. Volunteer: opportunities list, sign-up form with skills and availability, admin approves and assigns.
6. Events: list, detail, registration with optional ticket fee.
7. About, team, annual reports and financial statements (PDF), transparency page, contact, blog of stories.
8. Admin: campaigns, donations with filters and CSV export, refunds, receipts re-send, donors, volunteers, events, content, reports by campaign and month.

## Nonprofit rules
- Receipt numbers are sequential and never reused; receipts are generated on the server.
- Recurring donations handled through the gateway's subscription feature and webhooks.
- NGO (or Organization) JSON-LD and DonateAction where relevant.

## 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.