Linting your Sass is a great way to ensure some degree of code quality. At the very least you will have greater stylistic consistency.
One thing before we get started: be careful not to blindly follow what a linter says, though: treat linter rules as guidelines, not absolutes .
In my text editor of choice, Sublime Text 3, the best way to get linting in any language is currently using the Sublime Linter package. Once that is installed, you can install extension packages for each language you want to lint.
In my case, the main ones are Sass (as
I had been looking to change web hosts for a while, and thought I’d try out one of the hosts that was offering an SSD option.
I’ve also been learning a lot lately about performance, and how that is measured. This was a perfect opportunity to test the effect of an SSD server. Since I was moving my site, and changing nothing else about it, this seemed like a good comparison.
There was a situation where we had some breadcrumbs being produced by a CMS. The problem was that the breadcrumb appeared on the top-level page as well as it’s children pages. On the top level page it came across very redundant, and this single level breadcrumb would appear right above the page title. However, we wanted the breadcrumb trail to still appear on the second level pages.
Ideally, this kind of situation would be dealt with at the template level, and the markup would simply be absent. In this case, we couldn’t change the template, we could only change the CSS.
The solution was the CSS :only-child pseudo selector.