Distribute via NPM

[vovimayhem]

It's a common practice to distribute CSS frameworks via NPM, specially on projects that compile SASS & javascript - i.e. Bootstrap.

By distributing alom via NPM, we'll be enabling developers from other frameworks - i.e. ReactJS, AngularJS, EmberJS, rails, etc - to make plugins that integrate alom easily in their respective frameworks and build processes, and consequently:

• Developers will no longer have to add the CSS/SASS files directly to their projects, relying instead on their respective dependency managers (npm+yarn, rubygems+bundler, nuget, etc), and saving space / reduce code fatigue on their projects.
• Developers will be able lock down to a specific alom version, and update it /downgrade it accordingly.

It would be useful to:

• Pay attention to the "name" and "version" keys at the package.json file, as they control the package name and version you'll see (and use) in npm / npmjs.com
• Start using Git tags (With the added benefit that you'll have downloadable archives for the project)
• Consider moving/renaming the scss files to avoid any possibility of clashes with common file names:
  • Move scss/_*.scss files to scss/alom/_*.scss
  • Rename scss/base.scss to scss/alom.scss)