It seems as if someone has finally cracked the problem of running multiple standalone versions of Internet Explorer under Vista.

In my last post I outlined some of the problems that might arise from the proposed version targeting changes to Internet Explorer 8. My major concern was that by removing the motivation for web authors to update legacy sites, version targeting might hamper the adoption of modern web development techniques. During the week I have given some more thought to this issue, and it occurred to me that in Adobe Flash we have a fantastic real-world test case from which we might learn if version targeting is a viable strategy for a web browser.

When Dean Hachamovitch demonstrated in December that the forthcoming Internet Explorer 8 browser passed the Acid2 test in standards mode, there were calls for Microsoft to clarify if “standards mode” was the default setting for IE8. Last week it was announced on A List Apart and the Internet Explorer blog that IE8 will render pages using an IE7-level rendering engine by default, and that web developers must opt-in to take advantage of the new Acid2-compliant rendering mode.

When I started out as a web designer, content management systems belonged strictly to the realm of big budget websites. For everyone else, it was perfectly normal for a web designer to manually update a site whenever a change needed to be made. Clients didn’t expect a CMS to be included with their website, and web designers didn’t offer the option. Times have certainly changed, and in an age of blogs, Facebook, and MySpace, clients expect to be able to take control of their website’s content.

For most web designers, especially those who work solo, a custom built content management system is still a tall order. Fortunately there are numerous commercial and open source content management systems available, which offer a practical and affordable means of wrangling content. However, a “one size fits all” content management system that doesn’t address a site’s specific content requirements can introduce as many problems as it solves.

Almost exactly a year ago I was musing about the possibility of dropping support for Internet Explorer 5 when testing websites. Time marches on, and now we are seeing calls to ditch support for IE6 too.

Like many web designers, Photoshop is my tool of preference when it comes to doing website mockups. As such, I spend a decent chunk of my time working with the program, and have picked up a number of techniques that speed up my workflow. I’m not talking about creating shiny image reflections, or beveled starbursts, but rather simple tricks that shave a few minutes off your working day so you can go home earlier.

Big news from the Apple camp - Safari is now available for Windows! For Windows-based web designers this is exciting news, meaning it is now possible to test websites in Safari without needing a Mac at hand. The final version of Safari 3 will be released later this year, but you can get your hands on the beta version right now.

A couple of months back I wrote a post about the importance of making links look like links. From the comments left by readers it was clear that peoples opinions differ widely on the best way to style links, so I thought I’d follow up with a brief survey of the various ways it is possible to make links stand out on a page.

One of my clients is currently optimizing their website for search engines. As part of the process I met with a rep from an SEO firm, who suggested ways the website design could be tweaked to be as friendly as possible to search engines. Most of the ground he covered was not new to me, but one tip was an eye opener: he advised me to entirely remove the meta keywords tags from the website.

An article on the importance of making hyperlinks stand out might seem like an exercise in stating the obvious. I would have thought so too, until I came across the portfolio site of a reputable web design firm last week and found myself playing a game of link hide-and-seek.