Full Disclosure » CSS

CSS Shaders Coming.

Nate — Tue, 18 Oct 2011 16:22:41 +0000

Adobe sends a proposal to the W3C that introduces advanced filters for use on DOM elements. The open web stack has a long way to go before it has the power of native layout, graphics, storage, logic, etc., but at the very least it’s reassuring to see it continually advancing. Oh, and welcome aboard, Adobe.

Better Restaurant Menus.

Nate — Tue, 18 Oct 2011 15:48:05 +0000

Unit Interactive decided to throw together a little demo of how to make a better restaurant menu. Anything’s better than Flash or PDFs.

SMACSS

Nate — Sat, 08 Oct 2011 03:05:07 +0000

I’m only part of the way through the first chapter, but it’s so good that I’m pre-emptively recommending Jonathan Snook’s extended write up of his CSS architecture and guidelines, SMACSS. If nothing else, it’s worth examining your own practices in light of Jonathan’s extensive experience.

Coloratum.

Nate — Sat, 03 Sep 2011 03:44:43 +0000

So much to love in Lea Verou’s CSS Coloratum. Convert colors to CSS values.

Whenever I wanted to convert a CSS named color to RGB, I used to open the CSS3 colors spec in a new tab, search in the page and copied the values. Every time it felt even more tedious. I didn’t want to search in long tables, I wanted to type the color somewhere and get the values back, in an easy to copy format. So, after yet another color lookup earlier today, I decided to scratch my own itch and do it myself.

Of course, I didn’t plan to include a whole database of CSS colors in the website. My idea was much simpler: Use the named color to draw a rectangle in a

Read the rest of her description.

BagCheck Separates Mobile and Desktop.

Nate — Thu, 01 Sep 2011 15:35:49 +0000

A common sense explanation from Luke Wroblewski on why BagCheck doesn’t try to serve a single HTML page to both mobile and desktop users:

A desire to optimize source order, media, URL structure, and application designs made separate mobile and desktop templates a great fit for us.

Responsive web design isn’t a panacea, and to be clear, nobody who understands it is promoting is as such. Yet there seems to be a disproportionate amount of hype relative to its advantages. Can you provide a marginally better experience at different browser resolutions using the responsive web design principles? Yep. Should you solve every problem at the CSS level? Absolutely not. We have a lot of tools including HTML, JavaScript, and server languages available to us to accommodate the radically different ways people interact with our content and applications. We should use whatever best suits the situation. That’s not a particularly bold or esoteric statement, but it bears repeating from time to time.

HTML5 Boilerplate 2.0.

Nate — Thu, 11 Aug 2011 02:18:05 +0000

It’s not something I’ve been using, but HTML5 Boilerplate seems like good stuff. A lot of smart people put this thing together, and now it’s at version 2.0. Maybe it’s time.

The Expressive Web by Adobe.

Nate — Wed, 03 Aug 2011 12:41:30 +0000

Impressive demo of HTML, CSS and JavaScript: The Expressive Web.

Chrome Developer Tools.

Nate — Wed, 18 May 2011 18:35:17 +0000

Paul Irish makes the Chrome developer tools look so nice, yet no matter how many times I try to switch away from Firebug, I can’t.

Ceaser: CSS Easing GUI.

Nate — Wed, 23 Mar 2011 13:39:59 +0000

Another site to add to your bag of tools-that-make-complex-CSS-easier. Ceaser enables designers (and developers) to tweak CSS transitions in a visual and instantaneous way.

Using HTML5 Elements Without JavaScript.

Nate — Wed, 23 Mar 2011 02:24:06 +0000

If using JavaScript to cram support for HTML5 elements into your CSS offends you, Tantek Çelik and Nicholas Zakas have a solution for you: nest a block-level element inside your semantic HTML5 element and style it instead.