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

How to build a scroll-driven deck from a concept in one afternoon with Awesome HTML Scrolline Deck

Start a deck from a concept pack, write beats in deck.yaml, and preview it in the browser.

  • Top pick
  • Content
  • Intermediate
  • 1 hour
  • From the README
  • Any agent

Who it is forAn analyst or presenter who has a quarterly review, market update or pitch to show and wants a scroll-driven deck instead of slides.

The problemSlide tools cut from one slide to the next, so the audience loses track of the numbers and objects that carry the story.

The outcomeA working local deck at a dev URL, built from a concept pack, with stops and timings computed in node.

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 deck -- new my-review --concept data
  6. Write your beats in decks/my-review/deck.yaml using the beat format in the README.
  7. npm run deck -- plan my-review
  8. npm run dev, then open http://localhost:5173/decks/my-review/ (inferred from the sample URL pattern)

Prompt for your agent

In the awesome-html-scrolline-deck repo, check out branch v2, run npm install, then create a deck named <deck-name> with `npm run deck -- new <deck-name> --concept data` and write its beats in decks/<deck-name>/deck.yaml from <source-brief>. Run `npm run deck -- plan <deck-name>` and report the stops and timings it prints. Verify that the plan command finishes without errors before you stop.

Caveat. The example decks are in Korean, and the README documents only the data concept as a starting point for real-data reviews.

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