{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!