If you’re like me, you’ve been very concerned about the direction XHTML 2 has been heading. Very recently I’ve thought to myself that I won’t develop a commercial XHTML 2 site this decade. (Look how long it took them to get simple stuff right!) Only time will tell, but Tantek’s XHTML Considered Hopeful brings back that warm fuzzy feeling that promising new technologies give. Yes, it was going in a bad direction. Yes, it’s coming back.

I’ve lurked on www-html for several months now, maybe it’s time (and I finally have the time) to start seriously reading working draft and lend my voice to the process. That’s assuming of course I have anything cogent to say. I think the lesson to be learned here is if you’re concerned with where the spec is heading, let people know. As Tek says, they’re listening.

(My personal favorite new element so far? Gotta be <l>. Lots of possibilities there.)

Today has been a wonderful day feeling with code goodness. I don’t know why, but I really, really, really like playing around with XHTML. I find I enjoy programming in other languages (mostly PHP, but Python and Perl more now than before) most when it deals directly with XHTML. Anyway, I’m working on some really fun stuff and by this afternoon this site should be even more on the bleeding edge than it was before. Stay tuned.

The American Megatrends website is now table free and running on compliant XHTML 1.1 and CSS. Isn’t that a beautiful thing? Glancing through there are some places where the markup could be streamlined or more semantic, but considering there is a sole “webmaster/internet strategist/designer/developer” working on this, I don’t see it as a big issue that a few things slipped by. Plus a launch with full compliance! Also refreshing is the attention paid to accessibility.

It seems logical that a hardware manufacturer would immediately see the benefits of standards-based development, as that is something that has been thankfully prevalent in that sector for years now. I hope that other similar corporations will follow their lead, as anyone searching for obscure drivers on a late night knows how terrible some hardware sites are. Once using only wget (long story) I had to find a Linux driver (tough in and of itself) for an IDE controller. There is very little that could have made that experience better, but a site with easy-to-read code such as AMI has now certainly would have been a relief. Rack another up for MACCAWS.

Tantek and Jeffrey have both written quite nicely about handmade sites and aggregation, respectively. I’d like to address some of Tantek’s points first; since I am writing content management system (by his definition), I found his ideas particularly relevant.

First he lists a number of hand rollers, presumably as examples of the kind of “pushing the envelope” that he posits is easier without the burden of a content management system (even one that is designed specifically for the purpose of blogging). Let’s take a look at the list:

• Jeffrey Zeldman — The epitome of doing it by hand. He has a URL scheme that doesn’t change, a novel multi-level permalink system, and damn fine structure. No complaints here.
• Derek Powazek — Derek’s site, at least in its current iteration, is powered by Movable Type. Disqualified. 😉 {Fray} would have been a much better example, but even that is moving to a database-driven backend. (The Storyblog there is also MT powered.)
• Eric Meyer — Again, no complaints. In a perfect world he could lose the class on his permalink, style it through contextual selectors, and add rel="bookmark" but that’s a nitpick and I know it. Kudos to Eric.
• Brittney Gilbert — This looks hand done. Update: Tantek was right, a little to harsh here. Sorry! My intention was to say that, looking just at the code, this site does not push the markup and style envelope the way the other sites listed do. Does that make it bad? No. Read on.
• Simon Jessey — Nice. Added to bookmarks.
• David Baron — Not a whole lot going on here, looks like there are only a few posts per month. It seems very Tantek-influenced and well done, but with the frequency of his updates, I doubt that making his pages by hand is that much of a burden. Which brings us to my next point…

For the moment let’s look at hand-coding specifically in the realm of blogging, in its most general sense. In my view, for something to be a blog it really only needs permalinks and entries arranged in reverse chronological order. Feedback mechanisms– trackback, pingback, plain vanilla comments, a nice way to browse the archives, a search— are nice, but aren’t really required. Blogging (or whatever you’d like to call it) by hand requires discipline, and honestly few outside of the Çeliks and Zeldmans have what it takes to create a document for all time. Things like permalinks and archives are a pain to do manually; I know, I’ve tried.

There are some good reasons for doing a blog by hand, but I don’t think Tantek explicitly states the most important one. Lack of support from your host is not a good reason; there are too many options out there, from free and up. Along that same vein, cost should not be a barrier, as some of the very best systems out there are free (as in beer). Difficulty setting up shouldn’t be a problem either, as there are a number of people (including myself) who are familiar with a number of blogging systems and wouldn’t mind you setting up any one of them. Tantek comes closest when he likens what he does to a craft, implying that hand-coding his website is not merely a means but an end. Whatever you do should put as little as possible between yourself and whatever it is you love about creating your little corner of the independent web. This above all other things is the driving force behind WordPress, where my chief inspiration is myself, a lazy philosophy major. Tantek is happy writing the code for his page, just as I get a buzz typing in a box and having everything else happen automagically.

The question then becomes what makes Tantek happy about coding his site, not suppositions about the relative merits of hand coding something that could be easily automated. So what makes Tantek happy? I don’t know, but I can relate a story that might shed some light on it. At SxSW I had the pleasure of spending some time with Tantek and I got to see him update his site several times. (Watching people blog is fascinating in and of itself, because I’m convinced that everyone does it just a little differently.) Anyway when he met someone new Tantek would whip out his Powerbook and add that person to a list of people he had met so far at the conference. It was surprisingly fast, he could do it offline, and overall I got the feeling I was peeking behind the curtain of his web presence and seeing a well-oiled machine at work, the happy cogs of OS 9, his editor (BBEdit?), a Wifi card, and a simple FTP program all spinning away in what could only be described as a highly evolved process. It rocked my world; a process so radically different from my own, yet if we had raced, it would have been close.

I’m sure Zeldman is the same way. I’m sure of very few things in life, but I know that he wouldn’t still be doing what he’s doing if he didn’t enjoy it. So I guess in some sense, I’m a blogging hedonist. Do what makes you happy.

Just to clarify, I’m referring to coding by hand specifically for blogging, which I think is a tad daft, and not general hand-coding web pages, which I practice because there is no tool out there to my liking. If there were a perfect tool I still might not use it, but I’d definitely give it a try. However, in any hand-coding situation, you still shouldn’t make things any harder on yourself than need be. Noel Jackson uses Texturize with PHP’s output buffer to add typographic niceties on the fly to pages he hand codes. I’ve started doing this myself and it saves a tremendous amount of time, and it’s terribly simple to use. With two lines of PHP I was able to update a 450-page site, something that would have taken hours to do manually. (Not to mention us poor PC folk don’t have access to Dean Allen’s scrumptious Preflight Cruncher.) I’ve written similar tools for acronyms, line breaks, and pretty much any other mundane task that can be easily codified.

Moving on…

I agree wholeheartedly with Jeffrey on the potential for aggregation to steal the soul of a site. Recently on my syndication page I included a quote:

Q: If you offered an RSS feed, I could read your stuff without visiting your site.

A: If you stored your groceries on the sidewalk, we could eat your food without sitting across the table from you.

That’s classic Zeldman, complete with the famous Playboy-inspired editorial “we” that we so dearly wish we could pull off too. That was then, and he’s obviously trying to be more diplomatic this time around, yet the thrust is the same. I have debated removing my feeds several times, but ultimately my ego won out. There are several people who simply wouldn’t read this site if it wasn’t available in a syndicated format, and my desire for readership—to be able to look at my stats and know I’m not speaking into a void—is greater than whatever it is inside me that wants my writing to be appreciated in the context of my site. Christine says she comments more since she started using an aggregator. Besides, I try to remind my RSS readers several times a week that they’re missing out on something. It’s “Nice. But not the same.” I haven’t seen any unbiased studies that compare the effects of RSS on readership and such, and on a personal level it’s hard because RSS stats tend to be inflated due to the automated nature of their updating.

I think a laissez-faire attitude will eventually prevail. I can primp and preen my design all I want, but when it comes down to the basics all my code is merely a suggestion, and the interpretation of that is at the whim of whatever user-agent is knocking at the door. I question whether or not RSS is the best format for this sort of thing, but it seems to be quite good at what it does. RSS boils away the fluff and leaves just the meat, but what sort of meal is that?

For the project I mentioned in my last post I’ve also been using a fantastic class called ezSQL that really makes a lot of things an absolute piece of cake. I don’t remember exactly how I came across this class, perhaps via Simon, but at the time I wasn’t doing anything I could use it for and so I just bookmarked it and made a mental note to check it out later. After not much more than a night of using it the syntax is already very intuitive to me and I look at the documentation hardly at all; the class itself is so logically done that a quick glance at the code is just as helpful as the documentation. Of course there is some room for improvement, for example it would be nice if the errors and such were valid XHTML, but I’ll survive.