In memory of Saber Rastikerdar — creator of · Vazirmatn, the open typeface he gave the Persian web and asked nothing for.
Skip to content

Frontend Architect — Learning Path

An engineer responsible for the structure, boundaries, and long-term evolution of a frontend system.

Level: Advanced · Required: 151 articles (~35.4 h) · Optional: 29 articles (~7.9 h)

Difficulty of required articles: Foundational 3 · Intermediate 102 · Advanced 40 · Staff 6.

Follow the sections in order. Articles link into docs/; each shows its difficulty and estimated reading time. Full prerequisites for any article are in its domain's graph.json (see GRAPH.md).

Milestones

  1. Define module boundaries and dependency direction that scale
  2. Choose rendering and data-fetching boundaries deliberately
  3. Design API contracts and a versioned design system
  4. Structure a monorepo with package and build architecture
  5. Record and defend architectural decisions

Expected skills

By completing the required articles you should be able to:

  • System structure, boundaries, and dependency management
  • Rendering, state, and data architecture
  • Design-system and package architecture
  • Trade-off analysis and technical direction

Required articles

Frontend Architecture

State Management

Data & Server State

API Design & Contracts

Rendering Architectures

Routing

Design Systems

Package Architecture

Build Systems & Tooling

Developer Experience & Workflow

TypeScript

Engineering Practices

Systems Thinking & Leadership

Optional articles

Security

Performance Engineering

Delivery & Infrastructure

Observability & Reliability


← All learning paths · Knowledge Map · Dependency Graph

Peer-reviewed engineering decisions · MIT licensed