Discover innovative tools, design features, unique websites, and code structure curated by the GoWeb community.
View the resources by category or by monthly GeekOut! Compilations. Check out the latest compilation below.
< Back to
Shame on you…for creating all of those hacks!
Hello everyone. ?My name is Xavier and I sometimes … add hacks to my CSS. I thought I should be the first to admit this. You don’t do this? Are you sure? Well, if you have ever used !important or overflow:hidden to “fix” a quick problem to get the site out of the door, then yes, you hacked your CSS instead of figuring out the problem.
I found this article?by Harry Roberts and thought it quite funny, and convicting and true at the same time. He suggests separating our quick, dirty and tacky CSS into a new file named “shame.css” instead of keeping it in our well-defined CSS. ?He states:
By putting your bodges, hacks and quick-fixes in their own file you do a few things:
- You make them stick out like a sore thumb.
- You keep your ?main? codebase clean.
- You make developers aware that their hacks are made very visible.
- You make them easier to isolate and fix.
$ git blame shame.css.
I think I will do this on my next project.