Sep 30, 2014

5 Responsive Techniques for your Responsive Headache – part 1

Designer Developer

Every developer and designer has those days that no matter what you try or imagine, it just doesn’t work for your responsive site. Your idea may be a great solution for mobile devices but, it is not as user-friendly on desktop and vice versa.  You use all of your progressive enhancement knowledge and yes, it is functional but does it really meet the need of the user?  Does it really fit with the flow of the site? At times, the answer is no.

Here are a few techniques and plugins that I have found that have helped cure my…well, responsive headache.

Oct 15, 2013

Flexbox – True layout properties for CSS without a framework

Developer

We have tried everything to tame the elusive HTML layouts. We began with tables, then divs using CSS floats and even changing the display property but nothing was easy without a number of hacks and feats of magic.

Now entering, Flexbox! The flexbox module is a collection of wonderful new CSS properties that I’ve been excited about since I came across it on www.css-tricks.com and even more so, when I attended a workshop at the WebVisionEvents conference in May. It is the true layout module in CSS without a framework.

Apr 29, 2013

Shame on you…for creating all of those hacks!

Developer

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:

  1. You make them stick out like a sore thumb.
  2. You keep your ‘main’ codebase clean.
  3. You make developers aware that their hacks are made very visible.
  4. You make them easier to isolate and fix.
  5. $ git blame shame.css.

I think I will do this on my next project.

Source: http://csswizardry.com/2013/04/shame-css/