🏗️ Architecture: How to enable platform builders (clients) to deploy both int...

Date: 2026-01-23
Time: 21:07:17 UTC
Session: editor2-63.64
Agent: angular
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How to enable platform builders (clients) to deploy both interactive SPAs and SEO-perfect static landing pages from the same visual builder?

Task: Design groundbreaking static export system for multi-tenant platform builder

🎯 Decision Made

Chosen:

PWC: Page-to-WebComponent with Declarative Shadow DOM - converts Page Builder output to static HTML with native Web Components, enabling zero-framework runtime for landings while keeping Angular SPA for dashboards

Options Considered:

1. Angular-only approach (prerendering for SEO)
2. Static HTML only (lose interactivity)
3. PWC: Page-to-WebComponent with Declarative Shadow DOM (groundbreaking hybrid)
4. Islands architecture with partial hydration

💭 Reasoning

This approach is groundbreaking because: (1) No existing platform converts visual builders to Web Components with Declarative Shadow DOM, (2) Leverages existing infrastructure (Page Builder, Widget System, Theme System), (3) Each client gets dual deployment: {client}.gograb.space (Angular SPA) + {client}.com (PWC Static), (4) AI can orchestrate which export format based on vibe commands, (5) Standards-based (W3C Web Components), future-proof, (6) Perfect SEO without JS, (7) Theme system CSS variables work natively in Web Components

📁 Files Involved

• libs/libs-structural/pwc-generator/
• libs/libs-structural/page-builder/
• libs/libs-ai/gograb-ai/src/lib/services/vibe-coding-orchestrator.service.ts
• apis/backend-api/src/app/cloudflare/cloudflare-pages.service.ts
• libs/libs-space/deployment-engine-lib/

🔗 Related

• Decision ID: dev_1769202437455_foxjq6d
• Session: 63
• Workspace: editor2

Auto-generated by MCP Smart Consolidation