{"_id":"deckem","_rev":"33-6c9a511512c94c2b62dbe0c53f4c4c5d","name":"deckem","description":"Build deck.js presentations using Jade templating","dist-tags":{"latest":"0.0.11"},"versions":{"0.0.11":{"name":"deckem","description":"Build deck.js presentations using Jade templating","tags":["presentations","deck.js","couchdb","steelmesh"],"author":{"name":"Damon Oehlman","email":"damon.oehlman@sidelab.com"},"version":"0.0.11","main":"index","bin":{"deckem":"./bin/deckem"},"engines":{"node":">= 0.4.x < 0.7.0"},"dependencies":{"async":"0.1.x","climate":"0.2.x","debug":"*","jade":"0.20.x","out":"*","underscore":"1.x.x","scaffolder":"0.4.x"},"devDependencies":{"vows":"0.5.x","interleave":"0.1.x"},"repository":{"type":"git","url":"git://github.com/steelmesh/deckem.git"},"bugs":{"url":"http://github.com/steelmesh/deckem/issues"},"contributors":[],"_npmUser":{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"},"_id":"deckem@0.0.11","_engineSupported":true,"_npmVersion":"1.1.0-beta-10","_nodeVersion":"v0.6.7","_defaultsLoaded":true,"dist":{"shasum":"f5571f8f929e4f5ee985c9f93c7a270e46b5a2c7","tarball":"https://registry.npmjs.org/deckem/-/deckem-0.0.11.tgz","integrity":"sha512-PuB7y9bjN6NlT1M2RCKxNy0xYQYalXNJVC54YDepTJ+F2PEqloDzWCwsOLX3n5EbPhbn/ZVew2f2IMW8mR1pQA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEQ1AN4sVdf8gxiDY6SAEEDhawnQXpizyfA6XEJM6jH3AiAo59gKeovnaF1QaWiWLglyB54FH+jTautOrxicms2ZGQ=="}]},"readme":"# Deck'em: Jade + deck.js Awesomeness \n\nFirst, lets establish why this project exists:\n\n1. [deck.js](https://github.com/imakewebthings/deck.js) is a wonderful library for creating web presentations.  Does just enough, and has plugin support.  Brilliant.\n\n2. The [Jade templating engine](https://github.com/visionmedia/jade) is very expressive and is likely to save you from typing html tags again and again and, um, again.\n\n3. The two combined with some tooling would be awesome.\n\n__NOTE:__ Deckem uses a [modified version of deck.js](https://github.com/DamonOehlman/deck.js) which removes a lot of the iframe hacks that have been implemented to improve the behaviour of video embedded in slides.  This has been done as deckem is designed to be a coders presentation tool and iframes are used to embed demos that have been built with [demogen](https://github.com/DamonOehlman/demogen).\n\n## Getting Started\n\n### Installing Deck'em\n\nFirst, I'd recommend installing using npm:\n\n```\nnpm install deckem -g\n```\n\n### Scaffolding a new Deck\n\nThis will install the helpful `deckem` command-line tool.  You should now be able to scaffold a new deck.  Change to the directory you want to create the deck in and run the following command:\n\n```\ndeckem create\n```\n\nAll being well, you'll end up with a new `main.jade` file.  Something similar to the one shown below:\n\n```\n.slide\n    h1 A Test Slide\n    \n.slide\n    h2 Another Slide\n    \n    p This a slide with some sub-slides.\n    \n    ul\n        li.slide Like this one\n        li.slide And this one\n    \n.slide\n    h2 Some Example Code\n    \n    textarea.code(mode='javascript',runnable='true')\n        console.log('hello');\n```\n\n### Building the deck\n\nIn the same directory that you scaffolded your deck, run the following command:\n\n```\ndeckem build\n```\n\nAfter building your deck (note, you can also just run `deckem` as build is the default action), you will have an additional three files in your directory:\n\n- index.html (The compiled deck)\n- deckem.css (A collection of [CSS files](/DamonOehlman/deckem/blob/master/src/deckem.css) required to make the deck look pretty)\n- deckem.js (A collection of [JavaScript files](https://github.com/DamonOehlman/deckem/blob/master/src/deckem.js) require to make the deck work)\n\n## Advanced Usage\n\n### Configuration Files\n\nIn addition to the main `deck.jade` file, you might have also noticed that a scaffolded presentation also contains a `deck.json` file.  This file allows you to configure aspects of the deck.\n\n```js\n{\n\t\"title\": \"Your Deck Title\",\n\t\"theme\": \"neon\"\n}\n```\n\n### Building a Suite of Decks\n\nIn short, run the `deckem` from a directory in which you have subfolders with decks in them.  It will build them all for you and put the client assets in the root folder only.  \n\nDeck configurations are inherited from parent folders down into subfolders, so you can specify a theme in a top level folder and have all child decks use that them while using the configuration file to set the presentation title.\n\n## License\n\nMIT\n\n## Roadmap\n\n- Include options in the build process to change deck.js themes, etc\n- Read configuration information from a local config file and include deck.js extensions appropriately.","maintainers":[{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"}],"directories":{}}},"maintainers":[{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"}],"time":{"modified":"2022-06-14T22:27:40.004Z","created":"2011-09-14T02:07:38.300Z","0.0.3":"2011-09-14T02:07:41.103Z","0.0.4":"2011-09-16T03:04:07.506Z","0.0.5":"2011-10-01T10:51:22.397Z","0.0.6":"2011-10-01T14:41:05.503Z","0.0.7":"2011-10-04T02:56:02.991Z","0.0.9":"2011-12-21T10:23:28.897Z","0.0.11":"2012-02-09T22:34:50.677Z"},"author":{"name":"Damon Oehlman","email":"damon.oehlman@sidelab.com"},"repository":{"type":"git","url":"git://github.com/steelmesh/deckem.git"}}