Mergerie
Contents

Recording a presentation video (ready for YouTube)

This page is generated from docs/guide.en.md · Edit this page on GitLab

npm i -D playwright && npx playwright install chromium   # once
npm run record:demo                                       # both languages, one after the other
npm run record:demo -- --lang=en                          # → demo-recordings/mergerie-demo-en.webm
npm run demo:gif                                          # → docs/demo.gif (the README one)

scripts/record-demo.js is self-contained: it launches the app in demo mode itself, waits for port 4319, and drives a Chromium that records, in 1920×1080, a guided tour with a visible fake cursor, intro/outro cards and explanatory captions synchronised with each screen — then shuts everything down cleanly (closing the context flushes the video). The route: Reviews → a scored report → the version selector v1 → v2 → v3 (a progression from 5.8 to 8.4) → resolution tracking → AI Dev (a session linked to its MR, a question asked by the AI) → Notes (morning brief, todos, pages) → Jira → Git (the branch explorer) → Links (grid, health, global palette) → Docker (.env drift + live logs) → Stats → the navigation column folding away. The .webm produced uploads straight to YouTube.

Both languages are recorded one after the other against the same demo server, and the language is set in both places the app reads it from — localStorage for the interface, and config.language in the database for messages coming from the server. Setting only one yields an English video punctuated with French sentences.

Dropdowns are redrawn inside the page for the duration of the recording. A native <select>'s list is drawn by the operating system, outside the page: the camera films the page, so it never showed up. You saw the cursor click, then the value change on its own — the least intelligible gesture in the video. The stand-in is built from the element's real options; it is a recording device, living in scripts/record-demo.js and nowhere else.

The README's GIF comes from the same recording: npm run demo:gif. Its settings (6 fps, 640 px, 32 colours, palette computed on the video) are tuned to stay under ~4.5 MB — a file GitHub reloads on every visit to the landing page — without making the interface unreadable. The palette dropped from 64 to 32 colours the day the tour gained the Agents tab and the dark theme: at 64, the same GIF weighed 6.7 MB. They live in scripts/demo-gif.sh rather than in a command to be rediscovered: working them out again costs half an hour and yields a file twice too heavy.