🏗️ Architecture: Is it possible to maintain Angular for editing/development b...

Date: 2026-01-23
Time: 23:32:39 UTC
Session: editor2-63.69
Agent: angular
Confidence: 88%
Status: ✅ Documented

📋 Decision Context

Question:

Is it possible to maintain Angular for editing/development but deploy as pure static HTML?

Task: Not specified

🎯 Decision Made

Chosen:

Possible via Adaptive Static Export - AI decides per-page

Options Considered:

1. Not possible - Angular requires runtime
2. Possible via Angular prerender (but still ships bundle)
3. Possible via Adaptive Static Export - AI decides per-page

💭 Reasoning

Key insight: Page Builder already has JSON representation (WidgetInstance[]). This is the source of truth, not Angular components. Therefore: JSON can output EITHER Angular (for editing, complex pages) OR pure static HTML (for landing pages). Implementation: StaticWidgetRendererService converts WidgetInstance[] to HTML. ThemeCSSExtractor extracts theme-system to pure CSS variables. PageExportAnalyzer (AI) decides per-page: pure-static (0 JS), enhanced-static (minimal JS for accordions/forms), angular-islands (mostly static + micro-bundle for 1-2 complex widgets), full-angular (many interactive widgets). This is groundbreaking because: Astro does this for React/Vue but NO Angular support. Webflow exports static but no custom code. Angular prerender ships full 150KB+ bundle. GoGrab would be ONLY tool with visual builder → pure static HTML for Angular. Challenges: Dual rendering paths (maintenance overhead), interactive widgets need JS (forms, tables). Mitigation: Use native HTML features (