53 lines
2.7 KiB
Markdown
53 lines
2.7 KiB
Markdown
---
|
|
id: LSN-0001
|
|
ticket: studio-docs-import
|
|
title: Assets workspace execution wave legacy lesson
|
|
created: 2026-03-26
|
|
tags:
|
|
- studio
|
|
- legacy-import
|
|
- assets-workspace
|
|
- event-driven-ui
|
|
---
|
|
|
|
## Context
|
|
|
|
Legacy import from `docs/studio/learn/assets-workspace-execution-wave.md`.
|
|
|
|
This lesson captures the didactic consolidation of the first `Assets` workspace execution wave after the original implementation slices had already been absorbed into Studio specs and learn material.
|
|
|
|
Relevant specs:
|
|
|
|
- `docs/studio/specs/1. Studio Shell and Workspace Layout Specification.md`
|
|
- `docs/studio/specs/4. Assets Workspace Specification.md`
|
|
|
|
## Key Decisions
|
|
|
|
### Assets workspace should remain asset-first, event-driven, and preview-first
|
|
|
|
**What:** The stable workspace model treats `Assets` as a real asset workspace, separates navigator projection from details rendering, routes routine UI ownership through typed events, and keeps sensitive mutations preview-first rather than refresh-heavy or modal-first.
|
|
**Why:** The original execution wave produced many local slices, but the enduring lesson is the ownership model: local redraws instead of workspace-wide refresh, didactic asset detail ordering, workspace-local review with shell-level lifecycle visibility, and semantically separate mutation feedback.
|
|
**Trade-offs:** This model requires more deliberate component boundaries and event routing, but it avoids monolithic redraw logic and keeps the UI easier to reason about as the workspace grows.
|
|
|
|
## Patterns and Algorithms
|
|
|
|
- Treat `Assets` as a real workspace with explicit `loading`, `empty`, `error`, and `ready` states.
|
|
- Keep navigator updates and selected-asset details updates independently owned.
|
|
- Use typed workspace events for local state flow instead of defaulting to `refresh()`.
|
|
- Keep activity at shell scope, while review and mutation reasoning stay inside the workspace.
|
|
- Reserve modal confirmation for high-risk commit boundaries; use inline preview as the default review surface.
|
|
|
|
## Pitfalls
|
|
|
|
- Treating `Assets` like a filesystem explorer with extra badges.
|
|
- Rebuilding navigator, details, and unrelated controls for row-scoped changes.
|
|
- Letting details sections depend on one monolithic selected-asset redraw.
|
|
- Using logs as the main explanation surface for mutations.
|
|
- Publishing shell activity without keeping workspace-local review visible.
|
|
|
|
## Takeaways
|
|
|
|
- The durable lesson from the first `Assets` execution wave is the ownership model, not the historical sequencing of implementation slices.
|
|
- Event-directed local redraw and preview-first mutation review are foundational Studio patterns for the asset workspace.
|
|
- Legacy source attribution: `docs/studio/learn/assets-workspace-execution-wave.md`.
|