This is a post I’ve been meaning to make for a long time. However, an informal presentation of the awesome Doodlekit last night at KCRUG and a site Scotty showed me yesterday reminded of the quagmire we’re in.
The Problem
If you need to build a website for yourself or for a company, often the default answer is “You need a Content Management System (CMS)!” The problem with this assumption is multi-fold:
- Do we really know what it means to have a CMS?
- Do we know how our content will be structured?
- Do we know our audience and their needs?
- Do we have a preferred way of working? (a.k.a “workflow”)
- Are we managing web pages or something else entirely?
To tackle this problem, we first need to define what we mean by Content Management System, and then break it up into its varieties.
