The meta-framework lane, mapped
Beyond the mainstream (WordPress, Shopify, React/Next, Vue/Nuxt) sits a lane of modern frameworks with genuine strengths: Astro, content sites that ship almost zero JavaScript by default, islands of interactivity where needed; SvelteKit, applications with Svelte's elegant reactivity and small bundles; Remix, web-standards-first data handling, forms and loaders done right. All three are production-grade, all three have passionate communities, and all three lose to the mainstream in hiring pool size and ecosystem maturity. The stacks pages cover the mainstream choices; this page is when the niche lane wins.
When each earns its place
- Astro: content-heavy sites, blogs, documentation, marketing sites, directories, where pages are mostly static and speed is the differentiator. Astro's output is among the fastest possible on the web, and this site's own architecture pattern (static, edge-served) is the same idea. If the site is 90% reading, Astro is a serious contender.
- SvelteKit: interactive applications where bundle size and simplicity compound, dashboards, tools, internal apps for teams that will maintain it with a small senior group. The trade: smaller talent pool for future hiring.
- Remix: data-heavy apps where forms, loaders and progressive enhancement align with the product, strongest when the team values web standards over framework magic.
When they are fashion, not fit
The red flags: choosing the stack because a conference talk was exciting, building a brochure site in SvelteKit because Astro was "too simple," or, the expensive one, picking a niche framework for a client whose next developer will be a generalist from the mainstream pool. Niche stacks concentrate hiring risk: fewer developers know them, and the ones who do are good and scarce. The honest filter this practice applies: who maintains this in year three, and can they be hired? If the answer is strong, the niche is fine. The stack pages carry the mainstream comparison, the calculator prices either path, and the stack decision is made in scoping, with the reasoning written down, whichever way it goes.