Tag Archives: themes

Magazine-format blog: points to ponder

The “magazine” format has taken blogs by storm this year, and if you’re of the mind to move your blog in that direction, there are a few things to consider.

First, ask yourself: what is a magazine? As a collection of features covering different topics, one can argue that most blogs fall under the term, but online and print magazines share predictable, consistent sections which different readers can flock to. Consider Newsweek’s last-page editorial. Last time I checked, Anna Quindlen has as regular gig on that page. When I have a chance to peruse a printed Newsweek at the local CVS, I go straight to that page. Other readers go straight to other section. A magazine is a consistent, regular publication with content that is expected by the audience. If you’re a free-form blogger who can’t deliver that kind of content consistently and frequently, the magazine format will leave entire swathes of your site with poorly updated material.

Continue reading Magazine-format blog: points to ponder

The costs of Free

Recently, Michael Torbert, developer of the popular All-In-One SEO Pack (AIOSEOP) plugin, released a major upgrade to, among various other bugfixes and feature enhancements, future-proof the plugin against scaling issues. I worked with him on beta-testing the upgrade, and found it to be flawless. I was one of many, but gauging by the reaction of a few, there were not enough of us who did the testing.

Continue reading The costs of Free

A retrospective of WordPress Classic

In God Emperor Of Dune, Leto II Atreides ruled for almost four thousand years as tyrant of humanity. In doing so, he created a desire for people to be free, and ensured that they will never stagnate and fall victim to the need for a single commodity for existence.

Back in 2002 I started to learn web design from a code-based perspective. The CSS techniques we now consider standard were at the time, groundbreaking. Grey Matter, Blogger, and Movable Type were the frameworks of the day, while I started poking around with a then-little-known program called B2. Fast forward a few months, and a then-little-known guy named Matt Mullenweg decided to fork B2 into a new project, called WordPress.

Continue reading A retrospective of WordPress Classic

What is a theme and what is it not?

I’ve designed WordPress-powered sites and blogs for almost five years now. I have my niche, for which I am grateful. Recently, I came across some huff-and-puff regarding Matt Mullenweg’s decision to remove over 200 themes from the repository, citing non-compliance with the GPL.

I have a feeling I’ve been living under a rock for the better part of three or so years. I’ve watched the WordPress community from the sidelines. I saw its expansion and internecine conflicts. I’ve remained silent on most issues out of being ignorant on so many of them and am not afraid to admit to being so.

However, recent events have raised questions and concerns. Jeff Chandler wrote a thoughtful post on Premium Themes and I am left with a few questions and thoughts of my own.

Allow me to introduce you to my design workflow. Whenever I design for a client my first step is to almost always begin with the WordPress Classic theme’s document structure. Old habits die hard and I have found it to be one of the most efficient ways to start off with a “naked” theme. I strip the CSS file of everything except the theme header, substitute it with a blank template of code of all the elements I use in almost all my designs, and start coloring and shaping. I have never, still do not, and perhaps never will, follow the Photoshop-to-code development workflow. If a client wants something exotic, like a horizontal navigation bar (with tabs!), I have a codebook for that too. Now, I tell my customers that the site I design for them is for use on that project only, or for whatever number of sites we agree upon. The combination of images and CSS code form a look which, I believe, is the intellectual property of either myself or my client (depending on the terms of the contract).

The question, then, is, what part of my design falls under the GPL? Does that mean that any one party can rip off an entire design I make, despite the inevitable embarassment at having me parade their lack of creativity for all to see? It’s so easy for me to reverse-engineer the look and feel of Jeffro 2.0 without looking at source codes for HTML and CSS, but I do not, because it is a professional embarassment to do so. What portion of his, or anyone’s, site can I “liberate?”

What is covered by copyright? I know that blocks of CSS code don’t get that benefit, and for good reason. Faux columns would never have caught on, for example. I don’t think that only the content presented by the blog is covered, though. The look and feel of a site are part of its identity, especially if the design is relatively unique.

What are the limits of the GPL when it comes to Themes, Premium Themes, and Blog Designs? This inquiring mind would like to know.