Monday 16 March 2009

Why a CMS?

Just about every professional website is built on top of a Content Management System. Certainly when we go to see prospective customers it is their expectation that they will have full control over the content of their websites once it has been delivered. In reality only a fraction of them actually update their content, but they do expect to be able to do it!

For six years now we've been building websites on our own content management system Wirenet. Wirenet is built using classic ASP and uses a Microsoft SQL Server database. It's done us proud and has delivered billions of web pages since its launch with the Linder Myers website back in 2002.

However, all good things must come to an end and Wirenet is no exception. In the last couple of years we've been seeing a significant increase our clients' expectations of the web. Many want advanced functionality and more and more are moving to ecommerce. We found that building this functionality was a lot easier with a more up to date platform, ASP.NET. However, making the two technologies, Wirenet and .NET work together was a bit yukky (technical term that!).

So our plan was to rewrite Wirenet with ASP.NET. The problem was finding the time! After a year of not doing it we decided to have a look for other web platforms we could use instead. We had a go with many CMSs but narrowed down our shortlist to DotNetNuke and Kentico.

More details on how we chose Kentico next time

No comments:

Post a Comment

About Me

My photo
I'm most often described as a Grumpy Old Bugger.

Followers