or, When is your CMS not a CMS?
Computer-orientated terminology tends to get thrown around like buzzwords, it seems. Not only by people who don't really know what they're talking about - but also by those that should. And, like buzzwords, they convey an idea - not a technical specification. If you haven't heard of a CMS or a CDP however, you might be left in the dark.
but Buzzwords are cool - they're easy and indeterminate.
Sure, saying 'CMS' or 'Content Management System' is easier than describing what you mean all the time - but suppose both parties have completely different ideas of what to expect from a 'Content Management System'. After all, what does your 'Content Management System' do? Does it manage your content for you - or help you manage your content? Does it even do that? Is it just a facilitator for creating content? Drawing up lengthy technical specifications may help, but throw a client-who-uses-misunderstood-buzzwords into the mix and you're in for a bumpy ride. Chances are you'll both assume different functionality.
So, imagine you have what's called a 'Content Management System' - what should it do? IMO, the humble Dreamweaver is a great example of a Content Management System. You can manage files and folders to your hearts' content.
By keeping an internal database of linked files and folders, Dreamweaver does the tiresome work for you - updating links and pathnames. Microsoft Office Sharepoint Server (MOSS) is also very good at this - once pages are linked, you can move, rename and edit them safe in the knowledge that the server knows where the files are. That's what I'd call a Content Management System.
Conversely however, a search for a Content Management System on google will turn up hundreds of systems - and yet none will offer this kind of functionality. These are the WordPress kin - systems that facilitate the creation, modification of files, and day-to-day tasks of running websites. Now, if that doesn't sound like management, I don't know what does. But how can these completely different ideas both come under the same terminology umbrella?
In short, I'm not sure.
Broken down into the component parts, terms are usually so ambiguous they need further expansion. That then becomes the point at which you wish you'd never uttered 'CMS', and start trying to come up with a better description. Trouble is, if you use your new, improved, terms - people start giving you blank looks and then the bitter cycle rolls on.
What's the real issue?
Why does CMS bug me so much? Firstly, [MMT Digitals'] primary website delivery software is branded 'Rearview ECMS'. Rearview Enterprise Content Management System. Now, to give credit where credits' due, it's not half bad - you can do all the day-to-day management within the system - but move files, folders or pages around, and kiss your links goodbye - as is the case with so many other similar systems.
Perhaps these systems should be called 'Content Delivery Platforms' or 'Content Creation Systems' - that is, after all, what they do. You still have to go and fix links yourself. Or maybe they do deserve their titles, and it's the others' that need changing. Something like 'Server Management Software' - no wait, that anagrams' already taken. How about 'Resource Interface System'?
Actually, that's not so much the issue as is: What if someone expects you to work with the wrong sort of Content Management System? You can sell the idea of a CMS to your client, but then your client could go around and buy Microsoft SharePoint Server and expect you to develop a normal website in it.