Clients do not care which framework their site runs on. They care that it ships on time, loads fast, and can be maintained by whoever comes after you. So the framework question is really a risk question — and each of my three defaults answers it differently.
My decision rules
Content-heavy site that changes a few times a month? Astro — static by default, zero JavaScript until you ask for it. App-like product with auth, dashboards, and a team that already knows React? Next.js. Rich interaction and animation on a content site? SvelteKit — less code and motion feels native.
Pick the tool whose failure modes you understand.
Whatever you choose, write the decision down. A one-page rationale saves the next developer a week of archaeology.
If any of this maps to a project you are planning, I am happy to talk it through — no pitch, just a second pair of eyes. Start a conversation
