Coder Social home page Coder Social logo

generator-reveal's Introduction

Reveal.js generator Build Status Coverage Status NPM version

Dependency Status devDependency Status

A Yeoman generator for the awesome Reveal.js presentation framework.

Usage

Creating a new presentation

Install: npm install -g generator-reveal

Make a new directory, and cd into it:

mkdir my-new-project && cd $_

Run yo reveal and start building your presentation.

After all files are created you can view your slides with grunt:

grunt serve

Then, create further slides with yo reveal:slide more-content. See below for available options. When you want to export your presentation to some static HTML server, you can type grunt dist to have all your relevant files saved to the dist directory.

Working on an existing presentation

If you are checking out an existing presentation to do some work on it, make sure to install the required dependencies:

cd my-existing-project
npm install && bower install

Now you should be able to view the slides again with grunt:

grunt serve

Generators

Available generators:

Slide

Generates a Slide file.

Example:

yo reveal:slide "Slide Title"

Produces slides/slide-title.html:

<h2>Slide Title</h2>

<p>This is a new slide</p>

And the slide filename will be added to your slides/list.json file.

[
    "index.md",
    "slide-title.html"
]

Vertical Slides

In order to add vertical slides, you can nest an array inside slides/list.json

[
    "index.md",
    [
        "vertical-html.html",
        "vertical-markdown.md"
    ],
    [
        "vertical-html-2.html",
        "vertical-markdown-2.md"
    ],
    "the-end.md"
]

Simple (Image) Slides

Sometimes you just want a slide with a background image. That's okay, a slide object does not need a filename.

[
    "index.md",
    {
        "attr": {
            "data-background": "http://example.com/image.png"
        }
    }
]

Options

Markdown

Invoked with --markdown

yo reveal:slide "Slide Title" --markdown

Produces slides/slide-title.md

## Slide Title

This is a new slide
Attributes

Invoked with --attributes

yo reveal:slide "Slide Title" --attributes

adds a slide Object with an attr key to your slides/list.json file. Attributes will be passed to section element containing the slide.

[
    "index.md",
    {
        "filename": "slide-title.md",
        "attr": {
            "data-background": "#ff0000"
        }
    }
]
<section data-markdown="slides/slide-title.md" data-background="#ff0000"></section>
Speaker Notes

Invoked with --notes

yo reveal:slide "Slide Title" --notes

Produces slides/slide-title.html:

<h2>Slide Title</h2>

<p>This is a new slide</p>

<aside class="notes">
    Put your speaker notes here.
    You can see them pressing 's'.
</aside>

All three options maybe combined, e.g.

yo reveal:slide "Markdown Slide With Notes And Section-Attributes" --notes --attributes --markdown

Resources

If your presentation requires specific resources that you would like included with your project, place them in the resources directory. These assets will be included in the distribution and available for access at the path resources/asset_name.ext.

Github Pages Deployment

With the help of Grunt Build Control, generator-reveal can deploy your presentation to Github Pages easily. All you have to do is

  • Set your username and repository name when you call yo reveal
  • Create and configure your remote Github repository for the presentation
  • Push your first commit
  • Deploy with grunt deploy

If everything goes right, grunt deploy will build and push your presentation to a gh-pages git branch. Just give it a couple of minutes, fire up a browser and go to http://username.github.io/repositoryname to see your brand new presentation.

Customisation

To change the options of the whole presentation, such as the theme used, transition effect etc. consult the Reveal.js documentation. An important difference, though, is that you should not edit the index.html file directly as it gets overwritten as you add presentation content whenever a new grunt build is triggered. You should instead edit the templates/_index.html file, which is used as a template for the automatically generated index.html.

Highlight.js Syntax Themes

The generated presentation app includes the Highlight.js Syntax Themes as a dependency, allowing you to change the syntax theme.

The available syntax themes can be found in the bower_components/highlightjs/styles folder. Selecting a new syntax theme can be done by changing the stylesheet reference in the templates/_index.html file:

<!-- For syntax highlighting -->
<link rel="stylesheet" href="bower_components/highlightjs/styles/monokai_sublime.css">

License

MIT License

generator-reveal's People

Contributors

atomaka avatar boo1ean avatar daformat avatar danielwegener avatar diagramatics avatar dvberkel avatar iamcarrico avatar janraasch avatar jonanh avatar kahlil avatar metakermit avatar mischah avatar nwinkler avatar pfrenssen avatar riezebosch avatar slara avatar tristola avatar yfr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

generator-reveal's Issues

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.

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?

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

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.

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?

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)

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.

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.

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. :)

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 ?

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.

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 ?

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

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.

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)`

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,

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

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?

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.

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 !

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.

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 :)

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

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)

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

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?

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.

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"

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?

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.