Every Module Should Have a Demo.

[gauntface]

This is a checklist of things missing from current docs.

• Every module has a demo.
  • Add some styles to demos.
  • Make it more evident as to what the demo is showing off.
• Every module has a description for the module in JSDocs.
• Every module has some JSDoc OR we have some markdown file introducing each project.
• Add examples to every method.
• Add Example of public constructor.
• Add fuller examples on each index.

[gauntface]

cc @jpmedley I'll go through this with you sometime next week to get your thoughts / input on this as well as how to use npm-publish-scripts (if you are interested).

[jpmedley]

"how to use npm-publish-scripts (if you are interested)." Never ask if I'm interested. Ask when I have the time.

[prateekbh]

@gauntface current JSDocs also $0 thingy, after every parameter. May be we can cover to remove them as well
e.g. https://github.com/GoogleChrome/sw-helpers/tree/master/packages/sw-background-sync-queue#constructor

[gauntface]

@prateekbh what is the $0 thingy you are referring to?

[addyosmani]

I have an issue for migration docs tracked at #109 - should this be folded in here or best to keep that separate?

[gauntface]

@addyosmani Keep it seperate for now - I've change the title for this to just cover Demos.

[gauntface]

Going to close this - demo's still need some love, but can be done if and when we feel it's important