search

wildfly-extras / wildfly-decks

Apache License 2.0
1 stars 4 forks source link

Consider migrating to reveal.js #10

Open jasondlee opened 6 months ago

jasondlee commented 6 months ago

We should consider migrating this from the old, apparently abandoned dzslides to the newer -- and maintained -- reveal.js. Reveal offers both the static version user here (i.e., no build required) or the more advanced server-based. I had a slide deck based on this project that I migrated to reveal, and the changes were minimal (e.g., slight change to the basic structure of index.html, and changing class="next" to class="fragment"). On top of being maintained and current, reveal offers better navigation (e.g., navigating back between slide fragments is much improved), "vertical slides", etc.

jamezp commented 6 months ago

It's been a while, but I've used reveal.js several times and I quite like it. I likely have some examples somewhere.

emmartins commented 6 months ago

In the quick analysis that I did it seemed dzslides sits between both reveal.js offerings, being better than reveal.js static version due to the onstage controller, but perhaps reveal.js static has other goodies that you can use to convince me to switch? Reveal.js server based I think is overkill and may send some people away, due to the need to learn its setup and usage.

Honestly by now you know that I tend to give priority to something that just works, than trying to make it perfect at once, and IMHO we now have a framework good enough and ready, just needing the content, so I would prefer to fully focus on the content and complete this first iteration, before considering evolving the framework. By the way I will present the full deck in person at a RH company gathering April 5th, so kind of in a hurry :shipit:

jasondlee commented 6 months ago

Definitely do what works first. This was more of a long-term consideration.

FWIW, my slide deck for Devnexus is based on reveal.js using the zip file starter, and I load the presentation, hit 'S' and get a speaker deck window, so I think the static file approach will work just as well. If you're interested. You're always free to close this as "won't do". :)

emmartins commented 6 months ago

Not a won’t do, just leave it for once we have a completed deck that we can tag.

On Mon, 25 Mar 2024 at 21:59, Jason Lee @.***> wrote:

Definitely do what works first. This was more of a long-term consideration.

FWIW, my slide deck for Devnexus is based on reveal.js using the zip file starter, and I load the presentation, hit 'S' and get a speaker deck window, so I think the static file approach will work just as well. If you're interested. You're always free to close this as "won't do". :)

— Reply to this email directly, view it on GitHub https://github.com/wildfly-extras/wildfly-decks/issues/10#issuecomment-2018992705, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEDY6DDHNDOBU4BBMLUZCTY2CM4PAVCNFSM6AAAAABFDTDIE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYHE4TENZQGU . You are receiving this because you commented.Message ID: @.***>