Architecture: What features should dock-layout have to serve as both IDE l...

Documentation for Sessions

🏗️ Architecture: What features should dock-layout have to serve as both IDE l...

📋 Decision Context

Question:

What features should dock-layout have to serve as both IDE layout manager AND content creation tool?

Task: Not specified

🎯 Decision Made

Chosen:

Multi-mode dock system with: (1) Highly configurable per-instance, (2) Development vs Renderable states, (3) Pixel-perfect responsive design, (4) Event system, (5) Layout Builder API, (6) Size constraints, (7) Watermark/empty state

Options Considered:

IDE-only dock system
Content-creation dock system
Dual-purpose with modes

💭 Reasoning

User vision: dock-layout serves TWO purposes - as IDE panel manager AND as content creation tool for space-builders. Development state allows customization, Renderable state shows final output. Configuration must be granular (tabs vs titles, closable vs locked, settings visibility). Must work on mobile. This elevates dock-layout from utility to core platform feature.

📁 Files Involved

libs/libs-ui/dock-layout/src/lib/models/dock-config.model.ts
libs/libs-ui/dock-layout/src/lib/services/dock-layout.service.ts

🔗 Related

Decision ID: dev_1768251152878_ufoo0c8
Session: 39
Workspace: editor2

Auto-generated by MCP Smart Consolidation