.net 176 on design screw-ups

It’s not often these days that I get catharsis when writing articles, but for .net 176 I got to vent, albeit through the words of others. Having worked on an overview of grid design for the previous issue (interesting and essential, but also very regimented subject matter), 176’s feature is about the top-ten design mistakes, including such gems as making Flash websites that look like HTML web pages, and version capping (telling people to ‘upgrade’ to a lower version of a plug-in or browser, because you stupidly set the then-current version as the sole requirement).

However, great fun as all this was, my own comment was mercilessly cut by the brutal editor (nothing to do with the fact that there simply wasn’t room, obviously), and it read: “When linking to PDFs, make that very clear, to avoid users’ browsers freezing up while Adobe Reader invades, leading to wailing, gnashing of teeth, and the subsequent ejection of laptops out of nearby windows.”

It amazes me that many web designers still do this sort of thing, even linking directly to a PDF from a site’s primary navigation. This, for me, is a design crime for which the culprit should be tarred, feathered, tarred again, and then dropped down a really deep well. Head first. Aaaand… relax.

You can grab the latest .net from netmag.co.uk, and if you’re outside of the UK, it’s called Practical Web Design for reasons that I still don’t entirely understand.

.net 176 design mistakes article

Luckily, the above .net image is not shown at full size.