slara/generator-reveal

Yeoman generator for Reveal.js

generator-reveal's Issues

yo reveal:slide breaks under [email protected]

Although I am not sure what the problem is, the full extent of the problem or if it is even a problem with generator-reveal, I would like to report the following issue. I am also reporting this as a yo issue.

When running a yo command it told me that a new version was available. The version I was using was 1.3.3 and the latest version was 1.4.5. I upgraded with the command npm install --global yo. When I did the yo reveal:slide command stop working.

In particular the following command

yo reveal:slide --markdown "broken"

produces the following error

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Did not provide required argument name!
    at SlideGenerator.<anonymous> (/usr/local/lib/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:351:33)
    at Array.forEach (native)
    at SlideGenerator.Base.checkRequiredArgs (/usr/local/lib/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:347:19)
    at SlideGenerator.argument (/usr/local/lib/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:317:8)
    at SlideGenerator.module.exports.Base.extend.constructor (/usr/local/lib/node_modules/generator-reveal/node_modules/yeoman-generator/lib/named-base.js:20:10)
    at new SlideGenerator (/usr/local/lib/node_modules/generator-reveal/slide/index.js:17:51)
    at Environment.instantiate (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:281:10)
    at Environment.create (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:258:15)
    at Environment.run (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:317:24)
    at /usr/local/lib/node_modules/yo/lib/cli.js:91:9

only when I downgraded yo to version 1.3.3 did the command produce the expected result.

data-background

Unless I am doing something wrong the data-background does not seem to be working. I should just be able to add the following attribute to the section element in the [slide-name].html, right?

data-background="#ff0000"

Use high-res svg badges on `readme`.

Feature: git add + git commit new slide as it is created

I think it would be very useful/handy to add an option to have the generator run git-add and or git-commit when creating new slides.

Pros

I find I forget quite often to add a new slide to the index, and forget to commit changes in slides/list.json (since I hardly every edit it by hand).

Cons

Have a generic "added slide .." commit message scattered throughout the history would not be pretty, but in my opinion is very useful for searching the history. I really like having them in there for each slide, others may disagree.

Thoughts on implementation

Could be decided at setup when you pick the theme in that case being an always or never event. Or just a per invocation flag, eg yo reveal:slide mynewslide --git would:

1. create slides/mynewslide.html
2. modify slides/list.json
3. git add slides/list.json slides/mynewslide.html
4. ? git commit -m " created mynewslide"

The 4th point should probably optional. It is possible you don't want commits to be made automatically for you.

Markdown slides separation

Hi, first of all thanks for the contribution, it works great! Just one question, how do I do for separate slides horizontal and vertically under the same Markdown file?

Regards,

Font issue

When generating after a reveal, fonts are not loaded with defaults.

In my Chrome logs:

Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/lib/font/league_gothic-webfont.woff
Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/lib/font/league_gothic-webfont.ttf
Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:9000/lib/font/league_gothic-webfont.svg#LeagueGothicRegular

Update to support reveal.js 3.x

Hello

A new skin (black) has been introduced in this new version of reveal. Are there any other improvements or breaking changes that need to be supported?

Any interest in moving to gulp instead of grunt?

Opinions please :)

Providing both seems like a lot of effort. Maybe grunt is more approachable for the use-case.

• http://gulpjs.com/
• http://gruntjs.com/

Code Highlighting does not work

I have seen that code highlighting does not work. If you create a new slide:

yo reveal:slide "Example Slide"

and then you put this in the slide as a test:

<pre><code class="javascript">
var a = 34
var b = function(){
return "great"
}
</code></pre>

<pre><code>
System.out.println("What is this?");
String p = "this is p";
</code></pre>

You' ll see the code won't be highlighted.

I believe the reason for this is that the code will be highlighted only if already present from the start in the DOM of index.htm. However, as the html slides are loaded one by one and not present in the DOM, the code won't be highlighted.

Using `grunt serve` instead of `grunt server`

It is currently the default command in Yeoman's official generators. Might as well follow suit.

npm not registered (yet) ?

Hey... I wanted to check out this project, but my npm says it cannot find anything for:

npm install generator-reveal

Error:
npm ERR! 404 'generator-reveal' is not in the npm registry.

Or is it just me?

Keep up the good work,

Regards,

Mathias

No support handling a CJK title with reveal:slide

Already issued into underscore.string: esamattis/underscore.string#349
It's a kind of lack of feature by slugify, however, there are room for fixing this as an application level though.

