New Feature: Getting Started With Handling CSS

[crimson-knight]

It's time to introduce CSS handling into the shard. There's a basic ways for handling CSS that I think that the shard should handle at least in the first iteration.

Specifically, in the beginning, we want to be able to handle CSS file similarly to how we handle group files where processing isn't happening, but we're still creating a fingerprint and caching the file. The file fingerprint is based on the files contents, and then the hash is calculated and added into the file name. This fingerprinting process helps significantly with preventing issues related to browser.

1. The starting directory is a src-like directory for the shard to reference and iterate over find files, create fingerprint for each file, and then an output directory where the file with the fingerprinted file name will go.
2. A file watcher process that: watches for file changes, performs the finger printing process and moving the file, then sends an update to the browser to update the source files.

Updating the browser so it doesn't require a full page refresh would make the process of front-end development a much more pleasant experience with Asset Pipeline in general.