Interactive guide · 2026 edition

Frontend Tech Stacks, Visualised

A mind-map view of the 2026 frontend universe — frameworks, meta-frameworks, styling, state, forms, build tools, UI libraries, and hosting. Pick your stage, filter by what matters, and see the stack that fits.

/ search 1-4 stage Esc reset

The landscape at a glance

— · click a node to jump to its card

Which stage are you at?

Pick one — the stack below adapts, and cards fade to only what fits.

All technologies

Decision cheat-sheet

Pick by team situation

  • Solo founder: Next.js + Tailwind + shadcn/ui on Vercel. Or SvelteKit for lighter footprint.
  • Small React team: Next.js App Router, Zustand, TanStack Query, RHF + Zod, Tailwind + shadcn, Playwright.
  • Small Vue team: Nuxt 3, Pinia, VueUse, Tailwind + Nuxt UI, Vitest, Playwright.
  • Content-heavy site: Astro + MDX + Tailwind. Zero JS by default.
  • Dashboard / admin: React + Mantine or Ant Design + TanStack Table.
  • Enterprise / regulated: Angular or Next with strict conventions + MUI.
  • Server-rendered + sprinkles: Rails/Django/Laravel + HTMX/Hotwire + Alpine.

Pick by constraint

  • Smallest bundle: Svelte or Solid.
  • Best SEO / TTI: Astro, Qwik, or Next with RSC.
  • Hiring pool: React, always.
  • Best DX for juniors: Vue + Nuxt or Svelte + SvelteKit.
  • Cross-framework design system: Lit + Web Components or Radix/Ark UI headless.
  • Zero JS if possible: Astro.

Anti-patterns to avoid

  • Chasing the framework of the quarter. Churn is expensive.
  • Building your own component library on day one.
  • Runtime CSS-in-JS with React Server Components.
  • Mirroring server state into Zustand/Redux.
  • Skipping TypeScript to "move faster".
  • Retrofitting accessibility after launch.
Tweet Reddit LinkedIn Star on GitHub