🏗️ Architecture: How should libs-renderable templates be structured for Angul...

Date: 2026-01-16
Time: 20:50:31 UTC
Session: editor2-48.4
Agent: angular
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How should libs-renderable templates be structured for Angular + Flutter support?

Task: Session 48: Create libs-renderable structure

🎯 Decision Made

Chosen:

Single library with platform-specific folders (src/angular/, src/flutter/, src/shared/)

Options Considered:

1. Separate Angular and Flutter libraries
2. Single library with platform-specific folders
3. JSON-driven configuration with platform adapters

💭 Reasoning

Each template has: (1) shared/manifest.ts - platform-agnostic metadata and configuration, (2) angular/ - Angular standalone component with signals and CSS, (3) flutter/ - JSON widget definition that Flutter apps can consume. This keeps related code together, allows shared interfaces, and makes it easy to add new templates. The Flutter JSON schema can be parsed by a Flutter app to dynamically render layouts.

📁 Files Involved

• libs/libs-renderable/shared/models/layout-template.interface.ts
• libs/libs-renderable/layout-templates/split-sidebar/src/angular/split-sidebar-layout.component.ts
• libs/libs-renderable/layout-templates/split-sidebar/src/flutter/split-sidebar.widget.json

🔗 Related

• Decision ID: dev_1768596631390_wos1n52
• Session: 48
• Workspace: editor2

Auto-generated by MCP Smart Consolidation