Reputation: 597
I am a bit conflicted on whether to have seperate .scss/css files for things like header, homepage, about page
Then on the other side having them all imported into one global.scss file.
In terms of fixing the issue through the DOM, you then have to then find out what line of css it is on, then go to the relevant scss file to change it and correct the problem.
So my question is, what is the best practice. I understand that compiling into one css file and minifying it is best practice but in terms of debugging I would think that having separate scss/css files would prove to be the better option?
Thanks for any advice or experience
Upvotes: 0
Views: 39
Reputation: 557
Your sass compiler has the option to generate a .map file which maps your css to the lines of code in your sass file while debugging (using inspect element e.t.c).
There is not really a best practice universally , as there are many factors to consider such as compiling sass libraries (susy/bootstrap), or collaboration between multiple developers.
At the end of the day though it really comes down to what works best for you.
Upvotes: 1