[wp-hackers] WordPress as CMS (was: wordpress security)

mark waterous mark at watero.us
Thu Oct 22 04:57:17 UTC 2009

> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of William Canino
> Sent: Wednesday, October 21, 2009 3:50 PM
> Subject: Re: [wp-hackers] WordPress as CMS (was: wordpress security)
> I think using WordPress 2.8.4 as a CMS is like using a coffeemaker to
> boil vegetables.  Office pantries probably don't have a stove or
> cookware, but they all have a coffeemaker. And everyone knows how to
> use a coffeemaker, right?  Yes, WordPress 2.8.4 as a CMS is a
> MacGyverism.

Personally, I like Ozh's take on this;

Your analogy does make sense, but it's a little broader than that, isn't it?
When you say 'Coffee', everybody knows that you mean that black substance
(of varying thickness) that helps some people stay up late and get work
done, and others maintain a constant state of vibration. When you say 'CMS',
or Content Management System, you can't pigeon hole the coffee pot that
makes your content. Wordpress IS a CMS. It manages content. Plain and
simple. It may not offer the same features as some other CMS' do, but that
doesn't mean it's not a kitchen utensil, just like Drupal or Joomla. It's
just a different kitchen utensil.

As I alluded to (maybe I didn't?) in my earlier post to the thread, I agree
with everybody saying that changing the naming conventions currently being
used is more important than stripping available functionality. I couldn't in
my wildest dreams envision the desire to remove my Posts ability.

More information about the wp-hackers mailing list