In the past I have had many clients bring up the question of "Why should we put our highly functional site in Sitecore?" As in the content of the site involves forms, developed conditional logic, and third part tools and services to make up the majority of what is displayed. At face value Sitecore is a CMS with a lot of use for a site that is heavy content. However the tools that Sitecore provides can still be of great value for a functional site.
Last August my company landed a new project to refurbish some Payday lending websites. As part of that project it was my task to find a .Net and MVC compatible CMS to move some legacy VB.Net websites to a new CMS based platform.
Recently, I teamed up with a group of front end developers on a project to launch a fully responsive web site. Things were going smoothly until the content entry portion of the project started. I started to get ticket after ticket in my queue...
Let me preface this blog by saying I have done a fair amount of both administering and developing for SharePoint 2007 / 2010 and Sitecore versions 6.x – 7. In my experience, I have found that some IT professionals have a love affair with SharePoint. For this reason, they see SharePoint as something that can be bigger than a simple intranet. This brings me to a common question I have been asked, “Should I use SharePoint as a CMS for my public facing website?”