Make cadence npm-compatible.

[cburschka]

NPM, the NodeJS Package Manager, seems to be the hot thing for all JavaScript-based software now.

If we can work out a good way to sanitize our build process, maybe move away from the somewhat haphazard Makefile + Python-based templating system toward something a bit more intuitive, cadence might be publishable.

[cburschka]

Writing this down here because I can't find a better place right now: We need to distinguish between deploy and build process. The current makefile does both at once, and they can't be easily separated. That's what switching to a modern deploy/build tool requires.

[cburschka]

Writing this down here because I can't find a better place right now: We need to distinguish between deploy and build process. The current makefile does both at once, and they can't be easily separated. That's what switching to a modern deploy/build tool requires.

This is still relevant, and the biggest impediment to a clean build process.

Make (disregarding the install target) currently has these tasks:

• translate and copy script sources into lib/
• copy emoticon packages into assets/ and generate emoticons.js
• render the index.html and config.js templates

The first of these is part of the build process, the latter two are part of the deployment.