Looked at the demo: it makes a total mess all over my history stack.
If you're trying to be "trend and geek," build a system that doesn't break the back button. Unless you're building a CSS3-only engine, you don't have to store the state in the URL. You can still parse the URL fragment to allow people to deep link the slides, having a small "link to this slide" button is worth it not to have to force the user to click back 20 times to leave the presentation.
Although I guess if you're using the TOC to navigate the slides non-linearly it could be considered a feature.
Hmm...I guess this is more a preference on how to use the back button on a browser. If you have open up any GitHub's repository on a HTML 5 compatible browser, you can find that it has similar design.
jekyll_and_hyde is just a simple hook over jekyll and slippy(the jQuery plugin that make your HTML file a presentation). It doesn't force you to use slippy as the presentation library. To use other library/template for your presentation, you may type in "jh new new_presentation --template=your_template_git_repo" during its creation.
This is quite impressive, I have to admit. Though being that there is a Jekyll python-clone called Hyde, I thought they were finally being brought togetherf...
Showoff is pretty cool too! But the shiniest point of jekyll_and_hyde that I would like to mention is its tight integration with jekyll, which is the GitHub Pages rendering engine. That means you can publish your slides just by simply pushing it up to GitHub :).
Beamer is pretty cool too. I myself like ti a lot. One shiniest point of jekyll_and_hyde is its tied integration with GitHub, which runs a jekyll rendering engine for its GitHub Pages. You can just simply push your presentation markup to GitHub and it works.
The things is you wanna minimize your toolset of making your presentation, such as just using Git and Textile. Of course other sort of presentation has their places
http://johnmacfarlane.net/pandoc/README.html#producing-html-...