Skip to main content

Source-Backed Reading Notes

Why this page matters

Architects should know which external sources support which decisions. This page maps stable, high-signal sources to the book's architecture topics.

Source map by topic

TopicPrimary sources to consultUse in the guide
browser runtimeMDN event loop, rendering, performance APIsPart II runtime, Part VI performance
Web Vitalsweb.dev Core Web Vitals, INP, LCP, CLS guidancebudgets, profiling, funnel capstone
accessibilityW3C WAI, WCAG 2.2, ARIA Authoring PracticesPart VIII, design-system contracts
browser securityOWASP Cheat Sheets, MDN CSP/CORS, web platform security docsthreat models, CSP, third-party reviews
React renderingReact docs for Server Components, Suspense, memoization/compiler guidancePart III rendering boundaries
Next.js renderingNext.js rendering, caching, routing, server actions documentationroute strategy and cache discussions
architecture decisionsADR examples, fitness functions, evolutionary architecture ideasPart I and Part XII artifacts
team architectureTeam Topologies, platform engineering writingPart IX operating model and ownership
design systemsW3C accessibility, design token community reports, component API practicePart VII and design-system reference
AI/GenUI safetymodel eval, tool authorization, RAG citation, prompt injection guidancePart XIII and GenUI reference

How to add source notes to a chapter

Use this compact format:

## Source lens

- Source: what the source is authoritative for.
- Decision use: which architecture choice it supports.
- Limitation: where the source does not decide the product tradeoff.

Source-quality rules

  • Prefer primary documentation for platform and framework behavior.
  • Prefer standards bodies for accessibility and browser behavior.
  • Prefer security organizations for threat categories and mitigations.
  • Treat blog posts as examples unless they include reproducible data or official guidance.
  • Do not cite a source as authority for a tradeoff it does not actually decide.

Review checklist

  • Does the source support the decision being made?
  • Is the source stable enough for a durable chapter?
  • Is the chapter clear about where judgment is still required?
  • Are source notes concise enough to maintain?

Exercises

  1. Add a source lens to one legacy chapter using this format.
  2. Identify one chapter that needs a primary source instead of a secondary article.
  3. Write one limitation statement for a framework documentation source.

Source lens

This page is the source-governance layer for Part XII citation standards, meta source map, and future guide maintenance.