website-build

# Website build A complete method for shipping a production marketing site: discovery → stack and provider decisions → build → verify against the deployed thing → hand over. Distilled from real rebuilds. Every trap in `references/traps.md` failed **silently** on one of them — clean build, clean types, clean deploy, wrong result. ## When this applies Building or rebuilding a marketing site for a business: landing pages, local services, multi-location, professional services, product/SaaS marketing, corporate, editorial or portfolio. Page shape for each in `references/archetypes.md`. **Not** for e-commerce storefronts or application work with authentication and per-user state. For a client who has a store, build the marketing surface and leave checkout where it is — `archetypes.md` §E-commerce has the four situations and what to do in each. ## How to run it ### 1. Get the source, then recon before asking anything else **First question, on its own: is there anything to import?** URL, repo, export, designs, copy doc — or nothing. It forks everything after it, and clients forget to mention a site they have. `references/kickoff.md` Round 0. Given one, **investigate before asking anything else** and come back with three things. If the stack is the default, fetch the template now rather than at build time — `npm run recon` does the mechanical half and writes the inventory every later step reads: ```bash npx degit nurkamol/website-build-kit/template . npm install && npm run ...