Goal: a repeatable demo asset for showing ElevareAI off — a written walkthrough script, plus captured screenshots compiled into an mp4 and a gif.
Scope:
- A demo script (
_docs/DEMO-script.md or scripts/): the ordered click-through — log in as demo@elevare.ai, ask a QA question (show KaTeX math rendering), generate practice, show goals/progress — with the narration/beats for each step. Reuse the pre-demo warm-up note (curl /health for free-tier cold start).
- A capture step: script/tooling to take the screenshots in order (headless browser or manual capture checklist), stored in a known dir.
- A build step: turn the ordered screenshots into
demo.mp4 (slideshow with per-frame timing) and demo.gif (looping, web-embeddable). Prefer ffmpeg (mp4) + ffmpeg/gifski (gif); document the exact commands so it's reproducible.
Open questions to resolve when picked up:
- Live-recording (real screen capture of the running app) vs. stitched still-screenshots? Title framing implies stitched stills — confirm.
- Where the assets live (committed to repo vs. release artifact vs. gitignored
_docs/local/); mp4/gif can be large — decide before committing binaries.
- Automated capture (Playwright/chrome-devtools against the live Render URL or a local run) vs. a manual screenshot checklist.
Done when: running the documented steps produces demo.mp4 + demo.gif from the current app, and the walkthrough script matches what the frames show.
Definition of Done: follows the working process (branch → PR Closes #<this> → gates → CI). Binary-asset handling decided explicitly (not silently committed).
Goal: a repeatable demo asset for showing ElevareAI off — a written walkthrough script, plus captured screenshots compiled into an mp4 and a gif.
Scope:
_docs/DEMO-script.mdorscripts/): the ordered click-through — log in asdemo@elevare.ai, ask a QA question (show KaTeX math rendering), generate practice, show goals/progress — with the narration/beats for each step. Reuse the pre-demo warm-up note (curl/healthfor free-tier cold start).demo.mp4(slideshow with per-frame timing) anddemo.gif(looping, web-embeddable). Prefer ffmpeg (mp4) + ffmpeg/gifski (gif); document the exact commands so it's reproducible.Open questions to resolve when picked up:
_docs/local/); mp4/gif can be large — decide before committing binaries.Done when: running the documented steps produces
demo.mp4+demo.giffrom the current app, and the walkthrough script matches what the frames show.Definition of Done: follows the working process (branch → PR
Closes #<this>→ gates → CI). Binary-asset handling decided explicitly (not silently committed).