Preserve initial frontend pattern language research scaffold

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-24 07:55:34 +02:00
parent 017ad6ea17
commit 2a5dabdc85
43 changed files with 2030 additions and 1 deletions

View file

@ -0,0 +1,18 @@
# DocumentWeb
Status: research stub
## Intent
Describe **DocumentWeb** as a configuration of independent frontend patterns rather than as a monolithic architectural style.
## To establish
- context
- dominant forces
- pattern configuration
- variants
- consequences
- failure modes
- known implementations
- sources

18
architectures/Islands.md Normal file
View file

@ -0,0 +1,18 @@
# Islands
Status: research stub
## Intent
Describe **Islands** as a configuration of independent frontend patterns rather than as a monolithic architectural style.
## To establish
- context
- dominant forces
- pattern configuration
- variants
- consequences
- failure modes
- known implementations
- sources

View file

@ -0,0 +1,18 @@
# LocalFirst
Status: research stub
## Intent
Describe **LocalFirst** as a configuration of independent frontend patterns rather than as a monolithic architectural style.
## To establish
- context
- dominant forces
- pattern configuration
- variants
- consequences
- failure modes
- known implementations
- sources

View file

@ -0,0 +1,18 @@
# Microfrontends
Status: research stub
## Intent
Describe **Microfrontends** as a configuration of independent frontend patterns rather than as a monolithic architectural style.
## To establish
- context
- dominant forces
- pattern configuration
- variants
- consequences
- failure modes
- known implementations
- sources

24
architectures/README.md Normal file
View file

@ -0,0 +1,24 @@
# Named Architectures
Named frontend architectures are represented here as **configurations of patterns**.
This prevents architectural labels from becoming indivisible categories.
Initial candidates:
- Document Web
- SPA
- Islands
- Server Components
- Microfrontends
- Local-First
Each file should eventually answer:
- What problem family does the architecture address?
- Which patterns are essential?
- Which are optional?
- Which forces make the configuration attractive?
- Which forces make it unattractive?
- Which architectural variants exist?
- Which technologies commonly implement it?

18
architectures/SPA.md Normal file
View file

@ -0,0 +1,18 @@
# SPA
Status: research stub
## Intent
Describe **SPA** as a configuration of independent frontend patterns rather than as a monolithic architectural style.
## To establish
- context
- dominant forces
- pattern configuration
- variants
- consequences
- failure modes
- known implementations
- sources

View file

@ -0,0 +1,18 @@
# ServerComponents
Status: research stub
## Intent
Describe **ServerComponents** as a configuration of independent frontend patterns rather than as a monolithic architectural style.
## To establish
- context
- dominant forces
- pattern configuration
- variants
- consequences
- failure modes
- known implementations
- sources