Too much technology ends up smothering the actual implementation details about imager.js HOT 2 CLOSED

As mentioned in the other thread, I completely agree. Here's a proposal:

• Imager.js is the canonical location of the library, docs and a barebones example of how it works. Do we want to have Grunt tooling in place for creating a minified version of this library (but drop the current setup otherwise)?
• grunt-imager-demo - a separate repo which contains a tooling example of how to automate some of the things we've previously discussed like image generation, populating the Imager config and so on.

Our focus is on getting the first of these items out the door and then explore the second if there's sufficient interest in it. What do you think?

from imager.js.

@addyosmani totally agreed. First get repo up to scratch. Bare bones grunt for some form of 'deploy'. Then further work on a demo (likely done within this repo inside a /demo/ folder for example). Then automation and user configuration to follow. Sounds good to me.

from imager.js.