Week 2 – Pro’s and Con’s of CMS

Some major pros to using a Content Management System can really depend on who will be using it and why. For instance, if you are just a blogger looking for a platform to share your stories or diary entries, you can use an open source CMS like WordPress or Joomla at little to no cost. However, if you are a business owner or a marketer then you are better off with a licensed CMS such as BluePost.com. Either way, there are pros and cons when working with a content management system in general.

Pro number one, most of them are free and available to anyone and can be really easy to use. Thanks to the technical revolution, tutorials and information are widely available for guidance and community support. Pro number two would have to be the fact that the author has control and responsibility of their own domain and platform. According to the article WordPress.com Vs WordPress.org, What’s the Difference? “Self-hosting platforms are more author centric and more robust.” They can personally host whatever content they want and have control of their visual layout whenever they want. If you can write code, even better though some free open source hosts only allow accessible code features for a fee. The biggest pro is you have the potential to create a unique and presentable website using any computer and of course, the right password.

On another note, when dealing with the pros of something there are always cons. Con number one, when creating a website with any CMS, there is almost always a cost for your domain. Usually less than $5 bucks a month, yet you are not protected from hackers or viruses. This can leave a lot of those new to building websites in a vulnerable position. You would have to fix problems on your own, unless you upgrade for more features at a price. Con number two, especially with a licensed CMS, you can end up with a website that lacks portability on certain web platforms. This makes your site a little harder to communicate your product or blog effectively. This also means you have to depend on your developer to make certain changes on your site without having access to making the changes yourself. One last pro is that you can never truly depend on technology for the longevity of your project or product. In the article It’s About the Developer, Not the CMS, Christopher Butler clearly states “The mundane reality, of course, is that the lifecycle of the average active website is 3-5 years, often continually adapted to the changing technology of the ecosystem of the Web. If you want to take a long-view at the beginning and make decisions accordingly, you’re better off making a choice of relationship- aligning with a person or firm that will bring wisdom and stability to that changing environment- not one of technology.”