http://jeremykeith.web2announcer.com/ Web 2.0 announcer top stories for jeremykeith en Mon, 18 Aug 2008 07:00:00 GMT http://web2announcer.com/go/2743087 unknown@ma.gnolia.com 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 Mon, 18 Aug 2008 07:00:00 GMT http://web2announcer.com/go/2743087web designformscssjsDesignTechnologycomputerscienceconceptVideohigh resolutioneffectsdigital photographyhtmlemailmentionwebsitesql toolsmysqltemplatesmathtutorialhighschoolmiddleschoolpsychologypersonalitycreativemangageneratoravatarfuniphonewebdevdevelopmentwebkitpanicstevenfrankitunes2008-33aloestudiosnewsweb developmentmovabletypewordpresssixapartbloggingiconsstarwarsparodyhomageEricMeyerjeremykeithaneventapart http://web2announcer.com/go/2077742 unknown@ma.gnolia.com Jeremy has a nice post on how you can intermix microformats, rather than creating new ones or extending existing ones. For example, rather than adding a "date of death" field to hCard, why not mark something up as both an hCard and an hCalendar event -- the hCard comtains all the person details, and the event (the person's life) has a start an end date. No need for a "date of death" field. Jeremy's got other smart examples, too. Because I sometimes I get asked about my feelings on microformats (people have noticed that I don't ever really talk about them), here they are: Microformats are a very good idea, and they can do no harm. They're just regular, semantic HTML, so implementing them is easy and non-controversial in my mind. However, I don't feel like they *currently* add much value, because there are so few useful tools for consuming them. Yes, I know there are Firefox extensions and such -- but where are the microformat tools that are going to benefit my Mom or my Grandma? Also, I sometimes wonder why one wouldn't simply add a read-only REST API to their site, instead of encoding everything in microformats. It seems simpler and less fragile to me. So, bottom line: I haven't gotten into microformats much myself. Not because I don't think they're a good idea. In theory, they are. But more because I haven't seen a lot of real-world benefit to taking the time -- yet. The flip side is that the time I would have to take is pretty minimal, and implementing them on my sites could do no harm (even if I don't think it would do much good, either). Mon, 02 Jul 2007 07:00:00 GMT http://web2announcer.com/go/2077742world clockbirthdeadStatisticsopen designstemplatescss templateswebdesignDesignartguidesNone assignedwhiteboarddiyDaring_FireballJohn_GruberiphoneicalwebdevjavascriptProgrammingajaxmicroformatsjeremykeithhtmlxhtml