32 lines
1 KiB
Markdown
32 lines
1 KiB
Markdown
|
# Frontend Architecture Compendium
|
||
|
|
|
||
|
|
## Purpose
|
||
|
|
|
||
|
|
Provide a continuously improving synthesis of the major ideas used to reason about frontend architecture.
|
||
|
|
|
||
|
|
The compendium explains schools of thought without treating any one of them as the canonical model.
|
||
|
|
|
||
|
|
## Initial chapters
|
||
|
|
|
||
|
|
1. From GUI architecture to web architecture
|
||
|
|
2. Navigation and the document web
|
||
|
|
3. Client/server authority
|
||
|
|
4. State management and unidirectional flow
|
||
|
|
5. Rendering and projection
|
||
|
|
6. Hydration, islands and resumability
|
||
|
|
7. Server components and streamed UI
|
||
|
|
8. Hypermedia-driven applications
|
||
|
|
9. Local-first and replicated frontends
|
||
|
|
10. Composition and feature slicing
|
||
|
|
11. Microfrontends and organizational boundaries
|
||
|
|
12. Accessibility, resilience and progressive enhancement
|
||
|
|
13. Performance as architecture
|
||
|
|
14. Frontend observability and recoverability
|
||
|
|
15. Pattern languages as a unifying representation
|
||
|
|
|
||
|
|
## Editorial rule
|
||
|
|
|
||
|
|
The compendium may explain technologies and historical movements in detail.
|
||
|
|
|
||
|
|
Canonical patterns should remain technology-independent whenever possible.
|