Thursday 20th December, 2012
Monday 26th November, 2012
django inline css @ GitHub
We’ve been talking about this at work today. Looks really sweet for doing html emails in django.
You write good html specifying css classes, it outputs ugly but email friendly inline css. A nice way to keep your email templates DRY. If you’ve ever worked on html emails, you don’t need any more convincing.
Wednesday 21st November, 2012
In this particular (and rare) circumstance [of large websites with lots of legacy CSS], where dueling developers have added rule after rule to a huge, shapeless style sheet that is more of an archeological artifact than a reasonable example of modern code, Nicole’s admonition to avoid descendant selectors based on id is probably wise.
In response to: In Defense of Descendant Selectors and ID Elements – Jeffrey Zeldman Presents The Daily Report
Rare? RARE? What kind of dinky little disposable sites does Zeldman work on? I can’t take anything that he says at face value, because I just don’t work on the kinds of projects he works on. I’ve never worked on a serious project that didn’t have tons of jumbled css.
Also, is it just me, or do his arguments for ids just not make any sense? How is an id “more semantic” than a class name? #footer and .footer both say footer. What’s more meaningful about # than . ?
Saying you just need a master chef and permission to do some refactoring shows a lack of understanding of two things.
One. Refactoring CSS is hard. When it’s not compartmentalized in the manner of OOCSS or SMACSS it’s really, really hard. Because it’s all one jumble and you have to test everything on every change.
Two. A master chef would have to have absolute control over all html and css. I mean code review every checkin and make every dev do things the ‘right’ way. But if there’s no system of compartmentalization, then every contributor has to have just as much knowledge and comprehension as the master chef. That’s totally untenable. Each dev needs to write ‘good’ CSS on their own, or you’ll have to correct them every time.
So, those are the two main problems that OOCSS and SMACSS try to solve. In that context, I don’t think Zeldman’s arguments are very relevant.
Thursday 1st November, 2012
Monday 24th September, 2012
Tuesday 14th August, 2012
To combat this font-sizing problem, we now have access to the rem (root em) unit. This is still a relative unit, but it’s always relative to a fixed base value, which is the font size of the root element of the document (in HTML, that’s always the html element).
Monday 2nd July, 2012
Friday 29th June, 2012
Not everything always works in your favor when you design for the screen. Interaction design is engineering: it’s not about finding the perfect design, it’s finding the best compromise.
Thursday 28th June, 2012
Monday 18th June, 2012
Debunking Responsive CSS Performance Myths - igvita.com
Here’s at least one credible sounding vote for “put the css in the head and call it done.”
After reading this, you won’t be able to point to your hand built, client side css loader to prove how clever you are. But you will be able to point to your lack of hand built, client side css loader to prove how clever you are. So that’s something.