There are a lot of topics in the web development world that come around every so often like clockwork. Usually it’s a “how do I do this?” question from another newbie for the umpteenth time on a list you’ve been a member of for five or six years. Sometimes, it’s a higher-level discussion about “where is the web going?” I suspect the newest discussion that will ebb and flow will be about the “Web 2.0.”
Then there are the meta-discussions that contain dozens of smaller discussions that also go around and around. The separation of style and content would be a meta-discussion. Originally it was just a regular discussion, but then it actually start happening and it spawned (or maybe it was spawned by) discussions about the semantic web. One of the conversations that further fractured from that regarded a standardized nomenclature for styles.
That is something I’ve thought about for a while for my own personal use. As a designer, I could create my own templating system akin to what they do over at CSS Zen Garden. I’ve even thought about using the Zen Garden HTML template and seeing how well I could adapt it to my customers’ websites. Taking it a step further, I thought about using the Zen Garden HTML template to develop WordPress themes and seeing how well I could adapt those to my customers’ websites. Sounds crazy doesn’t it? It might be.
It’s entirely possible that, in many instances, such applications wouldn’t be the best solution for a client. In those instances, the solution would have to be abandoned in favor of a better one. But, in other instances, it might work out great. For that group, a common set of solutions would exist which would improve my workflow and turnaround time. As an independant web developer that would improve my bottom line.
More altruistically though, it would also allow me to apply that common set of solutions to give back to the community by creating templates. I know that doesn’t sound like much, but hear me out. Each template could be put up on CSS Zen Garden as an example of what is possible and at the same time could be used as an actual WordPress Theme. People use blogging tools like WordPress because it lowers the barrier to entry: they can self-publish on the web without having to learn how to write XHTML, CSS, and PHP code. They don’t have to create their own .htaccess files to make their URLs more human (and machine) readable. In as little as five minutes they can be up-and-running with a robust content publishing/management system and all they have to do is put their content out there for the world to read.
You might think this is a bad idea since, let’s face it, most content will be utter schlock, but that’s ok. You don’t have to read it. Blogs are the harbinger of the Web 2.0. The web as a two-way medium. I post something that, like this very post, is only read by a handful of people, half of whom probably know me in “real life.” But they can comment on my post and I can comment on their comments. It’s the web as a two-way communications medium, not just me pushing content out there and you can like it or shut up–or both.
Putting out templates that could be used by people to help them communicate their message to a wider audience, when they might not otherwise have been able to communicate their message at all, is a great thing. Besides, as a designer, it’s the best contribution I can make to the blogging community. As a WordPress user, I feel a certain obligation to give back for what I’ve gotten.
