Make sure the asset pipeline processes scss files

[til]

Rename *.css to *.css.scss

This fixes the issue reported in #32 for me and is an alternative to PR #33 - this way rails automatically compiles the scss files.

[til]

Sorry about the slightly premature PR, since I had this lying around I thought I might as well just push it, but now realize that it is possible to use rails without scss, so this approach would not work then. Not sure what is the best way to deal with this - maybe add sass-rails as dependency?

[jordanbrock]

As mentioned in #33 I'd prefer to add sass-rails as a dependency because having raw css files just adds complexity to the project.

Yes it's possible to use rails without scss, but it's in there by default. If you're stripping components out then you've got to expect to make compromises along the way?

Thoughts?

[holetse]

I think its totally reasonable to add sass-rails as a dependency. The current version of this gem fails to work because .css is not automatically preprocessed by rails, and it contains invalid CSS. Since the gem does actually require sass-rails in its current implementation, calling out the dependency and merging this PR seems like the right away forward.

At a later point, @jordanbrock, you could explore alternatives to requiring sass-rails, but that seems to be a separate issue and one that does not need to be tackled today.

[FQ400]

+1 adding sass-rails as dependency.