Could you consider this?

Demo: https://asciinema.org/a/14581

Can't npm install with the package.json created by generator-reveal

I don't know what's the process of fetching the reveal.js source, but the version that comes with yo reveal doesn't seem to work - I can't install the dependencies via npm install. I described this in more details in isaacs/npm#3885.

Add a generator for HTML slides

npm install fail

Hi

First, some useful context :

$ node -v
v0.10.19

$ npm -v
1.3.11

Now, my problem :
When I run sudo npm install -g generator-reveal i get

npm http GET https://registry.npmjs.org/generator-reveal
npm http 304 https://registry.npmjs.org/generator-reveal
npm http GET https://registry.npmjs.org/yeoman-generator
npm http 304 https://registry.npmjs.org/yeoman-generator
npm http GET https://registry.npmjs.org/cheerio
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/tar
npm http GET https://registry.npmjs.org/diff
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/underscore.string
npm http GET https://registry.npmjs.org/lodash
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/isbinaryfile
npm http GET https://registry.npmjs.org/dargs
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/inquirer
npm http GET https://registry.npmjs.org/iconv-lite
npm http GET https://registry.npmjs.org/shelljs
npm http GET https://registry.npmjs.org/findup-sync
npm http GET https://registry.npmjs.org/chalk
npm http GET https://registry.npmjs.org/text-table
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/cheerio
npm http 304 https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/tar
npm http 304 https://registry.npmjs.org/diff
npm http 304 https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/underscore.string
npm http 304 https://registry.npmjs.org/lodash
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/isbinaryfile
npm http 304 https://registry.npmjs.org/dargs
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/inquirer
npm http 304 https://registry.npmjs.org/iconv-lite
npm http 304 https://registry.npmjs.org/shelljs
npm http 304 https://registry.npmjs.org/findup-sync
npm http 304 https://registry.npmjs.org/chalk
npm http 304 https://registry.npmjs.org/text-table
npm http GET https://registry.npmjs.org/has-color
npm http GET https://registry.npmjs.org/ansi-styles
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/cheerio-select
npm http GET https://registry.npmjs.org/htmlparser2/3.1.4
npm http GET https://registry.npmjs.org/underscore
npm http GET https://registry.npmjs.org/entities
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/block-stream
npm http GET https://registry.npmjs.org/fstream
npm http GET https://registry.npmjs.org/cli-color
npm http GET https://registry.npmjs.org/mute-stream/0.0.3
npm http GET https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/json-stringify-safe
npm http GET https://registry.npmjs.org/forever-agent
npm http GET https://registry.npmjs.org/tunnel-agent
npm http GET https://registry.npmjs.org/http-signature
npm http GET https://registry.npmjs.org/aws-sign
npm http GET https://registry.npmjs.org/oauth-sign
npm http GET https://registry.npmjs.org/cookie-jar
npm http GET https://registry.npmjs.org/node-uuid
npm http GET https://registry.npmjs.org/form-data
npm http 304 https://registry.npmjs.org/has-color
npm http 304 https://registry.npmjs.org/ansi-styles
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/cheerio-select
npm http 304 https://registry.npmjs.org/htmlparser2/3.1.4
npm http 304 https://registry.npmjs.org/underscore
npm http 304 https://registry.npmjs.org/entities
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/CSSselect
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/block-stream
npm http 304 https://registry.npmjs.org/fstream
npm http 304 https://registry.npmjs.org/cli-color
npm http 304 https://registry.npmjs.org/mute-stream/0.0.3
npm http 304 https://registry.npmjs.org/qs
npm http 304 https://registry.npmjs.org/json-stringify-safe
npm http 304 https://registry.npmjs.org/forever-agent
npm http 304 https://registry.npmjs.org/tunnel-agent
npm http 304 https://registry.npmjs.org/http-signature
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/aws-sign
npm http 304 https://registry.npmjs.org/oauth-sign
npm http 304 https://registry.npmjs.org/cookie-jar
npm http 304 https://registry.npmjs.org/node-uuid
npm http 304 https://registry.npmjs.org/form-data
npm http GET https://registry.npmjs.org/es5-ext
npm http GET https://registry.npmjs.org/memoizee
npm http 304 https://registry.npmjs.org/CSSselect
npm http 304 https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/domelementtype
npm http GET https://registry.npmjs.org/domhandler
npm http GET https://registry.npmjs.org/domutils
npm http GET https://registry.npmjs.org/readable-stream
npm http 304 https://registry.npmjs.org/sigmund
npm http GET https://registry.npmjs.org/CSSwhat
npm http GET https://registry.npmjs.org/domutils
npm http 304 https://registry.npmjs.org/domutils
npm http 304 https://registry.npmjs.org/readable-stream
npm http 304 https://registry.npmjs.org/CSSwhat
npm http 304 https://registry.npmjs.org/domutils
npm http 304 https://registry.npmjs.org/es5-ext
npm http 304 https://registry.npmjs.org/memoizee
npm http 304 https://registry.npmjs.org/domhandler
npm http 304 https://registry.npmjs.org/domelementtype
npm http GET https://registry.npmjs.org/event-emitter
npm http GET https://registry.npmjs.org/next-tick
npm http 304 https://registry.npmjs.org/event-emitter
npm http 304 https://registry.npmjs.org/next-tick
npm http GET https://registry.npmjs.org/hawk
npm ERR! cb() never called!
npm ERR! not ok code 0

