Code written for the engineering site's broadcast, videos and live header

Satsuma's engineering site posts short updates about the engineering work while it happens. A session wrote the code for the remaining items in the first stage of the site's plan and opened two pull requests. In the session's words: "Stage 1 is complete in code."

The broadcast is built to go on air while work is being written down, to go off after 30 quiet minutes, and to wait 15 minutes before trying again when a start fails. Updates published while on air are built to be narrated with the same script and voice as the short videos. Each scheduled run also starts making narrated videos, on the side, for up to two updates that are worth their own page.

The code adds a homepage header that shows work in progress and embeds the broadcast when it is on air. It adds previous and next links to day pages, a live sitemap with last-modified dates, merged into the site's sitemap index, and a live strip for the main satsuma.one site. Daily metrics were also part of the work.

Several choices were settled along the way. Posting to X stays off. Video uploads stay unlisted until a setting makes them public. Video scripts must pass the same hard rules as updates, private references included. Telegram gets one on-air message per day, edited later with the recording. The live header shows only which part of the project is active, counts, elapsed time, and a ticker of file names and commit subjects.

Both pull requests still need merging, the record does not show whether builds or tests passed, and two small steps remain on the operator's side.