Posts Tagged ‘cms’

Interesting Church Tech Links for May 17, 2009

May 17, 2009

Some more WordPress links today:

101 Techniques for a Powerful CMS using WordPress
A whole lot of interesting ways to make WordPress work more like a CMS. Some I’ve used, some I’ve not.
Broken Link Checker for WordPress
Been using this and it finally forced me to fix a few already known but broken image links
Analyze WordPress Performance – Plugin!
This plugin generates some interesting stats about the queries for generating a page. Not sure exactly what I’m going to do with the information right now but I’m glad to have another tool for when I will need it.
Change Admin Pagination on Posts, Pages and Comments
WordPress 2.8 looks like its going to have some nice upgrades, but for those who cannot wait, here’s some code to let you alter the number of comments, posts or pages listed in the admin module.

Other thoughts on WordPress as a CMS

January 6, 2009

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 Grahl points out some real problems that people using WordPress as a CMS need to consider. His first two issues didn’t seem too relevant to me.  Since I build custom templates for my WordPress installs I feel free to rip out anything I don’t want.  But then I considered that not everyone is probably digging deep into the WordPress themes system and might want a simplier way of controlling these elements.

I don’t personally use these plugins but maybe you’ll find them useful.  Thanks Tim.

WordPress as a CMS

January 2, 2009

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 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).