WordPress as a CMS


After years of maintaining web sites directly in HTML I made the leap to using WordPress as a CMS this past fall.   I had previously been using a SSI templating technique I developed and used successfully for many years in my professional duties. While its principally a blogging platform, I’ve been very happy with its ability to adapt to my rather exacting demands (the 190% software control freak that I am).  Even with my general dislike of PHP as a programming language I must admit to the excellence of the overall API and its flexibility to incorporate (and be incorporated into) other areas.

I’ve not yet written a plugin for WordPress but that I’ve not needed to is impressive to me.  I’ve not needed to because of the quality and diversity of the existing plugins as well as the simplicity of the templating system.  Its very easy to create and deploy a theme and I’ve easily wrapped my custom web forms in the active theme.  Actually, using WordPress.com is going to be an interesting experiment for me in not having complete control over the theme and configuration of WordPress.

I know many people are working with Drupal instead.  I have one friend say that he preferred Drupal because he couldn’t make WordPress do what he wanted.  I never followed up to understand what limits he ran into, but I’ve not found any.  As a church web master, what do you do for your content management and what limitations are there to your choices?

For me, using hand-coded HTML essentially required anyone else who might help me to be excellent with HTML and be able to deal with an FTP client.  Since there are only a few in my church that could handle it and they are involved in other ministries it then falls to me to handle every content update for the site.  This was fine when it was a small site.  But these days I’m trying to expand the volume of content and I’m not always in the right place at the right time to make some kinds of updates.  A system like this can let me delegate some of the content maintenance responsibilities without requiring coding skills… and I didn’t have to write the CMS myself (which I thought I was going to have to do).


Tags: ,

4 Responses to “WordPress as a CMS”

  1. WordPress as a CMS | PHP-Blog.com Says:

    […] the original post: WordPress as a CMS Related ArticlesBookmarksTags Using PHP and MySQL to Develop a Simple CMS – Version 1 In […]

  2. Other thoughts on WordPress as a CMS « Web Ministry Thoughts Says:

    […] thoughts on WordPress as a CMS By Daniel Pedersen As a follow-up to my previous post WordPress as a CMS I ran across “WordPress as CMS: Plugins that will get you there” from Out:think.  Tim […]

  3. eksith Says:

    It’s actually “Drupal”, not “Druple”

  4. Dan Pedesen Says:

    Yes, you are correct. Thank you.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: