Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/damonoehlman/demogen

DEPRECATED: Client-side Demo Generator
https://github.com/damonoehlman/demogen

Last synced: 7 days ago
JSON representation

DEPRECATED: Client-side Demo Generator

Awesome Lists containing this project

README

        

# demogen

Demogen is the ___write your JS library demo code once___ solution.

## Why use demogen?

It's annoying to wrap demos for your library in the same boilerplate HTML everytime, but that is the way that most of us like to consume demos. I've made various attempts to make my demo writing process simple (for me) in the past but it generally results in demos that are confusing to work with.

## Getting Started

First, install using npm:

```
npm install demogen -g
```

If all has gone well, then you will have a `demogen` executable available to you in your path.

### Scaffolding a Project

You can scaffold a new project by changing to the directory you want to create the project in and running:

```
demogen create
```

### Building the Demos

Demogen generates a number of static HTML files from the assets in the `_sources` directory. To generate those files, simply run either `demogen` with no additional parameters or:

```
demogen build
```

Once this is done you will have a number of .html files in the current folder for demos that have been defined in the `_sources` directory. Feel free to give it a go with a newly scaffolded project. The demos are currently pretty lame, but that will be fixed in time.

## Structuring your Demo Files

Get this right, and everything will just sing. So here's what you need to know.

### The Layout File

In the root of the `_sources` tree you should have a `_layout.html` file. The one that is created when scaffolding a project is essentially a version of the [HTML5 Boilerplate](http://html5boilerplate.com/) with [Handlebars](http://handlebars.strobeapp.com/) templating in relevant places:

```html





{{#css}}
{{this}}
{{/css}}
{{{ body }}}

{{{ code }}}







{{{ code }}}

```

You can either use this file or replace it with your own.

Additionally, like most things in demogen, this file can be overriden in a child directory to have a set of _sub-demos_ use a different layout entirely.

For instance, if you had a directory structure like:

```
- yourproject
|-- _sources
|-- _layout.html
|-- demo1
|-- demo.js
|-- category1
|-- _layout
|-- demo2
|-- demo.js
|-- README.md
```

Then the demo file created for demo1 (`demo1.html`) would be using the top level layout. The demo file created for demo2 (`category1-demo2.html`) would however, use the layout that exists in the `category1` folder.