Any idea what's wrong ?

Slides structure

When using reveal with larger presentations you need to have some more structure in your slides folder. Would it be a good feature for the generator if 'children slides' would sit inside a folder with the same name of the parent slide?

If that would be the case a grunt command to build the slide index could be added as well to reduce even more complexity :)

Reveal Slide Option

First, thank you so much for this fabulous work...love reveal but was a pain with markdown (the only way I write content). This makes it a snap!

Taking lazy to the extreme, it would be great to implement a paramenter to the reveal:slide method where a user can state they want speaker notes. All this would do is add the aside class notes html in the markdown file (or html).

I know, lazy. :)

Setting the options without rewriting with yo reveal:slide

Hi,

I don't quite understand the workflow with the yo reveal:slide command - it completely rewrites my index.html file. Where is it intended to set all the presentation-wide options then - theme, transition etc.?

Or is this command intended to be used only at the beginning and then manually add new slides files later on?

Check generated files with jshint and coffeelint in Grunt test task.

This would prevent bugs like #44 and #45. Default generated files should be checked at least.

Feature Request: Build

I'd still like to host my presentation on a remote server. Unless I'm missing something that is not currently possible. I'd love to type grunt build and my presentation gets statically built int a build directory that I can than host on a server.

Typo in .md with notes template.

There's a typo in slide/templates/slide-withnotes.md. It should be note: instead of notes: (See reveal.js/plugin/markdown). I'll fix this right away. Also, I think we should lock down the version of reveal.js in app/templates/_bower.json to a specific commit to be able to guarantee compatablity to the API.

execvp(): No such file or directory

I get this error when running yo reveal, right after answering the question, while the progress spinner is active:

I'm all done. Running bower install & npm install for you to install the required dependencies. If this fails, try running the command yourself.

execvp(): No such file or directory

Automatically add the slide reference to index.html with reveal:slide subgenerator

coffelint task fails when generated lines are too long.

For example, when the user selects the default github user and repo name, the test fail with:

Running "coffeelint:all" (coffeelint) task

Gruntfile.coffee
✖ line 101 Line exceeds maximum allowed length Length is 84, max is 80
✖ 1 error

generated package.json is missing a 'version' attribute

because of this npm install fails with the following error message.

npm ERR! install Couldn't read dependencies
npm ERR! Error: no version
npm ERR!     at validVersion (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:527:32)
npm ERR!     at final (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:289:23)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:119:33
npm ERR!     at cb (/usr/local/lib/node_modules/npm/node_modules/slide/lib/async-map.js:48:11)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:233:59
npm ERR!     at Glob.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/glob/glob.js:91:7)
npm ERR!     at Glob.EventEmitter.emit (events.js:88:17)
npm ERR!     at Glob._processEmitQueue (/usr/local/lib/node_modules/npm/node_modules/glob/glob.js:270:10)
npm ERR!     at Glob.emitMatch (/usr/local/lib/node_modules/npm/node_modules/glob/glob.js:255:8)
npm ERR!     at Glob._finish (/usr/local/lib/node_modules/npm/node_modules/glob/glob.js:217:8)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Darwin 11.4.2
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /private/tmp/test
npm ERR! node -v v0.9.2
npm ERR! npm -v 1.1.61
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /private/tmp/test/npm-debug.log
npm ERR! not ok code 0

When I add a version attribute npm install runs without problems.

Index.html hangs

yo reveal
grunt build

