Issue #9: Progress towards SCSS restructure.

[patrickbrown-dev]

No description provided.

[asoules]

The only issue using application.scss instead of application.css is that the files will be concatenated in development, which means that you won't know which classes are coming from which files when you inspect elements in the browser. This is a big enough downside that I usually opt to use application.css and then include any mixins or variables in each file that requires them.

[patrickbrown-dev]

Okay cool -- I'll send the amended code in another pull request sometime today!

On Wed, Jun 11, 2014 at 07:16:14AM -0700, Aaron Soules wrote:

The only issue using application.scss instead of application.css is that the files will be concatenated in development, which means that you won't know which classes are coming from which files when you inspect elements in the browser. This is a big enough downside that I usually opt to use application.css and then include any mixins or variables in each file that requires them.

---

Reply to this email directly or view it on GitHub:
#25 (comment)