DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to export a finished deck to an MP4 video with Awesome HTML Scrolline Deck

Render a deck's paused timeline to a 1920x1080 MP4 for sharing without a browser.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA presenter who must send a deck as a video file for a webinar, an event screen or an inbox that cannot run the web version.

The problemA scroll-driven deck does not work in a plain video player, and a screen recording would drop the scrubbing and timing.

The outcomeAn MP4 file at out/export/<deck-id>.mp4 that shows the same frames as the browser version.

What you need first

  • Node.js 22 or newer
  • git
  • ffmpeg, only if you cut frame sequences for scrubbed video
  • A Pexels or Pixabay API key in .env, only if you add stock video

Steps

  1. git clone https://github.com/gongnyang/awesome-html-scrolline-deck.git
  2. cd awesome-html-scrolline-deck
  3. git checkout v2
  4. npm install
  5. npm run export -- rail-ai-decade --dry-run
  6. npm run export -- rail-ai-decade

Prompt for your agent

In the awesome-html-scrolline-deck repo on branch v2, run `npm run export -- <deck-id> --dry-run` to print the timeline map, then run `npm run export -- <deck-id>` to render the MP4. Report the path of the output file, which should be out/export/<deck-id>.mp4. Verify that the file exists and that its resolution is 1920x1080 as the README describes.

Caveat. The export uses the HyperFrames CLI fetched by npx, so the first run needs network access, and the README does not state how long a render takes.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page