Eric Meyer: The Lessons of CSS Frameworks
ma.gnolia tags : web design forms css js Design Technology computerscience concept Video high resolution effects digital photography html email mention website sql tools mysql templates math tutorial highschool middleschool psychology personality creative manga generator avatar fun iphone webdev development webkit panic stevenfrank itunes 2008-33 aloestudiosnews web development movabletype wordpress sixapart blogging icons starwars parody homage EricMeyer jeremykeith aneventapart
added 2008 Mon Aug 18 7:00:00 by unknown user
Again from Jeremy's great live blogging of An Event Apart San Francisco, here's Eric on CSS frameworks. I'm glad to see someone else broaching this topic, and in general it looks like Eric did a great job of rounding 'em up. A few bits and responses: > If you?re going to use a framework, it should be yours; one that you?ve created. You can look at existing frameworks for ideas and hack at it. But the professionals in this room are not well served by picking up a framework and using it as-is. Generally speaking, I agree. I have made great use of Blueprint -- but it's worth nothing that almost all of the basic concepts were created by me (along with Nathan and Christian). As Blueprint has progressed, it's gotten farther and farther away from what we created, and I've been less enthralled by it. The point is: something you created yourself is always going to be more useful to you than something you didn't. > Four of them use psuedo-namespaced class names beginning with grid- or container- or span- (which you would apply to a div!?). I'm not sure if the parenthetical is Jeremy or Eric speaking, but this is also worth noting: in the original CSS framework Nathan, Christian, and I created, you were *not* necessarily supposed to apply those classes to a `div`. The classes were for *any* element, and there was *no* encouragement to liter your markup with extraneous `div` elements. The original Blueprint retained this philosophy, but later changed it, asking people to always use `div` elements as columns. I find this to be incredibly wrong, and I always override this Blueprint functionality when I use the framework. If you are going to use a `div` for every layout column/row/unit/whatever, you may as well just use tables. I hope everyone knows and understands that when I was touting Blueprint, it was before the made the boneheaded decision to require the use of a `div` element for every column. Saved By: Jeff Croft | View Details | Give Thanks
Again from Jeremy's great live blogging of An Event Apart San Francisco, here's Eric on CSS frameworks. I'm glad to see someone else broaching this topic, and in general it looks like Eric did a great job of rounding 'em up. A few bits and responses: > If you?re going to use a framework, it should be yours; one that you?ve created. You can look at existing frameworks for ideas and hack at it. But the professionals in this room are not well served by picking up a framework and using it as-is. Generally speaking, I agree. I have made great use of Blueprint -- but it's worth nothing that almost all of the basic concepts were created by me (along with Nathan and Christian). As Blueprint has progressed, it's gotten farther and farther away from what we created, and I've been less enthralled by it. The point is: something you created yourself is always going to be more useful to you than something you didn't. > Four of them use psuedo-namespaced class names beginning with grid- or container- or span- (which you would apply to a div!?). I'm not sure if the parenthetical is Jeremy or Eric speaking, but this is also worth noting: in the original CSS framework Nathan, Christian, and I created, you were *not* necessarily supposed to apply those classes to a `div`. The classes were for *any* element, and there was *no* encouragement to liter your markup with extraneous `div` elements. The original Blueprint retained this philosophy, but later changed it, asking people to always use `div` elements as columns. I find this to be incredibly wrong, and I always override this Blueprint functionality when I use the framework. If you are going to use a `div` for every layout column/row/unit/whatever, you may as well just use tables. I hope everyone knows and understands that when I was touting Blueprint, it was before the made the boneheaded decision to require the use of a `div` element for every column. Saved By: Jeff Croft | View Details | Give Thanks
Eric Meyer?s CSS Sculptor
ma.gnolia tags : Design type blog print css framework blueprint generator google maps embed tools gtd development user interface information architecture html reset standard None assigned andyrutledge business webdesign textbooks statistitics tutorial retroland social community book web instruction jquery javascript tables EricMeyer dreamweaver Adobe
added 2007 Thu Aug 23 7:00:00 by unknown user
Eric Meyer?s CSS layout generator, created in collaboration with WebAssist, makes it easy for Dreamweaver users to create standards-compliant CSS-based layouts. Saved By: jeffrey zeldman | View Details | Give Thanks
Eric Meyer?s CSS layout generator, created in collaboration with WebAssist, makes it easy for Dreamweaver users to create standards-compliant CSS-based layouts. Saved By: jeffrey zeldman | View Details | Give Thanks
Formal Weirdness
ma.gnolia tags : webdesign webdevelopment css html inspiration Design grid system:unfiled cool flickr Earth None assigned wear free funny beauty photography photoshop webdev tools css technique flag personal reference product bibliography mla apa community trolling trollwhisperer development csstechniques forms EricMeyer
added 2007 Thu May 17 7:00:00 by unknown user
Great post on why styling forms is so problematic & inconsistent
Great post on why styling forms is so problematic & inconsistent
