I have a grand vision of using polylux to export a fully featured, standalone HTML presentation. Impress.js is a lightweight, currently maintained, and popular library that could make it happen. It supports subslides, animations, and more.
In contrast to pdfpc, the presentation can be viewed in the browser compared to a niche downloaded application, and impress.js gets much more community support.
Sli.dev and reveal.js are other potential candidates, but are much more complex frameworks that require node.js for deeper configuration and hundreds of MB of installs. So impress.js is a nice lightweight alternative.
What changes need to happen on polylux?
common intermediate representation of metadata that can be shared between pdfpc, impress, and potential additional integrations. Things like representing slide transitions, subsides, etc.
script that converts SVG slides + impress template into a folder with index.html
The latter is dead simple -- I've already done this in a proprietary code base with generic svgs; it takes <100 lines of python + Django template. The first point (common representation of slide metadata) would need a bit more community consideration and feedback to do well.
I'd love to know your thoughts! Would you support a PR along these lines?
I have a grand vision of using polylux to export a fully featured, standalone HTML presentation. Impress.js is a lightweight, currently maintained, and popular library that could make it happen. It supports subslides, animations, and more.
In contrast to pdfpc, the presentation can be viewed in the browser compared to a niche downloaded application, and impress.js gets much more community support.
Sli.dev and reveal.js are other potential candidates, but are much more complex frameworks that require node.js for deeper configuration and hundreds of MB of installs. So impress.js is a nice lightweight alternative.
What changes need to happen on polylux?
index.html
The latter is dead simple -- I've already done this in a proprietary code base with generic svgs; it takes <100 lines of python + Django template. The first point (common representation of slide metadata) would need a bit more community consideration and feedback to do well.
I'd love to know your thoughts! Would you support a PR along these lines?