In the previous article in this series I introduced the first reason for why I chose to use WordPress as the engine for three CMS-like sites that I designed recently. I wrote about the theming/template system in WordPress - the “looks”. In this article I’m going to talk about the “guts” of Wordpress.

Why I chose Wordpress

2. The Guts

When I refer to guts, I mean the following things that are “inside” the WordPress engine:

i. File Structure

From the perspective of a newbie developer, the WordPress file structure greatly aids in comprehending where things are and what files need to be edited/looked at in the development process. The fact that directory trees and file names are descriptive of their function cuts down on a lot of the guesswork into where things are located.

Here’s the layout of the directory tree structure:

/wordpress (root): You’ll find all the main configuration and base level files such as config.php (database settings), wp-blog-header.php (calls necessary includes and header information), and various feed related files among others. I’m not going to go into detail about each of the files but I’ll just mention that for the most part, the files in the root wordpress directory are what WordPress accesses when initializing.

Thanks to Thomas Sutton, I became aware of a bug in the plugin that caused the post content for all posts to disappear when the auto-tag toggle for the series-meta was disabled. I’ve updated the .zip file for the download - which you can get quickly here. The only file that needs to be replaced is orgSeries.php.

Or if you are comfortable editing .php files do the following in the orgSeries.php file:

Find,
if($settings['auto_tag_seriesmeta_toggle']) {
$content = wp_seriesmeta_write($postID) . $content;
return $content;
}
which is at about line 375 (to 378)

ADD (at line 379 right before the })
return $content;

That’s it! I really apologize for that bug. It is something I should have noticed earlier. Thanks Thomas for pointing it out!

In the previous article in this series I gave a summary of some of the core differences between a CMS (content management system) and a blogging engine. I talked about some of the cases where one system is more preferable over the other when designing websites. In the conclusion to the article I mentioned that in light of what I had just written, it would have made more sense for me to go with a CMS for the website designs of Hanover Pentecostal Church, UnashamedSermons.com, and VigliottiWoodworking. Yet, as can be observed from the title of the series I obviously used WordPress instead. This article will focus on the first reason for why I made that choice.

But before I get to that I’ll give a quick rundown of some of the requirements that needed to be considered for each site.

UnashamedSermons.com
UnashamedSermons.com is where I host all the various sermons I have (and still am!) written and preached while pastoring at my church. There were predominately two purposes for me creating UnashamedSermons. One, I wanted a place where I could archive all my messages and access it for personal reference. Two, I wanted to make available to as many people possible these messages in the hopes more people would be impacted.

I just can’t get away from working on this plugin - I find it too useful for the various websites I write and I keep tweaking it to make it easier for me to write posts that are a part of a series and display the information that I want to display. The problem is, I’m spending so much time on developing this plugin that I have little time to actually write articles !

Anyway, this release of the Organize Series Wordpress Plugin is chock full of great enhancements and minor bug fixes including the following:

• Added a function/tag for counting the number of posts in a series. (tag returns a value). See usage instructions below for manually placing this tag (it is automatically included in the auto-tag insertion for series meta information)
• Added a function for writing series meta information (?This entry is part x of x in the series, ?The name of my series?) to the posts that belong to a series. This is automatically added by default to your blog but it can be disabled for manual insertion via the new option on the options page for the plugin. See usage instructions below for manually placing the series meta tag.

{this is part 2 of the series “Wordpress as a CMS”}

Wordpress is primarily a blogging tool (or engine as I like to call it!) but I’ve learned in the course of designing three websites that are not primarily blogs that Wordpress can also cross over and serve somewhat nicely as a Content Management System (CMS). In the second article of this series I want to talk a little bit about the difference between a CMS and a blog and then in the next article I’ll talk about how this played into my decision to use Wordpress for the design of UnashamedSermons.com, VigliottiWoodworking.com, and gohpc.net.

On the surface it may seem that there isn’t much difference between a CMS and a Blog. They both provide some sort of backend interface for administrators to manage the content of the website. They both invite social interactivity via the ability for visitors to leave comments, register as a user, or even become a contributor to the content. Then of course the primary focus of each is the delivery of some sort of content which in later years has involved not only pictures and text but also videos and audio (podcasts and the like). But surface appearances can be deceiving!