Serving multiple #CALIcon15 presentations with reveal.js

I have 4 sessions to present at CALICon15 this year and that means a lot of slides. Over the past few years I’ve tried a number of different approaches to putting together presentations including using outlines, wikis, AsciiDoc with deck.js, even plain old web pages. This year I’m giving reveal.js a try.

Reveal.js is a framework for easily creating beautiful presentations using HTML. It includes a lot of really handy features including speaker notes and a multiplexing plugin that allows viewers to follow a guided version of the presentation. The full installation gives me a nice node.js infrastructure that serves the slides and all I need to do is write an HTML file for each presentation.

Of course the basic installation instruction show you how to grab the code, then create and serve a single presentation. Even though I’m using git for versioning, I didn’t want to keep up 4 separate repos or even branches of code. I want to have all the HTML for the presentations in a single directory, in a single repo. I needed to figure out how to serve up multiple presentations from a single reveal.js installation.

It turns out there is a quick way to do this. I copied the included index.html to sample.html, for future reference and edited index.html into a single slide that links to 4 other html files. Each of the other files contains one presentation. This gives me a single code base for all the presentations and easy access to all of the features of reveal.js.

My presentations for CALIcon15
My presentations for CALIcon15

For my next step I’m going to give the multiplexing feature a try so folks can follow along. I think that there a lot of potential here for law schools to make use of this sort of tech in the classroom. Fast presentations that are shared directly with students would be something worth looking into.

The Conference Manifesto: 10 Steps to a Better Conference

Acceptance to the conference could be contingent upon the speaker reading and signing an agreement to meet the following criteria in their talks:

1) I understand that the conference paper should do something that an article cannot. Since it involves direct, real-time contact with other humans, the speaker should make use of this relatively rare and thus precious opportunity to interact meaningfully with other scholars.

2) I will not read my paper line by line in a monotone without looking at the audience. I needn’t necessarily abide by some entertainment imperative, with jokes, anecdotes or flashy slides, but I will strive to maintain a certain compassion toward my captive audience.

3) I understand that a list is not a talk. I will not simply list appearances of a theme in a given corpus.

4) I will have a thesis, and if I don’t, I will at least have a reason that my talk should exist.

5) I will keep direct citations to a minimum, not relying on them to fill up time. I understand that audience members shudder at lengthy blocks of text in the PowerPoint or on the handout.

6) In the Q. and A., I will not ask an irrelevant question for the sake of being seen asking a question. If my question is hyperspecific and meaningless to anyone but myself, I will approach the speaker after the talk with my query.

7) I will not make a statement and then put a question mark at the end to make it sound like a question.

8) If I ask an actual question, I will a) not take more than a minute or so to ask it, and b) ask it politely even if I disagree with the speaker.

9) I respect the time of my colleagues who’ve come to hear me speak. I will do my best to be as clear and succinct as possible, and make their attendance worthwhile.

10) I understand that if I disregard these recommendations, I might be complicit in the death of the humanities.

Source: The Conference Manifesto

This is aimed at academic conferences in the humanities, but it applies equally to academic conferences in law and to many tech conferences. CALIcon would be an even better conference if presenters and attendees kept these things in mind.