Presentor
Development notes

Polishing editing and presenting

September 6, 2026 · Experience notes

The editor keeps slides, canvas, inspector and notes in predictable places.
The editor keeps slides, canvas, inspector and notes in predictable places.
The presenter console shows current and next slides, notes and timing.
The presenter console shows current and next slides, notes and timing.

Embedding a video is only part of presenting it. The speaker needs seeking, pause and volume while the audience needs a clean frame. Audio should play from one output. Presenter and audience tabs exchange commands and playback status.

Notes belong in the editing workflow as well as the console. The canvas now has a notes area, serialized as presenter-notes in Markdown. Per-slide budgets are separate from total timing. Red overtime grows across the budget line rather than hiding behind a progress bar stuck at 100%.

Layout checks identify evidence that an author can inspect. Bounds can be measured; aesthetic quality cannot be reduced to a trustworthy score. Near alignment, font outliers and text-frame overlap are separate suggestions.

The global canvas, object timelines, branch history, realtime merging and speech rehearsal remain explicit design work. Proposed behavior is not documented as finished functionality.

Groups need an intermediate state. The first double-click selects a member; the next edits its text. Leaving media interaction keeps the object selected. Font size and weight stay in the inspector while OpenType and font synthesis live in an advanced panel. Corner radius and smoothing are separate; the canvas guide lets readers change them while comparing the source and shape.