## DOCUMENTATION: Frontend Architecture Overview

[OSEH-svg]

Description
New contributors have no map of how the frontend is structured — which folders do what, how data flows from API to component, and where state lives. This creates a steep onboarding curve.

Tasks

• Create apps/web/docs/ARCHITECTURE.md.
• Cover: folder structure and conventions (app/, components/, hooks/, lib/, utils/), data fetching strategy (SWR vs server components), state management approach, and auth flow summary.
• Include a simple ASCII or Mermaid diagram of the request lifecycle.
  Acceptance Criteria
• A developer new to the repo understands the project structure within 10 minutes of reading this document.