You can also you Slide Show (S9) to generate Reveal.js slides from your markdown source. See https://github.com/slideshow-templates/slideshow-reveal.js as an example. The templates are Jekyll-compatible (and, thus, work "out-of-the-box" on GitHub Pages (no plugin required). See http://slideshow-templates.github.io/slideshow-reveal.js/sli... as a live demo. Cheers.

Thanks for that hint! p_slides is explicitly dumb, though. It has no requirements to install additional software, pre-compile anything or run a server. This way it just works for many lecturers on different Operating Systems with very different areas of expertise and continues to do so without any changes after 5 years. Hosting on GH Pages is totally awesome for us developers, however my primary use case is to have the slides self-contained (no dependencies) in a private repository with other lecturers for using them in the university.

Hello, FYI: The output of Slide Show (S9) is a self-contained static site (works anywhere incl. of course private repos etc.) - you can also create a single-file PDF as an option. Only the templates "require" GitHub Pages or Jekyll if you want a "live" preview for demos. Cheers. PS: More info @ http://slideshow-s9.github.io

Hi Gerald

S9 really looks nice - however, it is not self contained in the sense that I was referring to. p_slides is essentially a single HTML file (with the other assets hosted somewhere).

For S9, Ruby and usage of the command line is required. For a developer, that's not a big issue, of course. Myself, I'm a Ruby/JS/Clojure dev, so I do not mind installing one more gem(; However, my goal was to _really_ make p_slides self-contained. There is no need to install anything, run any pre-compiler or run the slide within a web-server. It doesn't even use npm or bower to install the assets. With this methodology, p_slides certainly is technologically less complex (or interesting^^), but it continues to work after years without any change on any computer that has a browser. That's just not happening with Ruby or Node or any other dependency. I'm not saying the latter is bad (it is not at all!), I'm saying this simplicity ability to be completely self-contained with no tooling required was the specific design decision for p_slides and it served me and a couple lecturers well. I basically made no advertisement for it, I just wrote it, because I wanted something that just works and I can distribute to students, too.

For that gap I wrote a GitHub pages compatible Jekyll wrapper: https://github.com/tasmo/reveal-jekyll