Joe Brinkman wrote:
It is not accurate to say that the reason for the change was due to a shortcoming of DotNetNuke to handle the Enterprise requirements, since WindowsITPro.com shows that it can certainly handle the requirements. There are many large enterprises, including companies like Mercer that use DotNetNuke as an enterprise platform. Like any technology, a large part of using it in the Enterprise is the staffing mix that exists in the organization. If you have an organization that has a large PHP team, it will be a challenge to transition them to .Net. The converse is also true. Where most enterprise implementations of any technology fail is in the organizational changes that are often required.
It is accurate, actually. Additionally, Penton did not have a large PHP team and the development of windowsitpro.com not only involved Penton's resident .NET experts, but also a large degree of involvement from R2I. There was no skill-transition taking place for the development of windowsITPro. It still took over a year to get that site out the door and parts of it are already being re-worked. Essentially, it is the same site that it was - just a change of platform - and it took over a year to get there.
Joe Brinkman wrote:
To add a bit of balance to the discussion of Penton, it is important to understand why the initial switch was made from Drupal to DotNetNuke - because the Penton .Net team was delivering sites faster than the Penton Drupal team. There are many reasons that go into that, beyond just the core technology, and I would be happy to discuss them in another thread rather than hijacking this one.
Not true. The decision to adopt DNN at Penton was made before even a single Penton property had launched on DNN. It was suggested that DNN would be faster, which factored into the decision, but hindsight is 20/20. businessfinance.com,machinedesign.com,systeminetwork.com,atwonline.com,forums.registeredrep.com....all went out faster than any of the comparable DNN projects.
I'm not sure where you or Scott are getting your information about the internal workings of Penton, but you would be hard-pressed to find anyone at Penton, with the exception of those working in the Windows group, that think that the strategy to move from Drupal to DNN was sound. Fortunately, that's been corrected. It would probably be best to not cite Penton as a case-study for DNN.