Adopting a .NET CMS vs. Open Source?
So you find yourself shopping for a Content Management System. With the variety of homogenous CMS platforms in the market today, it makes it hard to disseminate which solution is the best for you?
Do I go with the “red pill or the blue pill”? Unfortunately it’s not that simple. A suggestion my friend made was “why didn’t Morpheus just take both pills?” It was an interesting argument instigated over several beers, but it did bring up a good question, why do you have to make a choice? Why choose .NET or open source?
My experience prior to working at Percussion, had me directly using a proprietary .NET CMS daily. Although it had its subtle nuances, it was the “devil I knew” so to speak. If any developments needed to be made, it was outsourced it to a .NET developer. If I needed to create a form or add a fancy image slider, a call to a third party was made and money was spent. It seemed like a backwards process since the organization previously had functional PHP code on the site.
It goes back to my original question, why did we have to choose? At the time there weren’t any suitable alternatives. The money spent redeveloping our existing functionality was a significant cost, and took several months to have the same website running through the new .NET CMS platform with the same functionality.
The new trend that is starting to make waves in the CMS community is the de-coupled approach. It takes the role of Switzerland when it comes to existing code on the site. If your flavor of development is .NET, PHP, Ruby on Rails, etc, they all can work within a CMS like Percussion. It provides usability and functionality with a twist of lime.
Percussion’s de-coupled architecture is unique from a traditional sense. It sits behind your firewall, and publishes HTML content to the web server. It gives the developer/engineer the ability to embed code within an “HTML Widget” and provides an easy solution to manage/share code between assets and pages, without the content author/subject matter expert being exposed and threatened by code.
Yes, I do work for Percussion, but my stance towards any new technology has always leaned on the side of pessimism. Learning about this new approach helped me understand that a CMS solution needs the ability to be agile, and allow a user/developer to get create great content/code with limited obstacles. This increases content consumption by viewers, and also saves money from less development time from custom functionality.
Don’t take my word for it, take and take it for a test drive. Feel free to contact me or one a member of our team, and setup a free cloud hosted trial, and see if this solution would be a good fit for your organization.
Chris Burns studies computer science part time as a graduate student at Boston University. In his downtime he enjoys casually nerding out on his Arduino/Raspberry Pi. His philanthropic efforts entail handling any/all computer/technical support for his family/friends. At Percussion, he loves to show new customers the possibilities of working with our CMS. Chris is also a dedicated humanitarian and lived abroad for one year in South Korea while teaching English as a second language.