Sections 01–07 are the course — true regardless of framework. This folder is how a given stack does it. Same convention as backend/frameworks/.

Not numbered — there’s no reading order. Pick the one you’re using.

The map

CoversStatus
react/The React model, hooks, error boundaries2 notes + a routed index into projects/
next/App Router, RSC, caching, next/imageScaffold + a routed index
css/Tailwind, Sass2 notes
sanity/Headless CMS — the document model, GROQ, Portable TextFull course — 3 notes
gsap/Tweens, timelines, ScrollTrigger, pluginsFull course — 7 notes
framer-motion/Animate props, gestures, variants, layoutFull course — 8 notes
threejs/Scene/camera/renderer, materials, R3FFull course — 8 notes

Note the shape of that table. The animation and 3D courses are the deepest material here — unusual, and worth leaning into: most frontend candidates cannot talk about the compositor, requestAnimationFrame, or why transform beats top → interview prep.

The same concepts, per stack

Course conceptReactVueSvelte
Componentfunction returning JSXSFC.svelte file
Local stateuseStateref / reactive$state (runes)
Derived valuecompute in rendercomputed$derived
Side effectuseEffectwatchEffect$effect
Ambient valueContextprovide/injectcontext API
Reactivity modelre-run the componentfine-grained proxiescompiled fine-grained

That last row is the real difference. React re-runs your whole component function and diffs; Vue and Svelte track dependencies precisely and update only what changed. It’s why React needs memo and the others largely don’t → the React model.

The filing rule

  • True whether you use React, Vue or Svelte? → a numbered section in the course
  • How one stack does it? → here
  • How it went in one of my projects? → projects/
↑ Back to Frontend