docs(webui): record HTML partial split decision
This commit is contained in:
1 parent
458779e809
commit
e03dcaa183
1 file changed
+27
@@ -0,0 +1,27 @@
|
||||
# `index.html` Partial Split Decision
|
||||
|
||||
## Current State
|
||||
|
||||
- `webui/index.html`: 1249 lines (current snapshot)
|
||||
- Existing static loading chain is stable after CSS/JS split tasks.
|
||||
|
||||
## Decision
|
||||
|
||||
Do **not** split `index.html` in the current execution plan.
|
||||
|
||||
Reason:
|
||||
- Current page still relies on static ordering and direct DOM presence for startup wiring.
|
||||
- Immediate partialization would introduce runtime behavior changes (injection/fetch/build) outside Task 13 scope.
|
||||
- The active goal is to continue safe large-file decomposition without regressing existing WebUI behavior.
|
||||
|
||||
## If We Need to Split Later
|
||||
|
||||
Pick one strategy explicitly before implementation:
|
||||
|
||||
1. Server-side partial injection in `gui/web_gui.py`
|
||||
2. Client-side fetch of static partial fragments
|
||||
3. Build-time HTML generation
|
||||
|
||||
## Recommendation
|
||||
|
||||
Prefer **server-side partial injection** if we want to reduce HTML size while keeping one-page delivery and avoiding additional client bootstrap complexity.
|
||||
Reference in new issue
Block a user