by Darren Ethier (@nerrad)
This series takes a look at the process I went through in adapting Wordpress for use as a Content Management system in the development of various websites I’ve worked on.
Here’s the promised first post in a series of articles I am going to write over the next month about the challenges and benefits of using WordPress as a content-management system (CMS). Now I know that this topic has been covered fairly well already on the blogosphere – I’m not so naive as to think […]
{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 […]
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 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 […]
