Well, folks, today officially marks the final day of CSS Insider. I've had a lot of fun blogging here for the past 7 months, and hopefully my posts have been helpful and informative to you as well. Would I say CSS Insider has changed my life? Well... I tend to shy away from hyperbole; but one fact worth noting is that if it weren't for my blogging here, I wouldn't have met and interviewed Eric Meyer, Jeffrey Zeldman, and Jason Santa Maria.

If you are so heartbroken at the thought of this blog going dark because you just can't get enough of Amber Rhea, worry not! You can find me at the Georgia Podcast Network, where I pontificate about a variety of topics; and my personal blog, Being Amber Rhea. And you might just catch me somewhere else 'round the Weblogs, Inc. network, as well.

I'll leave you with links to some of my favorite CSS news and info sites:

• A List Apart
• Position Is Everything
• css-discuss wiki
• 456 Berea St.
• CSS Beauty

Thanks, y'all.

Safari - or at least, something not unlike it - may be coming to the Windows platform. Swift is a new browser for Windows, based on Apple's WebKit rendering engine.

Swift is in the very earlier stages of development. Practically embryonic, you might even say. The repository was created a mere three weeks ago. And, as the Web Standards Project warns, "it's marked as 1.0pre alpha, and it is very much an alpha: very rough-looking UI, no scrollwheel support, pathetic form controls and I've had reports from colleagues that some folks can't even get it to install."

Nevertheless, Swift looks promising! I recommend keeping a close watch on this project. It could be very helpful to developers who need to ensure that their sites (particularly those with heavy scripting) function across browsers.

