Lately I’ve been going through lots of CV’s, as Canonical, the company I work for, is hiring a multitude of visual designers, user experience architects, front-end developers, etc.
CSS frameworks have a tendency to be dismissed by many CSS authors; code bloat and non-semantic class names are usually at the top of the list of reasons why. Even without ever using one, I shared the same opinion, but that might have changed after trying a few of them out while doing some research recently…
I’ve started using LESS a few months ago on a few projects. LESS allows you to extend the way you write CSS, letting you use variables, nested selectors, operations and mixins. It sounds great — and it is great — but there are a few things that can make it work against you. These are some of my thoughts on LESS.
Ever wanted to use fallback fonts on your CSS with different aspect ratios without them looking huge (or tiny)? The sparkling new CSS3
font-size-adjust property could do just that, maybe.
I’m in love with the simplicity that CSS3 selectors can bring to our stylesheets. Here’s a brief explanation of one of my favourites: the
A post by Darren Hoyt caught my eye the other day (among the hundreds of unread posts on my RSS reader…) where he asked whether designers needed a personal style or not. I wrote up a quick comment at the time, but I feel the question deserves a little more discussion — specially because no-one seems to have a definite answer (my bet is that there isn’t one).