You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey 👋
First off, great project! I've been scouring for a markdown-slide generator, and am on the verge of just using Reveal.
From my perspective, this has the following inherent trade-off:
Either the slides have to be written in html
Or they can be written in markdown, but this has to be rendered client-side
I was hoping someone had written a bridge between the two, rendering offline but then presenting with all the goodies Reveal, as a mature reasonably mature project offers.
I can see you've come close, but decided to essentially roll-your-own "Reveal-like" system.
So this is both a question and possibly a feature request:
Why did you decide to create your own Reveal-like client-side code and what would you think about instead switching to something that just does the markdown rendering and then embeds that in Reveal?
The text was updated successfully, but these errors were encountered:
Soo I guess I'm suggesting a merge between these two strategies - I prefer the idea of offline rendering (why make the client machine do the "heavy lifting"?), but at the same time I see the merit in integrating with a js-framework like reveal-js instead of a roll-your-own. Thoughts?
Hey 👋
First off, great project! I've been scouring for a markdown-slide generator, and am on the verge of just using Reveal.
From my perspective, this has the following inherent trade-off:
I was hoping someone had written a bridge between the two, rendering offline but then presenting with all the goodies Reveal, as a mature reasonably mature project offers.
I can see you've come close, but decided to essentially roll-your-own "Reveal-like" system.
So this is both a question and possibly a feature request:
Why did you decide to create your own Reveal-like client-side code and what would you think about instead switching to something that just does the markdown rendering and then embeds that in Reveal?
The text was updated successfully, but these errors were encountered: