David on Web Design
I've been taken to task by more than a few "professionals" on my page design and coding style. It's been called old-fashioned. Excessively rigid. Uncreative. Boring. And a bunch of other things I won't bother to repeat. First of all, I'm no beginner; I've been doing this since the early 1990s, and recently retired from a job programming advanced database-driven web applications.
While most young-uns may think the Internet has zoomed past me, all it's really done is gotten needlessly complex. I've always seen the primary purpose of the Internet as a source of information. Indeed, that was its founding mission. And while it's all well and good that it's gone on to provide entertainment and other services, when performing the task of conveying content, the content was, is and must always remain the single most important element. Page design—including the type fonts used—must service the core mission, that of conveying the content. Fancy page layout and, in particular, unreadable fonts only obfuscate the content, rendering a site's usefulness moot. Trust me, having a degree in graphic design and years of typography under my belt, I know what I'm talking about.
It's been long-known that animated elements in a page diminish one's ability to read the text. Back in the late 1990s, when animated gifs were all the rage the first time around (they're unfortunately enjoying a renaissance), they were often frowned upon by professional designers. But since the internet has become largely monetized, the problem has only gotten worse, because most ads are animated, and some even have sound. And ads are never going away; indeed, some sites go so far as to deny access for visitors who use ad-blocking software. Oh well, guess I really didn't want to look at that crap site after all.
As for my own page style, specifically the 600-pixel width, I offer advance warning that no one can convince me to change. Recently a web developer complained to me that most of his screen is "white emptiness." Yet on his own website, the text runs the full width, making it painful to read when viewed on a large monitor. What is more important, content or eye-candy? It's why newspapers and magazines have these things called columns—they make the content easier to read. And, if you pay attention, most grown-up web developers who understand the concept of readability keep columns of copy to between 500 and 600 pixels in width, and fill in the rest of the page with graphics, sidebars or (shudder) ads.
Well, if I insist on narrow-ish columns, why don't I use more of them to fill up the page? For starters, I must remind the wide-screen owners that not everyone is blessed the way you are; there are still plenty of folks with little old 600 x 800 screens—I personally know a few, believe it or not. Which means I'd need to code pages to optionally display different numbers of columns, and that's way, way too much work than it's worth just to fill in the negative space over there on the right. So, when you're faced with "too much" white space, how about reducing the size of your browser window? That's what I do (and I have one of the largest monitors made). Anyway, my page layout seems to be well-suited to mobile browsers—an unintended double-bonus, since it means I don't need to code two page layouts, one each for the mobile crowd and everybody else.
But table-based page layout? Seriously? Didn't that die out with the dinosaurs? As it happens, the much-ballyhooed CSS method of page layout is prone to failure: even the latest browsers do not consistently or reliably interpret CSS, and consequently many websites—including big-name, high-profile commercial sites—are kinda flakey around the edges. Worse, some pages completely explode into a laughable jumbled mess. Are people actually being paid to code such crap? Someone take their pacifiers away.
Many sites now go though spastic transformations as they load, with text changing font, size and weight five or six times before settling down, while graphic elements resize themselves and jump from place to place on a page. I sometimes feel as though I should take Dramamine before surfing. WTF? Not to mention that pages are taking longer and longer to load, even with broadband, often due to entirely unwanted auto-play videos rammed down our throats. Proof that man fills all available space (and bandwidth) with excrement.
Getting back to code, I've found CSS is serviceable for such things as font styles and other low-priority tasks, but that's about as far as I'll trust it. All the rest I still do with tables, because they've always been rendered reliably—from the earliest days of the Internet—and I'll place bets they always will. Have a look at my code: you won't see anything but a few standard tags. Anyone who needs more is over-designing a page, which diminishes readability.
Back in the day, better coders proudly displayed "optimized for any browser" on their home pages. After all, since content is king, it should be available to anyone by any means. Since then, I'd thought we'd gotten past the nonsense of browser-specific websites. Boy was I wrong! I've recently hit some sites that warned they could not be viewed in anything but the very latest browser version. Well, I guess they really don't want my business! What kind of drugs are these people on, anyway? Who in their right mind would deliberately exclude a sizeable percentage of their potential eyeballs just to make some gizmos spin? Give me a break.
I've been told that my pages are boring. Do I need dancing bears to hold someone's attention? If a visitor is bored, then it's a function of the content not being in alignment with the their interests. And if people who might be interested don't stick around, then it's a function of the quality of the content, not the page design. To that end, I always do my best to generate the highest quality content possible.
One last little thing, I don't use a web development application to generate my pages. For one thing, they have waaay more horsepower than I'll ever need, given that they're geared for gadget and plug-in happy people. For another, most of them generate garbage HTML. Non-man-readable code makes debugging a page next to impossible. I just use a simple text editor that understands HTML enough to color-code the tags. That's all I'll ever need.
It's ironic that a common complaint in the early days of the Internet was that most of it was worthless; yet, as developers pile on the plug-ins, add-ons and other gizmos in an effort to "improve the user experience" (buzzwords like that make me wretch), the percentage of worthlessness is instead increasing. I often wonder why I bother to publish anything online. Ever the optimist, I suppose.
Are you still with me? Then you're my target audience. Are you nodding in agreement? Good. Shaking your head? Well, thank you for hanging in there all the same. Sorry, but we'll just have to agree to disagree. One thing you cannot deny is that you could easily read all of the content. That's my goal.