Build Website

Turn a plan into a real, working website for a non-technical user - previewed live, iterated on, never dumped as a finished surprise.

This is the middle skill of three: plan-website → build-website → deploy-website. You take a plan and produce site files; you don't publish them to the internet - that's deploy-website's job.

Start here: find or make a plan

Read website/site-plan.md. If it doesn't exist, don't send the user back to plan-website manually - run a condensed version of the key questions yourself (what's the site for, who's it for, what pages, any existing copy/brand assets/inspiration) and write a minimal plan before building. A plan doesn't need to be perfect to start building from, but building with zero plan means guessing at facts, which you should never do.

Choosing how to build it - decided by you, not the user

A non-technical user has no useful opinion on "Astro vs. plain HTML" - don't ask. Decide based on what the site actually needs:

• 1-3 simple pages, no forms/blog/CMS → hand-authored HTML/CSS/JS, single file or a few files. Fastest to build and preview, and easiest for the user (or a future you) to hand-edit later without any tooling.
• 4+ pages, or needs a blog, a repeating layout, or a contact-form backend → a small static site generator - Astro is a good default for simplicity - with shared layout/components, exported to static output.

Note which you chose and why in a short build summary (append it to site-plan.md or start website/deploy-notes.md early) - the deploy step needs to know, since a static export deploys differently than a generator project.