There are plenty of HTML slide decks out there. But I believe this one is doing something different. It uses what I'm calling an "evolving-scene model": one shared diagrammatic canvas where a stable set of entities morphs across named steps. Boxes appear, move, connect, collapse, and re-label as the talk develops. The continuity between steps is the key differentiator.
And I came up with that model because that's basically how my brain works. I tend to understand things by building a map of concepts, then visualizing how they connect and layer on top of each other like building blocks. A "normal" slide deck typically treats each slide as a distinct departure from the previous one. Yes, PowerPoint has animations, but "evolving scenes" are challenging to make at best.
But once I had this method working, I knew I was going to use it again. So I turned the creation process into a skill: /and-scene:presentation. It interviews you about the topic, visual style, content, and what should happen visually. Then it scaffolds the browser app if needed, codes up the presentation, and verifies the visual styling for you.
The README has a couple of videos of example presentations too, which is probably the fastest way to get a feel for what it can do.
Disclosure: I’m the author. It’s free and MIT licensed, with no paid tier.
There are plenty of HTML slide decks out there. But I believe this one is doing something different. It uses what I'm calling an "evolving-scene model": one shared diagrammatic canvas where a stable set of entities morphs across named steps. Boxes appear, move, connect, collapse, and re-label as the talk develops. The continuity between steps is the key differentiator.
And I came up with that model because that's basically how my brain works. I tend to understand things by building a map of concepts, then visualizing how they connect and layer on top of each other like building blocks. A "normal" slide deck typically treats each slide as a distinct departure from the previous one. Yes, PowerPoint has animations, but "evolving scenes" are challenging to make at best.
But once I had this method working, I knew I was going to use it again. So I turned the creation process into a skill: /and-scene:presentation. It interviews you about the topic, visual style, content, and what should happen visually. Then it scaffolds the browser app if needed, codes up the presentation, and verifies the visual styling for you.
The README has a couple of videos of example presentations too, which is probably the fastest way to get a feel for what it can do.
Disclosure: I’m the author. It’s free and MIT licensed, with no paid tier.
[dead]