Content management systems, meh.
Anytime I take on a project that involves the possibility of using a CMS, I feel conflicted. In my experience as a web developer, I have typically found that any CMS I provide my clients with never quite meets their needs. Most find the administrative interfaces confusing and end up asking me to just make the updates or add content. From a technical perspective, a CMS also means a lot more code to maintain. Yuck.
Looking back at the content management systems I’ve worked with, one stands out: it’s one I developed from scratch that specifically targeted what the client needed: uploading PDFs of meeting minutes, adding phone numbers to a directory, updating content on specific pages, etc. It seems that the more generic and flexible a CMS, the harder it is for the average user to grasp. I’ve actually found that teaching a semi-technical client some basic HTML so that he could add news items to his site was better than integrating an entire CMS. He even thought it was fun! Non of my clients using WordPress found the administrative interface to be “fun”. Obviously, asking non-technical users to hand-edit HTML is not an option. However, it is an option for the ones who are capable.
If an average CMS user wants to add a new page to their site they won’t typically consider it from the perspective that a web developer would (which is from a site visitor’s perspective). Even when it comes to simply adding content, most CMS user’s don’t properly use headings where headings should be used or lists where lists should be used. In my opinion, you’re better off letting a web developer make the updates. It will be done properly the first time around, rather than paying them to come in and fix things when they’re broken.
How Do I Choose Whether or Not to Use a CMS?
- Is the client semi-technical? If yes, then give them a mini-training session on HTML and a quick crash course on semantic markup.
- If the client is not semi-technical then consider using a framework and developing only the specific updating abilities the client needs.
- Is the client insisting on a CMS even after you’ve explained the benefits of not having one? Then looks like you’re going with a CMS! Choose wisely.