Tags: web-dev map

Frameworks MOC

Date: 2026-08-16

---

A framework note’s job is subtraction: what it adds on top of the language, and which of its magic is just the language. Never re-document the language.

---

Cross-framework concepts

The models frameworks share. Learn these once and every framework gets cheaper.

• Component Models — the shared idea: state in, markup out, composed
• Declarative vs Imperative UI — describing the target state versus scripting the transition
• Reactivity — the three families: virtual DOM diffing, signals, and compiled reactivity
• Virtual DOM — what it does, what it costs, and why frameworks are moving away from it
• Signals — fine-grained reactive primitives, and why they’re converging across frameworks
• Component State vs Application State — the boundary that decides whether you need a state library
• State Management Patterns — stores, context, atoms, and the problem each solves
• Data Fetching Patterns — waterfalls, parallel loading, suspense, and fetching where the data is needed
• Server Components — components that never ship to the client, and what that changes
• Routing — file-based, config-based, nested layouts, and route-level data
• Forms in Frameworks — controlled and uncontrolled, and the native behaviour usually being fought
• Framework Rendering Modes — how a framework exposes SSR, SSG, ISR and streaming
• Framework Escape Hatches — refs, effects, portals: reaching the platform when the abstraction won’t
• Choosing a Framework — the questions that actually differentiate, and the ones that don’t

JavaScript frameworks

• Reference - React — the library, its model, and the hooks rules that trip people
• Reference - Next.js — routing, rendering modes, caching layers, and what it adds over React
• Reference - Vue — the reactivity system and single-file components
• Reference - Nuxt — Vue’s meta-framework
• Reference - Svelte — compiled reactivity, and what disappears at build time
• Reference - Astro — content-first, islands by default
• Reference - React Router — loaders, actions and nested routes: what Remix became, and what Shopify Hydrogen runs on
• Reference - Remix — disambiguation, then Remix 3: the separate React-free project that now carries the name
• Reference - Express — the minimal Node server, and the middleware model

Backend frameworks

• Reference - Laravel — the PHP framework, its conventions, and the request lifecycle it wraps
• Reference - Symfony — components, dependency injection, and the framework Laravel builds on
• Reference - ASP.NET Core — the .NET web stack, middleware pipeline and dependency injection

Commerce frameworks

• Reference - Hydrogen — Shopify’s storefront framework: React Router 7 in a worker on Oxygen, a Shopify-shaped context and a cache over every API call. Plus the framework-agnostic toolkit it’s pivoting towards
• Shopify Theme Architecture — sections, blocks, JSON templates, and the settings schema. Where Reference - Liquid meets the platform

CSS frameworks

• Reference - Tailwind — utility-first, the build step, and the design-token relationship
• Utility-First vs Semantic CSS — the argument, stated fairly from both sides

Content frameworks

• Reference - AEM — Sling, the JCR, OSGi and HTL. A repository with a REST framework on top, where the URL is a path into content rather than a route

---

Borders

Filed in other domains, needed constantly here.

• Foundations — Libraries, Frameworks and Toolkits · Coupling and Cohesion · Abstraction and Leaky Abstractions
• Platforms — Shopify · Vercel