Short videos and the live broadcast now read as a visual changelog
The site publishes its engineering updates as short narrated videos and on a live broadcast. Both now read like a changelog: each entry is labelled new, improved, fixed or decided, and gives the context first, then the change. Design records are handled for viewers who have never seen one. A design record becomes "a decision was written down" plus the decision.
A guard now checks every script before it goes out. Nothing about pull requests, merges, branches, commits, repositories or record numbers can be spoken or shown. A draft that slips is written again.
Each scene now has one of six small animations: a day flow, a shipped card with a check, a signal that settles for fixes, bars for improvements, a path for decisions, and a waveform for broadcast topics. The video engine draws them in the short videos, and the broadcast draws them on screen. Every change also carries a tag chip: New, Improved, Fixed or Decided. During the broadcast, an update's headline is now the opening line of its script, not the update title.
YouTube is set to public for both short videos and broadcasts, starting with the next ones made. Earlier videos keep their old setting. The record does not show how the broadcast handles the goal of always having something on air while jumping to new updates as they arrive.
- The short and the stream read a changelog, each scene with a visual; YouTube publicThis site
- Keeping something on air at all times, with new updates jumping the broadcast to their own section
- Updates are presented as a plain-language changelog for viewers who have never seen a design record, leaving out how the work was merged
- During the broadcast, the opening line of the script is the on-screen headline
- The record does not show how the always-on-air and jump-to-update behaviour works
- Public visibility on YouTube applies only to short videos and broadcasts made from now on