Content Management & ASP.NET

If I had it my way, Ektron would still be an option. Unfortunately, Ektron was dropped from the list by the committee because it didn't have a "Trash" feature. This is the feature that allows you to recover material that was initially removed. This was a requirement in the selection process. As a result, Ektron was dropped.

We share this CMS project with at least 4 other "sister" colleges. None of them build their Web site on a .NET foundation. We do.

What I really want to know from this group if there are any risks involved with working with a CMS that is not already .NET supportive or .NET based on a Web site that is based firmly on ASP.NET 2.0. Can anyone answer that for me?

On 14:24:57 18 April 2008 MartinusF wrote:

 

My advice don’t ignore Ektron. We searched and searched before we landed on Ektron, a much better and faster solution. Totally integrated with .NET and it has all the functionality you need.

 

You can implement yourselves, but it’s more efficient to use somebody who has done it before. We used Konnect Soft who do this sort of back end work. They did the “heavy lifting” for us migrating our site to Ektron and delivering back the .NET project within 4 weeks, which we then took over.

 

On 18:57:40 11 April 2008 RT wrote:

 

Hello everyone.

I am the campus Web master at St. Philip’s College and we have completed a redesign of our Web site as recently as last year. We are in the first phase of further improving our Web site from the ground up. It has become necessary for us to look at potential content management systems for easy updating for our 70+ Web authors, workflow and other benefits. Our Web site is based strongly on ASP.NET using Master pages, content pages and user controls.

I started off my research looking for CMS options that are based on ASP.NET. Almost every one of my selections (Ektron CMS400, Sitefinity, etc.) were cut out by the selection process. I don’t care what we select since I trust my teammates. What I am concerned about is if it matters what we choose in order to ensure .NET support.

If there are any other .NET Web developers and masters out there, should I be worried about this? Would I be able to still make use of my ASP.NET setup even if we don’t select a CMS that is based on .NET technology? I certainly don’t want to be "stuck out" if we select a tool that will not be of benefit to the foundation of our Web site scheme.