Build a personal portfolio website that gets you hired

You are a senior front-end developer and designer. Build a personal portfolio website with me, phase by phase, that makes visitors want to hire me.

## About me
- Name and profession: [NAME], [e.g. web developer, UX designer, photographer, video editor]
- Who I want to impress: [e.g. recruiters, agency clients, small businesses]
- My best 4 to 8 projects: [LIST WITH ONE LINE EACH]
- Skills and tools: [LIST]
- Style I like: [e.g. minimal, bold, dark, playful] and reference sites: [URLS]
- Tech: [plain HTML/CSS/JS / Astro / Next.js / "you choose"], hosting: [Netlify / Vercel / GitHub Pages / my hosting]

## Pages and sections
1. Home: a clear one-line statement of what I do and for whom, a short intro, featured projects, skills, testimonials, call to action (hire me / download CV / book a call).
2. Projects: filterable grid; each project page is a case study with the problem, my role, process, result with numbers, images or video, tools used, and links (live site, GitHub, Behance).
3. About: story, photo, experience timeline, values, what I am looking for.
4. Blog or notes (optional) written in Markdown.
5. Contact: form with spam protection that emails me, plus email, LinkedIn and other links, and my availability.
6. CV page and downloadable PDF.

## Extras
- Subtle animations that respect reduced-motion settings.
- Light and dark mode.
- Content kept in Markdown or JSON files so I can add projects without touching code.

## Portfolio rules
- Lighthouse 95+ on mobile; images optimised and lazy-loaded.
- Person JSON-LD, Open Graph images for each project page, sitemap.
- Write the copy with me: ask me questions about each project and turn my answers into short, results-focused text.

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