Architecture Visual Map
Why this page matters
This book is intentionally broad. Use this map to understand how the parts connect before choosing a path.
Book flow
Artifact progression
Specialty paths
| Specialty | Read | Produce |
|---|---|---|
| performance architect | Part II, Part III, Part VI, performance hub | route budget, profiling note, RUM plan |
| design-system architect | Part 0, Part IV, Part VII, design-system hub | token taxonomy, API review, adoption scorecard |
| security/reliability architect | Part 0, Part II, Part VIII, security/privacy hub | threat model, third-party register, degradation matrix |
| GenUI architect | Part 0, Part III, Part VIII, Part XIII, GenUI hub | registry contract, eval matrix, tool-risk policy |
| architecture leader | Part I, Part IX, Part XII, rubrics | operating model, review cadence, exception register |
Review checklist
- Can you explain which part answers which architecture question?
- Do you know which artifact each learning path should produce?
- Are you using a capstone to turn reading into evidence?
- Are you revisiting Part 0 when later chapters expose a weak foundation?
Exercises
- Choose one specialty path and list the artifacts you will produce.
- Pick one capstone and trace the parts that prepare you for it.
- Identify which part of the book answers your current hardest frontend architecture problem.
Source lens
This page is a navigation artifact over learning paths, hubs, reference architectures, capstones, rubrics, and review packets.