Board / script / camera / recorder
PRESENTER WORKSPACE / DESKTOP WEB
Excalicord
Bringing whiteboard, script, references, camera, recording frame, and project sync into one desktop explainer workspace.
- Role
- Product designer and design engineer (recording workflow / GitHub sync)
- Time
- 2026 · production prototype, ongoing
- Platforms
- Desktop Web / React / Excalidraw / GitHub
The canvas holds ideas; the workspace makes them explainable, recordable, and maintainable.
01 / Context
Not another whiteboard
The real scenario is drawing while explaining, with scenes, script, references, camera, and recording active together. Individual tools exist; the workflow does not.
The main canvas stays clear while script, references, camera, and recording frame enter on demand.
02 / Framing
Turn window switching into spatial organization
The product boundary follows the job of explaining something, not a generic canvas feature list.
Frame / explain / record / sync
The problem was not missing tools, but an explainer flow broken across windows.
03 / Decision
The canvas is the stage; support layers can leave
- Scenes, teleprompter, reference panel, camera bubble, and recording frame enter only when needed.
- Desktop-first, without pretending the recording workflow belongs on mobile.
Switchable frames
Speaking rhythm
External context
Presenter presence
Visible boundary
Support layers orbit the explaining action and remain hideable and focusable.
04 / Flow
From explaining clearly to keeping the work
Frame → Explain → Record → Sync turns a live explanation into a project that can be edited, restored, and reused.
From framing to a project that remains editable
The explainer produces not only video, but scenes and a maintainable project.
05 / Recovery
Sync is not an upload button
GitHub configuration, push, pull, restore, and stale-client protection together define recoverability.
Private sandbox / stale-client conflict protection
A real private sandbox verifies push, pull, restore, and stale-client conflict protection.
06 / Delivery
Release claims need layers
Local tests and the production canary provide strong evidence. Preview reachability was blocked, so production success is not presented as universal infrastructure health.
Tests, build, browser smoke, and production canary passed; preview reachability remains a separate gap.