Hi, thanks for maintaining deck.js.
deck.js is a solid choice when teams want full control over HTML presentations. One gap that still appears in some business and education workflows is this: after the HTML deck is finalized, the receiving side sometimes asks for an editable PowerPoint file instead of HTML.
A potentially useful companion workflow could be:
- export the deck to PDF or screenshots
- reconstruct that visual deck into an editable PPTX
- preserve text as actual text boxes and keep visual layers movable where possible
I'm working on an open-source project focused on exactly that post-processing problem:
Why I think this could be relevant for deck.js users:
- authors can keep the HTML-first workflow they like
- non-technical stakeholders still get a
.pptx they can edit in PowerPoint / WPS
- it creates a better bridge between web-native authoring and traditional presentation collaboration
If this sounds useful, I'd be happy to share a possible integration shape or prototype adapter.
Hi, thanks for maintaining
deck.js.deck.jsis a solid choice when teams want full control over HTML presentations. One gap that still appears in some business and education workflows is this: after the HTML deck is finalized, the receiving side sometimes asks for an editable PowerPoint file instead of HTML.A potentially useful companion workflow could be:
I'm working on an open-source project focused on exactly that post-processing problem:
Why I think this could be relevant for
deck.jsusers:.pptxthey can edit in PowerPoint / WPSIf this sounds useful, I'd be happy to share a possible integration shape or prototype adapter.