When Is A Content Management System Needed?
Wait, what’s a Content Management System (CMS)? Well, according to Wikipedia, it’s a computer application used to create, edit, manage, and publish content in a consistently organized fashion. We, for example, use ExpressionEngine as our CMS of choice. And no, I’m not going to get into why it’s so awesome right now. Go check it out for yourself.
So back to the point; when is it time to use a CMS? We’ve worked on several small websites lately and our customers decided they didn’t want the upfront cost of integrating the site into a CMS. But the more we make changes to these static sites we’ve built, the more of a pain it becomes. They decide to change “Services we offer” to “What we do” throughout the site and all of a sudden you’ve got a bunch of manual editing to do! Sometimes a search and replace function in your HTML editor will help, but not always.
Now, we have looked into creating a simple CMS of sorts with PHP HTML Templates, but just haven’t gotten around to actually implementing it in our workflow. Honestly, it looks like a bit of work to get up and running. We definitely ain’t programmers!
Either way, editing static sites is no fun and I think we’re slowly moving towards requiring a CMS of some sort. It’ll just be part of the package, so to speak. We just end up spending too much time making small updates like this that should be easier.
So how about you guys? What do you think? What do you use? Found anything better than the examples I’ve listed? Think I’m crazy? Let me know in the comments.
P.S. – If you want to learn how to create a more profitable web shop check out Freakishly Profitable. It's the best way to make a "monster" adjustment to your web studio's bottom line.