Accessibility and SEO
Accessible names, roles and keyboard paths; contrast and motion preferences; and the crawlability signals that make a document indexable and understandable.
Accessible names, roles and keyboard paths; contrast and motion preferences; and the crawlability signals that make a document indexable and understandable.
How a Vue application is assembled: component communication, router guards, Pinia stores, composables, and the server rendering pipeline that Nuxt adds on top.
How a declaration wins: origin and importance, cascade layers, the specificity triple, inheritance keywords, and custom properties that pass through the whole tree.
The document tree, the seven content models, the elements that carry meaning, global attributes and the metadata that decides encoding, viewport and language.
The document object model as a programming surface: node types, query and mutation APIs, the capture and bubble flow, delegation, observers and shadow roots.
Native data collection: the twenty-two input types, constraint validation, labels and grouping, the submit encoding path, and FormData at the boundary.
Box model and box sizing, formatting contexts, positioning and stacking, then flex for one axis and grid for two, with the auto-sizing rules that explain the odd results.
Elements, components and fibers: the render and commit phases, how keys decide identity, where effects run, and what Strict Mode, Suspense and server components change about all of it.
How an address becomes a document: navigation steps, the History API, back-forward cache, Fetch options, CORS preflight, and the HTTP cache headers that decide reuse.
From bytes to pixels: parsing, the render tree, layout, paint and compositing, which properties trigger which stage, and the long task and layout thrash that break the frame budget.
Viewport units, media and container queries, fluid type with clamp, responsive images, and the transition and animation rules that keep motion cheap and optional.
Where each kind of state belongs: local, lifted, context, external store, URL and server cache; how subscriptions stay tear-free; and how races, invalidation and optimistic updates decide correctness.
Svelte compiles components into direct DOM operations: runes for state, derived and effects, the legacy assignment model, and the SvelteKit file conventions around them.
Proxy-based dependency tracking: ref and reactive, computed caching, watch flush timing, batched updates in a microtask, and what the template compiler does before render.
Cookies, local and session storage, IndexedDB and the cache API: scope, lifetime, quota, eviction, and the one decision that matters most, where a session token lives.