Why static still wins
For personal publishing and documentation-heavy sites, static output is usually enough. It keeps startup performance strong and infrastructure cost low.
Practical setup
I prefer a small set of moving parts:
- SvelteKit with
@sveltejs/adapter-static - Build-time markdown parsing for content
- Cloudflare Pages configured to publish
build/
Rollback strategy
Static deployments are easy to roll back because each build is immutable. When something breaks, redeploy the previous known-good commit and investigate without pressure.