In a recent article I went through some of the basics using image optimization with Grunt. Since I went through the steps with Grunt it only seems fitting to share what it looks like when optimizing images with brew packages. For those that are not familiar with brew (i.e Homebrew), it’s a package manager for Mac. Homebrew installs the stuff you need that Apple didn’t.
Fuck me sideways I was totally screwed Wednesday morning when my Code Editor decided to shit the bed. I must have said everything in the book about Sublime Text 2 like “This piece of shit sucks” or “Support sucks monkey balls! I fucking hate you Sublime Text!” I mean I was soooooo frustrated. Basically I was freaking out and throwing up! So much so that I almost downloaded Text Mate for god sakes! Holy shit that was close. Well thankfully for all of you I’ve made a point to document my struggles and make life a bit easier in case of an attack by the package boogie monster.
You may or may not be new to Grunt, and as you become more comfortable using it you’ll most likely desire diving into other aspects of the tool chain in order to expand upon tasks like code linting, pre-processor compiling and especially image optimization which is the task we’ll be discussing today.
@font-face helper is designed to let authors install custom fonts directly into a style sheet without writing out the entire
@font-face declaration that looks something like the following…
I’ve always been on the fence when it comes to using a GUI over the CLI to transfer/update files on a remote server. For the majority of my work I use Fetch when I need to transfer or grab single files and sometimes I will even go as far as mirroring with Fetch to sync entire projects. There are better ways for sure, but I really wanted to see what else is out there and the benefits of each method/tool available (ones that don’t use a GUI at all!). I decided to take to the tweeters in hopes that other developers would provide me with some feedback/opinions.
“Hey you, Sass developers who use variables for media queries! How do you decide what to name the media queries?” It’s a pretty common question in programming languages other than Sass, and one that is always the toughest to decide.
When Chris Van Patten asked in this tweet there were a few replies. Some answers assorted and some similar. If you aren’t aware of Chris Coyier’s post on naming conventions then be sure to check that out before reading further. It’s what I call “the bear approach.”