What problem does it solve?
Existing HTML presentations built with frameworks like Reveal, Marp, or custom JavaScript are locked into their runtime and cannot be edited as native slide documents. This Skill migrates them into editable, self-contained bento/slides .bento.html files while preserving content, layout, visual identity, and interaction semantics.
Core Features & Use Cases
- Faithful Migration Workflow: Analyzes both source files and the rendered presentation in a browser, then rebuilds each object as native bento text, shapes, images, svg, tables, charts, or media rather than wrapping the HTML.
- Per-Object Conversion Strategy: Chooses native, hybrid, or rasterized treatment per element, and maps click builds, hover states, nonlinear navigation, and transitions to bento slide states, links, and morphs.
- Fidelity Ledger and QA: Tracks every carried, approximated, and dropped item, then validates output with window.bento.validate(), real text measurement, and slide-by-slide visual comparison.
- Use Case: You have a Reveal.js conference talk with fragment build steps and custom fonts. Use this Skill to convert it into a single offline .bento.html deck where text and shapes remain editable, with a report of anything approximated or lost.
Quick Start
Use $html-to-bento-slides to convert my HTML presentation folder into an editable bento/slides file and report any content that could not be preserved.
