generator-bespoke / 1.3.0 last updated 3 months ago created on Aug 13th 2013

Install

npm install --save generator-bespoke

Clone

git clone git@github.com:markdalgleish/generator-bespoke.git

maintainers

markdalgleish

versions 26 total

1.3.0 3 months ago markdalgleish
1.2.0 4 months ago markdalgleish
1.1.1 4 months ago markdalgleish
1.1.0 4 months ago markdalgleish
1.0.0 5 months ago markdalgleish
1.0.0-beta.2 6 months ago markdalgleish
1.0.0-beta 6 months ago markdalgleish
0.9.0 6 months ago markdalgleish
0.8.1 6 months ago markdalgleish
0.8.0 a year ago markdalgleish
0.7.0 a year ago markdalgleish
0.6.0 a year ago markdalgleish
0.5.0 a year ago markdalgleish
0.4.2 a year ago markdalgleish
0.4.1 a year ago markdalgleish
0.4.0 a year ago markdalgleish
0.3.1 a year ago markdalgleish
0.3.0 a year ago markdalgleish
0.2.2 a year ago markdalgleish
0.2.1 a year ago markdalgleish
0.2.0 a year ago markdalgleish
0.1.4 a year ago markdalgleish
0.1.3 a year ago markdalgleish
0.1.2 a year ago markdalgleish
0.1.1 a year ago markdalgleish
0.1.0 a year ago markdalgleish
5 Downloads yesterday.

readme

Bespoke.js Generator

A generator for Yeoman that scaffolds a Bespoke.js presentation.

The boilerplate project includes a Gulp build system, a preview server with LiveReload, Jade and Stylus compilation, and a GitHub Pages deployment task.

Your generated presentation optionally includes the following Bespoke.js plugins:

Usage

Assuming you have Node.js, install generator-bespoke:

$ npm install -g generator-bespoke

Make a new directory and cd into it:

$ mkdir presentation-hello-world
$ cd presentation-hello-world

Scaffold a new presentation:

$ yo bespoke

Presentation workflow

All source files for the presentation reside in the src directory.

Start a local preview server:

$ gulp serve

Compile and deploy to GitHub Pages, assuming a git repo with origin pointing to GitHub:

$ gulp deploy

To manually deploy elsewhere, compile all assets into the dist directory:

$ gulp

License

MIT License

Resolving all dependencies.. This could take a while as our cache is not yet fully warmed up.