In the days between Christmas and new year I had a job to do. A WordPress site for a family member that I designed quite some time ago wasn’t really doing the trick any more and I had promised to updated it. I decided to use the Flexx theme from iThemes

Before Christmas I had watched a live screencast demonstrating Flexx. I was really impressed with the features. I was lucky enough to be given a free copy and I was close to creating a new blog just so I would have the chance to use it. Luckily (for my schedule at least) a real project came up where I had the chance to use it.

As I was updating an existing site I didn’t want to vary too much from the layout that was there already. With Flexx I was able to choose where to include the main menu in relation to the header, which site the sidebars would be on, even how many sidebars there were, whether to include wigitised areas at the top and bottom of the posts, etc. I was able to do a good job of replicating the layout of the original site very easily.

The next step was updating the header. I used the old image from the site, cropped it a little to size and used the image manager built into Flexx to upload it. Flexx allows for several images to be uploaded and it will fade between them at specified intervals. I didn’t need to use that as I was trying not to move too far from the original design; however, the fact that it is there means I can consider some interesting additions to keep the theme fresh without doing too much work.

Putting the menu together was also pretty easy. I used Mark Jaquith’s Page Links To plugin to create pages linking to categories on the site and then used Flexx’s menu selector to choose which pages I wanted.

If you’ve been reading this site long you will likely know that I am a bit of a code junkie; I tend to like getting stuck in to the code and as a result tend to dismiss things like widgets as a bit of a gimmick; however, in this cases I didn’t need to and I really noticed how easy it can be. The site I was updating used my Fun with Categories plugin to allow posts to be selected based on both Country and type of post (journal entry or photos) and as such had some extra code to output that. I used my Fun with Theme Widgets plugin to convert this to a widget and then attached it to the sidebar.

I am fully aware that I didn’t use the Flexx theme to anything close to its full potential. What I used it for was very simple and could be accomplished with most themes; however, I do think that it would have been more difficult in most cases. Flexx is certainly a very flexible theme. It has a lot more features that I didn’t touch on here and, although I did get a free copy, I would recommend it to anyone.

*Note, the links to Flexx in this post are all affiliate links meaning I get paid if you buy anything. If you do not want to use these you can go direct to http://www.ithemes.com.

One of the cool things about WordPress is all the themes that are available. I am sure that the wealth of themes is one of the key reasons for its success. It is also one of the reasons why many of the themes available for Habari have been ports of WordPress themes such as the Dilectio theme that I ported over. Now though a theme has been ported from Habari.

The Charcoal theme, written by Ali B is the default theme that comes with Habari and has been ported to WordPress by Jo0Lz. He has even included the necessary styles and code for 2.7s threaded comments.

You can download the Charcoal theme from Jo0Lz’s Website.

The hoo hah about themes and GPL and community is still ongoing. I’ve been having a discussion about charging for WordPress themes over at XFEP, but I thought I should explain my point of view. So here it is.

I aim to be very logical and direct in most cases; therefore I will first attempt to consider what I think are the relevant points.

Question one: What is WordPress.org?

WordPress.org refers to:

• the WordPress software;
• the open source WordPress project;
• the community centred around the open source WordPress project; and
• the domain that gives a home to the open source WordPress project.

Question two: What is the open source WordPress project?

The project consists of the management of contributions to the WordPress core code that make up the free (as in money) WordPress software. These contributions are provided by a wide range of individuals who contribute to the project either in their spare time, or as part of their employment with firms that generate an income from WordPress related products or services.

Question three: What is the community centred around the WordPress project?

This is where things start to get tricky, and why this post is titled as it is. This is where people will begin to disagree.

I think we can all agree that: The community is a group of individuals who share an interest in the WordPress project.

I think we can also all agree that: An individual’s interest in the project may be intellectual, personal, professional, or financial.

I have excluded commercial deliberately as I do not believe anyone can have commercial interest in (i.e. own part of) the WordPress project. Note that when I refer to the project I am still referring to WordPress the software, and not the general contributions of the community.

I think it is reasonable to divide the community into two here in order to differentiate between the directly engaged community, that is, the people who blog about WordPress, and contribute to the repositories, and forums, and the wider WordPress community that use it, sell it (such as web designers that base sites on it), or develop based on it. This division is important for my view, but, even though you may disagree with my view, I think this step is reasonable.

So far then I have explained the community, in reference to other parts of the project, in the way shown by this diagram:

For the rest of my discussion about the community I want to exclude the wider community and focus on the directly engaged community (The Community).

Question four: What is The Community?

Here I need to examine what it is that I think any community is. Not just this community, but any community. It is a little theoretical so I hope you will excuse me.

In 1986 McMillan & Chavis put forward a theory of Pshycological Sense of Community. They defined it briefly as:

a feeling that members have of belonging, a feeling that members matter to one another and to the group, and a shared faith that members’ needs will be met through their commitment to be together.

More specifically they attributed community to four central elements:

