Break Plugins into Seperate Repositories

[ChristianMurphy]

As the project grows and plugins become more diverse, it would be best for each plugin to have its own repository.

To be able to use plugins, they would need to be bundled. Most likely using NPM packages or git submodules.

Currently the preferred method would be using NPM packages, and offering a thin wrapper around NPM to simplify the installation process. Something even simpler than APM.

This currently presents a number of challenges:

1. Where and how to install packages on the client.
2. How Nicest recognizes a package is a Nicest package and not another type.
3. How to generate and include the JSDoc from across multiple sources.
4. How modules will manage peer dependencies (which are no longer downloaded by NPM).
5. How shared Jade templates can be loaded in plugins.

[ChristianMurphy]

Rejoice could be a good way to manage custom server configurations.

[ChristianMurphy]

At this point in time, I'm going to leave this as is.
And reconsider if a real need should arise.