A CONTENT MANAGEMENT SYSTEM IS NOT A FILE CABINET

Content Management Systems (CMS) have revolutionized content creation and website maintenance for every business that has chosen them. They allow businesses to update content in house, responding to immediate communication needs in a way not possible with a site managed solely by your agency. And with this increased level of hands-on commitment, businesses become more engaged in site design and structure discussions. Expect this partnership between businesses and agencies to only strengthen as technologies and skill sets evolve, to the benefit of overall communication goals.

CMSs aren’t office furniture. They’re not even like an operating system or application. A CMS updates constantly, whether it’s the core software, the particular theme which skins your site, or a plugin that delivers extended functionality. In the past, you would have thought to wait for the major version upgrades – the 1.0 to 2.0 to 3.0 transitions – but the world of web development is built on continuous improvement. That is the true revolution of digital media, and with the collaboration CMSs foster, that reality is now part of a business’ understanding.

Primal Tribe currently develops sites in two robust and mature content management systems: DotNetNuke (DNN) and WordPress (WP). If we told you one is built on Microsoft’s ASP.NET framework and the other on Unix and PHP, would it matter to you? Probably not. We’re past thinking about one system as superior to another, and we know all you’re concerned about is a site that works, communicates your messages professionally, and is straightforward to update. Your business goals and needs come first, not the technology.

The idea of continuous improvement in CMSs is not to be on the leading edge of features, but to ensure stability in operation while minimizing security vulnerabilities. A CMS is a complex package of software modules working together as a single site. Browsers change. Operating systems update. New devices are being brought to market every day. CMS developers respond with updates that patch functions which may break with system updates and they take advantage of new features to improve their software. What they don’t do is make it a priority to patch old versions of a CMS. Their path is forward, not to maintain where they were a year ago.

It’s that commitment to the future you can benefit from with a plan for regular updates with your CMS. More than anything else, incremental upgrades are easier to learn and integrate into your workflow than a major update years down the road. Regular upgrades are far less stressful on staff who need to adapt quickly and move on with duties which include much more than your web site.

Behind the scenes, you can be assured the latest security measures have been implemented in response to emerging threats. It means a constant effort delivers peace of mind and few surprises, and all of sudden, your web site never becomes an issue. Who doesn’t want that?

   

Recent Posts