Do I Really Need Svelte in My Django Project? — A Practical Checklist I Wrote After Comparing Vanilla JS vs. Frameworks

Introduction While adding features like a hamburger menu, OAuth login, and per-user settings to a side project, I started to feel the limits of plain HTML/CSS/JavaScript (hereafter vanilla JS). As stateful widgets multiplied, so did the DOM spaghetti. That raised the million-dollar question: "Should I adopt Svelte (or SvelteKit), or keep pushing with vanilla JS?" This post distills a hands-on checklist for balancing framework benefits against resource constraints. 1. When did I actually need a framework? Requirement Pain with vanilla JS Svelte (Kit) advantage Shared state across multiple components Long querySelector chains & ad-hoc event buses $: reactivity, Stores for global state Client-side routing (SPA feel) Must hand-roll History API logic File-based routing built-in SEO + SSR Django template handles SSR, but JS widgets ship as empty <div> SvelteKit server-side render & prerender Bundle optimization Manual Webpack/Vite tuning Vite-powered build & code splitting