By now, you should have gotten my e-mail regarding content strategy.

As far as the browser issue(s) go, the idea is to let CSS rules handle things like curved corners and drop shadows and NOT use nested span elements and JavaScript to “fix” IE6. The IE6 users will see an OK web site, and people who use FF, Safari, etc. will see the enhanced version. By approaching it this we, we don’t need to change our mark-up in the future.

That’s great for personal Web sites, some small business sites, maybe. But, what about places that need IE6 for things like SAP or clinical applications or legacy software? Many at the conference were not inclined to let the design details slide for IE6 users, especially when IE6 comprises most of the browser traffic.

Your thoughts on designing in the grid, user testing and having a content plan are dead on. Did they have samples of content strategy documents? I could imagine that as a relatively short document (1-5 pages) outlining key messages, voice, and audience, but I wonder what you learned there?

I’m also intrigued by the statement that web sites need not look the same in all browsers. Theoretically, I’m with you. We all accept minor variances, but it seems to happen most often after hours of frustration in trying to deal with weird display problems. Is the idea meant to free developers of this sort of issue or does the philosophy go deeper than that?

See you soon!

Great post. I agree that our conferences should “keep up” if not push the edge for what is going on with the web.

And I’m looking forward to seeing your contributions over at interact.webstandards.org :)

Wish I had caught that tweet and could have taken the trip with you!

Zac