It's 2006, and we're still talking about site navigation? Yes, we are; and apparently we need all the reminders we can get, since so few sites seem to get it right. (Including, I'm well aware, CSS Insider. Don't hate; I didn't design it.)

In his new A List Apart article ("Where Am I?"), Derek Powazek slaps us upside the head, again, with the cardinal rules of web site navigation. From any page on a site, a user should be able to easily answer these three questions:

1. Where am I?
2. Where can I go?
3. Where have I been?

So simple, and yet somehow, so elusive to many designers.

Derek provides visual examples of great site navigation. Put your site to the test! Do you know where you are, where you've been, and where you're going?

What 'til you see this thing. Craziness, I tell you! James at Brothercake has created a 3D dungeon model through clever manipulation of CSS and the DOM. It even has correct shading - done on the fly! - to effectively convey perspective.

How did he do it? The solution builds off of Tantek Çelik's Study of Regular Polygons (which is fascinating in its own right), adding some Javascript to accomplish the shading. Check out the examples at Brothercake and appreciate CSS borders in a way you never thought possible. (You can even navigate through the CSS-based underworld!)

In an article entitled "Visual vs. Structural," Tommy Olsson compares the two most typical - and often competing - web design approaches: visual design and structural design. The balanced and well-written article makes the point that while there are often no major differences in the code produced from one design approach or another, using a structural approach can result in more accessible sites.

While I hesitate to use such loaded words as "better," I definitely agree that structural design can contribute to a product that is more scalable, easier to maintain, and more accessible. (I say this from the perspective of someone who has employed both approaches at one time or another.) And remember, "accessibility" doesn't just mean "blind people." As the web moves away from being confined to the desktop computer, accessibility is as much about accommodating mobile technologies as it is about making sure content is available to disabled users.

Looks like Microsoft is the latest to be guilty of a failed redesign. Their current homepage iteration sports a table-based layout circa 1998.

They've also released a beta preview of their new new homepage - which you can view only with Internet Explorer. (When I attempted to view the preview site in Firefox, I was simply redirected to the existing homepage.) The preview site appears to use semantic markup, although the source has been compacted down to only a few lines, so it's nearly impossible to read. And with no Web Developer extension in IE, outlining all block-level elements (or all table cells) isn't an option.

Funny that with the IE 7 team touting how standards-compliant the new browser will be, the Microsoft homepage flies in the face of standards. (Is that for-real ironic or only Alanis ironic?) Having worked for a few large corporations, I understand that one department's products can appear to be the antithesis of another department's, with the worker bees in both departments being none the wiser. Still, this is pretty egregious, given the emphasis Microsoft claims to be placing on web standards.

Although... we've been there before with Microsoft, haven't we? Perhaps these things are cyclical.

According to a post on IEBlog, IE 7 will be distributed via WIndows Automatic Updates.

I'm confused now, because in the interview with Chris Wilson that I linked to yesterday, Chris seemed to definitely say that Microsoft won't go that route in distributing updates. Or maybe when he said "pushing it out" he was referring to something other than Automatic Updates...?

Hmmm...

Vitamin has an interview with Chris Wilson, Group Program Manager of the Internet Explorer Platform team at Microsoft. They're not calling it a podcast, but I'm going to. (Being a podcaster myself, I'm capable only of speaking in hip web terminology.) At just over 5 minutes, it's a quick and easy listen.

Topics discussed include: the new features of IE 7, Microsoft's involvement with the Web Standards Project, and the process of updating to IE 7. Chris WIlson's turn-ons include: RSS, Flickr, and working closely with the web development community.

It's true that IE is the most notorious browser for inconsistencies, incompatibilities, and bugs. But the fact remains that no two browsers are created equal, and while IE is the most likely to cause headaches in the course of development, other browsers can be culprits, as well.

If you run into a major roadblock, Rafael Lima's CSS Browser Selector could be your saving grace. A tiny bit of Javascript (less than 1kb!) determines the user's browser and creates an accordingly-named class. From there, it's simply a matter of applying the styles that were written for that particular browser. For example:

.ie .example {
background-color: yellow
}
.gecko .example {
background-color: gray
}
.opera .example {
background-color: green
}
.konqueror .example {
background-color: blue
}
.webkit .example {
background-color: black
}
.example {
width: 100px;
height: 100px;
background-color: brown;
}

The colored box on the CSS Browser Selector page gets the point across better than anything else, though. Open the page in a few different browsers to see for yourself.

While we're on the subject of new browsers...

• Firefox 2 beta 1 is now available as a developer preview, for testing purposes only. (I guess that's a little redundant, isn't it?) Its features include: support for Javacsript 1.7; inline spell checking in text boxes; and the ability to reopen accidentally-closed tabs (I definitely need that one, with my command-W-happy fingers).
• Opera 9 has been released, with a lot of cool new features. To name just a few, it boasts built-in BitTorrent, thumbnail site preview, and one-click ad blocking. And there's more, so much more!
• All the cool kids are talking about Flock, with its built-in blog integration and photobar. If that doesn't have "Web 2.0" written all over it, I don't know what does.

Check out this Slashdot interview with Håkon Wium Lie, the originator of the CSS idea. (Can you believe it's been over 10 years since CSS was proposed? Time flies when you're coding with tables!) Lie currently serves as CTO of Opera Software.

In the interview, Lie suggests that before releasing IE 7, Microsoft should ensure that the browser passes the Acid2 test and supports TrueType downloadable fonts. He also discusses XML, microformats, Ajax, and (of course) the future of CSS. Read the interview and watch him effortlessly knock down all suggestions that CSS is somehow lacking in capabilities.

Internet Explorer 7 Beta 3 has been announced and is now available for download. Features include tabbed browsing, RSS integration, multiple search engines via the built-in search box, and more. Sure, these are all features that Firefox, Safari, etc. have had for a quite some time, but as the old saying goes, better late than pregnant. There are no new CSS features, however; Microsoft has stayed true to their promise that, for better or for worse, as of this March IE 7 was "layout complete."

In his article "HTML's a Tag Too," Bryan Veloso discusses the benefits of applying styles to the <html> element. He argues that by making more effective use of <html>, developers could eliminate the need for a wrapper div. Everything would effectively be "moved up" a level - apply global styles to <html> instead of <body>, and then <body> can serve the same purpose as the wrapper div would have. Bryan points out that this can be particularly handy in XHTML 1.1, in which the <body> no longer stretches the entire length of the page.

It's a neat idea, but for many developers - particularly those of us who work on large, enterprise-level sites - it is simply impractical. On large sites, rarely would you want to declare a global background image, for example. Or, you may not be able to access certain elements of a page at all, due to CMS limitations or other restrictions. However, for a small-scale site, styling <html> could be a good way to reduce divitis, as long as you're mindful of scalability issues.

A few weeks ago, I mentioned the nominees and categories for the CSS World Awards, presented by CSS Mania. Well, the winners have been announced! They were selected by a panel of judges made up of industry experts such as Molly Holzschlag and Andy Budd; so you can bet these web sites are truly the cream of this year's CSS crop.

You can view the full list of winners at the CSS World Awards site, but a few noteworthy selections include:

• Site of the Year, 3rd place and Media, 3rd place: Vitamin. This new resource for developers combines information about web development, graphic design, server-side programming, and more into one tasty info-morsel. It's been around for only a few months, but I've already consulted it more times than I can count. (Not surprisingly, I think it should've won 1st place, but...)
• Blogging, 1st place and Web Design (Companies and Portfolios), 1st place: Simplebits. The list of Dan Cederholm's contributions to the web design and development community just keeps getting longer (and his blog has been a mainstay in my RSS reader for a long time). This award is well-deserved.
• Portal, 1st place: CSS Beauty. Finally, a site that centralizes job openings for CSS geeks! Oh, but that's not all they've got. Here's a tip: whenever things get slow 'round here, head over to CSS Beauty for a while. You won't be disappointed.

Now it's time for everyone to get cracking on their best CSS kung-fu, in preparation for next year's awards.

Got opinions about the outcome of the 1st annual CSS World Awards? Share 'em here!

Check out the latest edition of A List Apart, featuring a fascinating article on automatic magazine layout of images. The technique utilizes server-side technology to calculate where the images should be placed, but of course, CSS had to be used for positioning within the rendered page. The potential for IE-related problems seemed to loom hugely on the horizon as I read the article, but once I got to the section that explained the CSS, I saw that Harvey Kane's solution is beautifully simple and effective.

Oh, and while you're at A List Apart? Bid a fond farewell to the <embed> element.