Jump to: navigation, search

I'm curious why you picked Reveal.js for the slide framework.

I've never used Reveal. Does it already have support for an audio track? (And if so, can you advance slides either by clicking the slide or by "scrubbing" the audio position?)

JimTittsler (talk)20:41, 12 March 2014

Reveal.js has a wide range of useful features which include

  • nested slides
  • nice slide tansition customization
  • markdown contents
  • PDF export
  • speaker notes(useful if author is giving a live presentation)
  • a nice API to do things easily

It does have automatic slide transitions at specific interval of time. For linking it with audio position, I'd be using Popcorn.js similar to way its being done in the prototype, but with easy authoring of course.

Aps (talk)20:54, 12 March 2014

Markdown could actually be a disadvantage, since WikiEducator authors are familiar with wikitext.

JimTittsler (talk)21:25, 12 March 2014

Wiki authors don't need to write/read markdown. They would just be using the UI. Reveal.js would be storing the content in markdown format in sub-pages.

Aps (talk)21:29, 12 March 2014

If it is in Markdown format, it won't render correctly on the subpages.

JimTittsler (talk)00:18, 13 March 2014

That's why I said that users won't need to read these subpages. Is there a way we can hide the pages? Or do you know a better way to store this data?

I'm thinking of trying to convert the main page only to a slideshow, but I guess parsing wiki text won't be that easy.

Aps (talk)01:00, 13 March 2014

My first suggestion would be to store it in wikitext format the way the prototype does. That might allow additional reuse beyond just the slideshow.

JimTittsler (talk)01:08, 13 March 2014

As per your suggestion, I have managed to store text in wiki only using div tags so that it can be read directly as well as used for slideshow and other purposes. Here is a demo I created -

Aps (talk)11:54, 17 March 2014