http://localhost:9000 hangs.

All assets return normally (eg: http://localhost:9000/bower_components/reveal.js/css/theme/default.css) but no .html pages respond.

We need a way to add some attrs to vertical slides too

Usage example: I need to place a mapbox map on one of my slides. In order to do so, I set CSS height to 100%, like so:

{
    "filename": "geo/map.html",
    "attr": {
        "style": "height: 100%;"
    }
}

But if I place this slide in one of vertical slide sequences, the above approach fails.

reveal:slide subgenerator should ask for a slide index

After #1 is solved, the subgenerator should be able to add the slide in a custom order.

numeric slide names lead to exception

If I want to create a slide with a numeric name I get an exception,

e.g.
yo reveal:slide "2"

C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\node_modules\nopt\lib\nopt.js:239
    if (arg.match(/^-{2,}$/)) {
            ^
TypeError: Object 2 has no method 'match'
    at parse (C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\node_modules\nopt\lib\nopt.js:239:13)
    at nopt (C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\node_modules\nopt\lib\nopt.js:40:3)
    at SlideGenerator.Base.parseOptions (C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\lib\base.js:331:10)
    at SlideGenerator.option (C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\lib\base.js:262:8)
    at SlideGenerator.Base (C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\lib\base.js:85:8)
    at SlideGenerator.module.exports.Base.extend.constructor (C:\Program Files\nodejs\node_modules\generator-reveal\node_modules\yeoman-generator\lib\named-base.js:19:10)
    at new SlideGenerator (C:\Program Files\nodejs\node_modules\generator-reveal\slide\index.js:17:51)
    at Environment.instantiate (C:\Program Files\nodejs\node_modules\yo\node_modules\yeoman-environment\lib\environment.js:281:10)
    at Environment.create (C:\Program Files\nodejs\node_modules\yo\node_modules\yeoman-environment\lib\environment.js:258:15)
    at Environment.run (C:\Program Files\nodejs\node_modules\yo\node_modules\yeoman-environment\lib\environment.js:317:24)

data-background has no effect

Are we missing some background initializer?

reduce upload size

Copying everything inside bower_componentes result in copying 160mb 3mb from reveal.js directory. (160 if your reveal.js is customised and linked locally with bower)

Maybe bower-wiredep and grunt-bower can save the day.

Update yeoman-generator to 0.18

see http://yeoman.io/blog/release-0.18.html

Add folder-based approach

I would like to add the possibility to get rit of the metadata keeping in the list.json. I would like to suggest to just order the slides by alphabet.

I usually order my slides like this:

/1-chapter1/0-chapter1-introduction.md
/1-chapter1/1-slide1.md
/1-chapter1/2-slide2.html
/2-chapter2/0-chapter2-introduction.md
/2-chapter2/1-chapter2-slide1.md
/3-chapter3-one-slide-only.md

Maintaining my list.json file becomes tedious to say the least.

I'm a big fan of the generator-reveal, just this one thing is bothering me. If you agree, i can do a PR. How would you suggest it would work? Just use the list.json if its there, otherwise do the folder ordering mechanism?

Package doesn't work

Unable to register generator-reveal/app/index.js (Error: Arguments to path.join must be strings)
Unable to register generator-reveal/slide/index.js (Error: Arguments to path.join must be strings)
Error reveal

generator-reveal 0.0.5
node v0.10.11

How to add subpages?

Normally, with Reveal, you can add subpages (so you browse full pages left to right and subpages up-down). Is this possible with this generator?

slide generation with --markdown --attributes seems broken

Using the new options, I end up with a slide list as below.
Within the presentation, the slide with atrributes doesn't get rendered.

[
    "index.md",
    "various.md",
    {
        "filename": "references.md",
        "attr": {
            "data-background": "#ff0000"
        }
    }
]

PS: thanks a lot for this nice tool !

possibility to add slide as text

It's a request to add a slide from a raw text in list.json Ex:

[
    "start.html",
    "Some Text",
    "end.html",
]

deploy to gh-pages

Include a grunt task for deployment of the dist folder to gh-pages.

yo reveal

Hello,

I have just tried to run yo reveal (after upgrading Yeoman to 1.0.4 and installing the reveal generator) and I get the following error:

/Users/paulbacchus/node_modules/generator-reveal/app/index.js:26
  '\n   `---------´  |    ' + 'Welcome to Yeoman,'.yellow.bold + '    |' +
                                                         ^
TypeError: Cannot read property 'bold' of undefined
    at RevealGenerator.askFor (/Users/paulbacchus/node_modules/generator-reveal/app/index.js:26:58)
    at /Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:290:20
    at /Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:548:21
    at /Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:224:13
    at iterate (/Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:131:13)
    at async.eachSeries (/Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:147:9)
    at _asyncMap (/Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:223:9)
    at Object.mapSeries (/Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:213:23)
    at Object.async.series (/Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/node_modules/async/lib/async.js:546:19)
    at RevealGenerator.run (/Users/paulbacchus/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:298:9)

Defaulting .editorconfig to 2 spaces

It is 4 at the moment. Some files are generated with 2 spaces already, and some need adapting.

Generate missing slide files using list.json

I'm using reveal (and your generator, thanks!) to build a rather large presentation. Because I'm using subsections, I find it easier to start by editing list.json itself with filenames and to give it structure. I'd like to use the info in the list.json file to generating missing slides.

I will probably tackle this for my own use, but also wanted to know if there was a more general interest in this feature.

When reloaded, code style is not applied (on Firefox)

When the page is reloaded, the code style is not always applied on Firefox.

It looks like the browser is still loading something (but I can't figure what).

No problem with Chrome.

Update engine: node

Let's go with

"engines": {
    "node": ">=0.10.0"
  }

in package.json to comply with yeoman-generator >=v0.17.0.

How to deploy to Github pages?

I'm trying to push to github pages, but it is giving this error:

Running "buildcontrol:pages" (buildcontrol) task

Creating branch "gh-pages".
Warning: fatal: Failed to resolve 'HEAD' as a valid ref.
 Used --force, continuing.
Warning: Task "buildcontrol:pages" failed. Used --force, continuing.

Done, but with warnings.

I've tried creating a HEAD as suggested in http://stackoverflow.com/questions/4848607/git-fatal-no-such-ref-head - but it doesn't seem to solve it.

PDF Export Busted

Reveal.JS recently had to make a fix to PDF exporting, an important and expected feature for conference presenters.

This generator, having a c+p index.html file, also needs that fix, but with a slight tweak since it's referencing the pdf.css file from the bower components.

I've found a fix courtesy of @kbremner here

Will submit a PR shortly

Allow reveal:slide to create slide in a subdirectory

I would like to structure my presentations in such a way that slides that form a short narrative go in a different directory. E.g. the introduction slides go into a directory slides/introduction while the conclusions go into a directory slides/conclusion.

At the moment the reveal:slide command does not allow this option.

I propose to enhance the command with a new option --directory that would indicate in which sub-directory the generated slide should go. It should make the directory if it does not exist yet, but only if it is a directory below slides.

If this is a desirable feature, then I will provide a pull-request.

index.html isn't what is expected

While I was trying to export my prez to pdf (without success), I opened the root index.html, which should contains something like this:

<!-- If the query includes 'print-pdf', use the PDF print sheet -->
        <script>
            document.write( '<link rel="stylesheet" href="css/print/' + ( window.location.search.match( /print-pdf/gi ) ? 'pdf' : 'paper' ) + '.css" type="text/css" media="print">' );
        </script>

But it was not here...
This made me realize that the root index.html is not the same than the /bower_components/reveal.js/index.html...
It's ok since the slides are not included in index.html like in the original, but other parts of this page should stay in sync with the main version, isn't it ?

Generation fails

/w/cli-intro ❯❯❯ yo reveal
/usr/local/lib/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:445
this.env.sharedFs.on('change', writeFiles);
^
TypeError: undefined is not a function
at RevealGenerator.run (/usr/local/lib/node_modules/generator-reveal/node_modules/yeoman-generator/lib/base.js:445:21)
at Environment.run (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/environment.js:319:20)
at /usr/local/lib/node_modules/yo/lib/cli.js:87:9
at Environment.resolver.lookup (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/lib/resolver.js:49:32)
at init (/usr/local/lib/node_modules/yo/lib/cli.js:66:7)
at pre (/usr/local/lib/node_modules/yo/lib/cli.js:53:3)
at Object. (/usr/local/lib/node_modules/yo/lib/cli.js:156:1)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)`

Create example presentation on gh-pages branch

This could even be used as a cool readme type thing, but for now it would simply be cool to show off what you can do with this generator.

bower_components dir gone

Am I being dense again or after executing yo reveal the bower_components dir no longer being created, thus reveal and the other dependencies are not being installed?