Growth Notes

Web Development MOC

Tags: web-dev map

Web Development MOC

Date: 2026-08-16

The entry point to the domain. Eight areas, ordered ground upwards — each has its own map in MOCs/, kept clear of the content folders.

This hub owns no notes; the area maps in MOCs/ do. Where a note could sit in two areas, the filing rules in CLAUDE.md settle it.

The spine

Read these in order if you read nothing else. Each is load-bearing for a lot of the rest.

  1. How the Web Works — DNS, TCP, TLS, HTTP, response. The whole round trip, once, properly
  2. HTTP Semantics — methods, status codes, headers, caching directives
  3. The Rendering Pipeline — parse, style, layout, paint, composite. Why some changes are cheap
  4. The Event Loop — one thread, a queue, and why “async” doesn’t mean “parallel”
  5. Semantic HTML — the document model accessibility, SEO and default behaviour derive from
  6. The Cascade and Specificity — the part of CSS behind every “why won’t this apply”
  7. Rendering Strategies — SSR, SSG, ISR, CSR, streaming, islands
  8. Caching Strategies — where a copy is allowed to live, and how you invalidate it
  9. Core Web Vitals — the measurable definition of “fast enough”
  10. Feature Flags — decoupling deploy from release, which changes how everything ships
  11. Libraries, Frameworks and Toolkits — who owns the control flow, and what adopting each kind of thing costs to undo

The areas

  • Foundations MOC — language-independent CS — data, memory, networking, storage, security, systems thinking
  • Browser MOC — the runtime itself — the document, rendering, execution, storage, the security and privacy model
  • Languages MOC — one section each: JavaScript, TypeScript, CSS, PHP, C#, Liquid, SQL
  • Frameworks MOC — what a framework adds on top of the language, and which of its magic is just the language
  • Design Systems MOC — primitives, components, and the governance problem attached to both
  • Architecture MOC — system shape — rendering, application structure, release, discoverability, change over time
  • Performance MOC — measuring it, loading, assets, caching, runtime, and holding the line
  • Tooling MOC — version control, dependencies, build, quality, testing, CI, the working environment

Borders

Filed in other domains, needed constantly here. Cross-references within Web Development are no longer borders — they’re internal links.

Graph View

Backlinks