Although I retired last year from writing stories solely focused on content management systems, I still have a few of my favorites that I like to keep an eye on. One of those favorites is DNN which back in the day we once called DotNetNuke. Less than a year ago, DNN brought to market Evoq 8 which addressed modern day marketing needs for better customer engagement. Last week, DNN showed the industry the ongoing evolution of its product line through Evoq 9. The new release continue's DNN's journey to be more than CMS company as it reaches beyond websites to apps, devices, and other Internet of Things.
The first time I heard the mention of customer experience management was at CMS Expo 2012. In one of the sessions, Robert Rose spent much of his time at the Expo warning the audience that content management systems need to do more than just content management. Rose believed experience management needed to be given a higher priority over web content management. Yesterday, DNN announced with Evoq 8 they are now ready to "move beyond web content management" and enable "marketers to publish, personalize, and measure content anywhere online". The improvements in Evoq 8 are focused on today's marketing needs for better customer engagement.
So I'm halfway through my three month sabbatical from blogging and I get an email from my good friend, Shaun Walker. For those that don't know Shaun, he's the CTO and co-founder for DNN Corp. You know, the guy that started DotNetNuke. To make a long story short, Shaun wanted to remind me that the DNN community recently released 7.3 which focuses on platform performance. Shaun thought it would be a good idea to mention the release to readers here at CMS Report. Given that this was the man that identified wayback that the future of content management systems was in cloud, mobile and social media...it is difficult for me to ignore such requests.
Over the years, we all have abbreviated DotNetNuke as DNN as we've discussed this open source .Net based content management system. It looks like the corporate folks upstairs have finally made this interchangeability official. DotNetNuke Corp will now be known as DNN.
The Company Name Change
A big part of the reason for this change, according to CEO Navin Nagiah is that the name “DotNetNuke” presents us as a company that provides solutions only to customers inside of the Microsoft ecosystem. "We have found that, as our software has become richer in user experience and functionality, we have had customers outside of the Microsoft ecosystem using our software. We expect this to further accelerate with the launch of our product lines on the cloud, allowing real-time deployment of our software, and making the stack on which we are built immaterial to the user".
DotNetNuke (DNN) has announced a social software solution aimed at optimizing customer engagement and loyalty through online communities. DNN Social gives businesses the ability to easily create and manage communities on their existing websites, giving end-users a one-stop destination for consuming content, exchanging ideas and interacting with other community members.
Newly Released DotNetNuke 7.0 Helps Organizations Save Time, Reduce Costs and Develop Advanced Web Applications
DotNetNuke Corp. (DNN), the company behind the most widely adopted Web Content Management Platform for Microsoft .NET, today announced general availability of its highly anticipated DNN 7.0 release. DNN 7.0 intends to make creating and managing content-rich websites, social intranets and online communities easier than ever, with benefits for enterprises, web content editors, developers and web designers alike.
DNN 7 has been planned and under development for some time and has become a highly anticipated release for DNN users. Last summer, CMS Report and DNN's CTO, Shaun Walker, discussed some of the expected "social CMS for business" improvements that were expected to go into this release. We were also fortunate to see a demo and presentation of DNN 7.0 earlier this month.
During the past couple years, I've had the opportunity to get to know DotNetNuke and their open source community much better than I had ever expected. Shaun Walker, a founder and CTO of DotNetNuke Corp., is also a visionary leader and over the past few years I've come to know and respect the man quite a bit. When you get to know DotNetNuke better, there should be no surprise in also knowing that DotNetNuke has become one of the most widely adopted Web Content Management Platform for Microsoft .NET. During the past couple years, Shaun has been whispering to me that I needed to watch DotNetNuke's progress in two significant areas: social publishing and the Cloud.
Some of my friends over at DotNetNuke have been talking to me about the latest version of their software. They're excited the new emphasis their favorite CMS is taking by combining traditional Web content management with enterprise social publishing capabilities. In fact, just today DotNetNuke Corp. announced the availability of DotNetNuke (DNN) 6.2, a social CMS that provides organizations the tools they need to easily configure and deploy internal social collaboration solutions and online communities.
I haven't had a chance to demo DNN 6.2, but I'll walk you through on what I've gleamed so far from the press releases and conversations within the community. I'm hoping to get an opportunity for a demo on the new features down the road but this will have to do for now. Just to get the definitions straightened out, what DNN is calling Social CMS is what I also like to call a Social Publishing Systems. Everyone has a different take on how to use social media, some companies get it while others are still trying to recognize their importance. Taking DNN 6.2 into consideration, it's apparent to me that DotNetNuke gets social.
The problem I have with top ten lists is that inevitably there is a story that should have made the list but didn't. Last week, I posted CMS Report's Top Ten Stories of 2011 and wished I could have included additional stories. The articles listed were ranked by popularity based by how many times viewed and the rate that they were viewed through the year. Popular stories do not always signify well written articles and they aren't always an indication of my personal favorites.
In case you missed these stories the first time around, below are ten additional content management articles we published in 2011. Every article deserves a second chance to be highlighted or tweeted again.
When I read the stories we post here at CMS Report, I am reminded how quickly the CMS market continues to evolve and mature. Every year, I worry that there is nothing "new" to write about in this information system niche only to have the developer, user, or owner of a CMS push another new story idea toward my screen. This time around when looking for the top ten content management stories of the year, I concluded we didn't have ten great CMS stories for 2011. Instead, I found more than two dozen great CMS stories for 2011.
Below are the top ten stories of 2011 that were posted here at CMSReport.com. The stories in this list are ranked based on the rate they were viewed since they first appeared at CMSReport.com.