Nuget Packages You May Not want to use

    This is just a thought and in my opinion, I feel that there are certain packages in Nuget that include css files  in which developers should use with caution. A good example is Bootstrap, which you should try using less instead of your own css file other customizing the bootstrap css. The reason for this is because less allows you to separate your styles from the root of bootstrap and makes it simpler for later updates with bootstrap. Not to mention the possibility of changing the third party libraries that you might be using. If the library you are using isn't in a less format I would be worried about customizing it because it would only make things harder for when you want to move away to something else.
    I think most developers out there are using Jquery UI or bootstrap but not many are using less which puts a lot of projects in danger for restyling and restructuring their code. I've made it my goal to try and not to separate css files into more than one css in production. With Asp.net it is very helpful to bundles css files together, but this might not be possible in all project or in non-asp.net application. Still with less I think developers should has no problem doing so. Also if you use less and have similar styles across multiple projects using less is another plus! So there are many reasons to use less over the traditional ways.

Resources
https://github.com/twbs/bootstrap#compiling-css-and-javascript
http://lesscss.org/

Popular posts from this blog

UI-Bootstrap Collapsible Sticky Footer

Installing Windows on Acer chromebook 15 cb3-532

Aspetcore: NLog with Postgresql