1. Membership
2. Influence
3. Integration and fulfillment of needs
4. Shared emotional connection

You can read more about the paper and the follow-up here.

So what does this mean?

It means that The Community is, as all communities are, a group of people with similar needs that contribute to the whole in order to benefit from the contributions of others. They give influence over others in proportion to their contributions and likewise expect to have a level of influence that is proportionate to their own contributions. Receiving influence is in some ways compensation for taking less than their contributions.

Within The Community each person expects others to be considerate to them as they are considerate to others; however, this consideration is a matter of faith and so once shaken can result in severe consequences such as significant disillusionment, a feeling that the community no longer supports them, and a desire to retaliate.

The Community is about the balance of give and take. This I think is the crux of the matter.

Question five: What does this have to do with anything?

If you are a member of the community what is it that you value?

Depending on how you view the WordPress community, what you value, and what you view as a contribution will determine whether you think excluding items from a repository for reason X is a good thing or a bad thing. You are likely to feel very strongly about it either way. For example:

Do you agree that: A person that makes a plugin freely available is appropriately compensated by the thousands of other plugins and themes that are available to him for free?

Do you agree that: A person that makes a plugin freely available is appropriately compensated by including a link back to his website on every website that uses the plugin in addition to the thousands of other plugins and themes that are available to him for free?

Do you agree that: A person that makes a plugin freely available is appropriately compensated by including a link back to his website on every website that uses the plugin if he is using that to advertise a paid product or service, in addition to the thousands of other plugins and themes that are available to him for free?

Do you agree that: A person who makes a theme freely available is appropriately compensated by the thousands of plugins and themes that are available to him for free?

Do you agree that: A theme author who makes a theme available is only appropriately compensated by the community by having those individuals that want to use the theme pay for using it, despite the availability of the thousands of free themes and plugins that are available to him?

Do you agree that: A theme author who makes a theme available is only appropriately compensated by the community by having those individuals that want to use the theme pay for using it, and by using the community website as a platform to advertise, despite the availability of the thousands of free themes and plugins that are available to them?

Do you agree that: A theme author who makes a theme available is only appropriately compensated by the community by having those individuals that want to use the theme pay for using it, and by using the community website as a platform to advertise, and by including a link on the website of every person that uses the theme to link back to their own website despite the availability of the thousands of free themes and plugins that are available to them?

Do you agree that: The community receives fair compensation from an individual who releases a theme for free, that puts a link on every page of every website that uses the theme, where that link links back to a website promoting a product or service that the individual will be paid for, despite the availability to that individual of thousands of themes and plugins offered for free by the members of the community?

What I take from this

There are a lot of situations and questions there. They are intended to stir thought, not make a point. My point is simply what I think.

I think premium theme authors, who have put more resource into creating a theme than they can support through spare time alone, deserve to be compensated for that effort above and beyond the content that the community provides, assuming the content provided by the community represents only that spare time, i.e. is of a lesser value than the premium theme author can recoup from the community. They should be able to sell their themes for an appropriate cost to recoup the difference between what the community provides and the extra they have put in. Capitalism will decide how much is fair.

I think that releasing free themes to the community with the intent to advertise, via a link to a website that offers paid services, is reasonable provided the creation of the theme expended sufficient additional resource to equal the value of the advertising provided by the community. Given that this is very complicated and cannot be policed I do not think it should be permitted (from the community repository, but from their own website they can do as they please).

I think that premium theme authors are a valued part of the community and so should be permitted advertising space in order to advertise to the community, but, not as part of any product that is provided through the community, and clearly marked. Theme prices should be lowered accordingly to reflect the value of the advertising that the community is providing.

Summation

These are views I have come to by thinking through the principles. I have excluded any reference to the individual’s involved in the premium theme market, the repository, or any other aspect and I have very explicitly excluded any reference to the GPL as I think it is a sofa sized red herring in the whole debate.

Obviously the answers I have come up with a very theoretical as well and certainly wouldn’t be usable in the real world, but by coming up with these answers I understand better where I stand and why it is that I felt that the decision to remove themes that link back to sites offering paid services was a reasonable one in the first place (assuming that that was the intention).

Last week I heard about the difficulties that themers face in trying to effectively style the new threaded comments. There are a lot of nested lists and div tags, the hcard microformat for the commenter’s details and variable classes to give you a lot of styling options. On the surface they can seem pretty confusing but when you lay them out it is actually quite straightforward. The image below contains a breakdown of the html elements, the IDs and the classes that are applied to the various parts of the default 2.7 comment output.

Where a number is inserted I have used n. For example, comment-n, or depth-n. It is also worth noting that many of classes are variable, that is, even/odd, byuser, bypostauthor, and so on will only be the case if the comment is numbered odd or even, if a user has commented, if the post author has commented. There are a number of other classes like this. It should be clear which ones are which.

In the main image about I haven’t included all the detail of the comment form itself. I have included that in here:

If you have any questions or comments on this on this please let me know.