New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Passing Of The Baton As DNN Moves To The Next Chapter

nextchapterSaying Goodbye

In any endeavor in life and in business, you face ups and downs. Some things are easy, some things are extremely difficult, and some fall somewhere along that spectrum. This is definitely one of the more difficult blog posts I have had to write. I regret to inform you that the company and Shaun Walker have decided to part ways.

As all of you know, Shaun is the creator and original steward of DotNetNuke and was one of the founders and board members of DNN Corp. Shaun has been instrumental in the adoption and growth of both the open source platform and ecosystem. Over the last 12 years, Shaun has been the leader that everyone looked to for guidance, and the one we all rallied around as we worked together to grow the platform, the community and the ecosystem. Shaun’s passion, vision and dedication to the platform attracted many people to DNN and it is largely the result of his hard work that DNN grew to be the largest Open Source project on the .Net platform.

Everyone at DNN Corp. appreciates Shaun's commitment and efforts, and we wish him the very best both personally and professionally.  I will personally miss working with Shaun as he has been a big part of my professional life for over a decade. Shaun is still a major shareholder in the company and will continue to informally advise the company, and interact regularly with our CEO Navin Nagiah.

The Challenge

Earlier this week, Navin asked me if I was willing to step up and assume a bigger leadership role at DNN Corp. – in his words, to play a very proactive and forward-looking role for both the platform and the community.

Navin went on to say: “Your challenge will be to ensure the platform is still relevant 5 and 10 years from now. The toughest part is having the willingness and fortitude to focus on the long term, and make any short term trade-offs required to ensure the platform’s long term viability and success”.

To me, challenge and opportunity are synonymous. This is a lesson I was taught as a young Plebe at the US Naval Academy and is encapsulated in a quote from a naval hero of the American Revolution:

“Those who will not risk cannot win.” – John Paul Jones

I have actively sought out challenging roles my entire adult life and as a result I wholeheartedly accepted Navin’s offer.

I started working with DNN in 2003 when it was still called IBuySpy Workshop. I immediately became passionate about the software and it’s potential. The more I worked with DNN, and the more I got to know the people in the community, the more passionate I became. Since that first day of working with DNN, we have come a long way as a product, as a community and as an ecosystem. While I am proud of our successes to-date, I strongly believe that our best is yet to come.

Looking Forward

Just 3 months after I started using DNN, I quit my job and created a new company focused exclusively on DNN. That company is long gone but my passion and belief in DNN remains as strong today as it was then. What I knew then and still believe today, is that in order to realize our potential as a product and as a community, we must be forward-looking and creative. We must be willing to take risks, to make some mistakes and to learn from those mistakes.

We need to continue pushing the platform. Pushing to keep the platform on the cutting edge and relevant. Pushing to grow the platform user base. Pushing to increase the size of our ecosystem. Pushing to continue collaboration with our community in delivering a platform that our users love.

Since DNN was first released on Christmas Eve in 2002 a lot has changed in the development world. ASP.Net has matured as a platform. Webforms is no longer viewed as a cutting edge idea. Many developers in the .Net ecosystem have moved to the ASP.Net MVC stack. With the arrival of frameworks like AngularJS, KnockoutJS, Backbone and Node.JS, JavaScript becomes more and more central to how modern web applications are built.

Beyond how web applications are built, we have also seen a dramatic change in how web applications are deployed. Ten years ago, most web applications were hosted in a customer’s private data center or through a traditional hosting provider. Today, more and more customers are moving to the cloud where servers are provisioned and de-provisioned in mere minutes; where applications can be scaled up and down as website load demands; and where applications are being scaled across data centers spanning the globe.

During this same period there has been a revolution in the mobile and social space. Ten years ago smart phones didn’t exist and mobile websites were a rarity. Today Android and iPhones are everywhere and having a mobile website is a must for any serious business. Facebook was just a small project created by a group of Harvard friends, and it was only available to fellow classmates. LinkedIn was just over a year old and Twitter didn’t even exist yet. Today billions of people interact through these social networks, and the underlying concepts and technology are beginning to change how businesses communicate and interact with their employees and their customers.

In this same ten year span Microsoft has fundamentally changed the way they build and deliver software. Windows Vista was released in 2007 after nearly 5 years of development. Since that release, MS has moved to a model where software is delivered in smaller increments over a much shorter time span. Feature delivery schedules are now measured in months rather than years.

Not only has Microsoft changed the frequency of their releases, but they have also embraced community and Open Source in ways that were almost unimaginable a decade ago. Almost the entirety of the ASP.Net stack has been released as Open Source. Microsoft now works collaboratively with their user community to drive the ASP.Net roadmap and actively encourages community contributions to the platform. This is a major shift from an era where Steve Ballmer famously said “I don't really know that anybody's proven that a random collection of people doing their own thing actually creates value”, and that “Linux is a cancer that attaches itself in an intellectual property sense to everything it touches.”

These are but a few of the many technological changes that have occurred over the last decade. We need to take a hard look at how we modernize DNN to once again be on the cutting edge of development trends. Making these modernization investments will likely mean that we will need to make some hard choices. Can we support these new technologies while maintaining backwards compatibility? Should we plan for a gradual shift spread out over a few years, or should we make a major generational leap like we did with DNN 3 and radically change the architecture to support future growth – even if it means introducing breaking changes and some heartburn for those who want to stay on older versions of the platform and/or have no easy way to upgrade? None of these questions have easy answers – what is clear is that being wedded to the past means being irrelevant in the future. What is also clear is that we need to take some smart risks to move the needle again on the power of our platform, and on the opportunities it offers to people who embrace it.

Even beyond the technology, I think it is time that we revisited how we build DNN and see if the current development model is still the right one for DNN and the community. DNN has been on both ends of the spectrum from a fully open project developed by community members on the core team, to a fairly closed model where DNN Corp was responsible for the vast majority of the development effort. There are advantages and disadvantages to both models; we need to evaluate our success as a product under both development models and make the changes needed to ensure our continued growth.

I will share more details about my thoughts on the future in due course, but here is a snap-shot of some discussions we are having internally and with members of the community:

1. DNN Platform and Community prominence on

2. Technology Roadmap

3. Community growth – both in size and in level of participation

I will go into more details on each of these topics in future posts. I will also soon be presenting to our MVPs to discuss these and other issues. In the meantime, I am interested in what you think. How do you think we can improve the product? What technology should we embrace and which technology should we leave behind? What development model would you like to see us adopt? How can we better serve the community?

Exciting Times Ahead

I am excited about my new role at DNN. I am excited about working with all of you. I look forward to bringing my leadership skills to bear, and in making a difference to the platform, to the community and to the ecosystem. I am positive that with your help, our best days are ahead of us. There is a lot of work to be done but I relish the challenge Navin has given me and look forward to working even more closely with our community to drive this next phase in DNN’s growth.


Will Strohl
Congrats on the promotion, Joe!
Will Strohl Tuesday, August 12, 2014 5:43 PM (link)
Brad Bamford
Congratulations, Joe.
I agree DNN has needs to trim some fat, get lighter, and drop dependancies, to be a relevant leader once again.
Brad Bamford Tuesday, August 12, 2014 5:56 PM (link)
Ash Prasad
Ash Prasad Tuesday, August 12, 2014 5:57 PM (link)
Robrecht Siera
Congrats Joe! Make sure you visit next years DNN Connect meeting ;-)
Robrecht Siera Tuesday, August 12, 2014 5:57 PM (link)
Kristian Ranstrom
Congrats Joe! Thanks for your continued dedication to the platform.
Kristian Ranstrom Tuesday, August 12, 2014 7:28 PM (link)
Chris Chodnicki
Congrats Joe. Hopefully more details will follow soon from Navin and Shaun.
Chris Chodnicki Tuesday, August 12, 2014 7:28 PM (link)
Alex Shirley
Congratulations Joe !
Alex Shirley Tuesday, August 12, 2014 7:28 PM (link)
Ian Sampson
Congrats Joe.

Your post is really encouraging and I whole-heartedly agree with everything you say. For those us that have been immersed in DNN for years, we sometimes lose focus on those strengths that make DNN the amazing platform that it is. But whenever I compare alternate platforms, I always come back recharged and confident that we've made the right choices.

The future of DNN lies in keeping it relevant. Customers want solutions - not projects. Developers want popular standards maintained, IT departments want to minimise overhead. So stay on track with the push to the cloud, keep driving support for the client side frameworks and further encourage the development of overlaying solutions.

And we're all in this together - DNN's success lies in the depth of ecosystem.
Ian Sampson Tuesday, August 12, 2014 7:51 PM (link)
David Poindexter
Congratulations Joe - I am sure you will thrive in this new role and we look forward to all that lies ahead!
David Poindexter Tuesday, August 12, 2014 8:13 PM (link)
Daniel Mettler
Congratulations Joe :)
We'll miss Shaun :(
Daniel Mettler Wednesday, August 13, 2014 2:09 AM (link)
Jaydeep Bhatt
Congrats Joe, and I am sure, there would be more good days, under your leadership

I also started working on DNN ever since it was still IBuySpy, and I guess, what all that I know, that is only due to DNN

I have a few suggestion

1) When DNN was introduced, there was no good opensource webform framework with ready to use Modules and a helping community that shared the code and helped in every glitch. Now the scenario, as you have explained clearly, is different. Can we have a completely new DotNetNukeMVC framework?

2) When DNN started it was free & opensource, nothing to hide. However, ever-since the paid professional versions are introduced, looks like, most needed features are introduced only in professional versions. I understand, there is always need for the money to run any big project, of this stature, but can we think of raising the money by some other innovative means? like paid support, hosting, paid modules & skins? but have a single full-featured version of DotNetNuke free? May be you can have the Install Version Free and charge for the Source version.
Jaydeep Bhatt Wednesday, August 13, 2014 2:51 AM (link)
Geoff Barlow
Congrats on the new position Joe!
Geoff Barlow Wednesday, August 13, 2014 3:04 AM (link)
Leigh Pointer
Congratulations on your promotion Joe. If the baton had to be passed on, I can not think of a better guy for the role.
All the best, good luck and pour yourself a coke ;)
Leigh Pointer Wednesday, August 13, 2014 7:31 AM (link)
Robert Santuci
Congratulations, Joe! Continued success, Shaun!
Robert Santuci Wednesday, August 13, 2014 9:18 AM (link)
Ken Grierson
Congratulations Joe!
Love new beginnings, cannot wait to see what is around the corner
Ken Grierson Wednesday, August 13, 2014 2:07 PM (link)
Ernst Peter Tamminga
Nothimg is constant bit change. Every decision closets an opportunity while making the way forward more clear. I am looking forward to that way. Congratulations to Joe and I am sorry to see Shaun step aside. But we will meet again!
Ernst Peter Tamminga Wednesday, August 13, 2014 3:11 PM (link)
Robin Hogg
Congratulations and all the very best Joe! I'm sure there will be great things in the future of DNN.
Thanks for all that you did Shaun, I wish you all the best success in your future endevours
Robin Hogg Wednesday, August 13, 2014 3:37 PM (link)
David Cuthill
Joe, Congratulations.
I've been using DNN since 2003.
What I find is that people can't see past Facebook. That's what they think Social Networking is.
When I show them a full portal with memberships and private groups - DNN with business social - their response is "Who would be interested in that?" or "How could we get them interested in private social groups when everyone has Facebook". (I tell them that not everyone wants Facebook, Facebook is simply a steam of unindexed repeated bloat content. Plus it's a Security nightmare.)
Basically - they know nothing, and they know that - and they don't care.
Anyhow, The DNN Social Groups notification emails don't work/ aren't there yet?
DNN Authentication providers is a misnomer. They're Membership account duplicators.

Where can I go?

Booking systems, event organisation - people can see the value. So that's what I'm focusing on.
Dave Cuthill
David Cuthill Wednesday, August 13, 2014 5:06 PM (link)
Joe Brinkman
Thank you everyone for the words of encouragement. It certainly makes my job easier to know that there are still a lot of passionate DNNizens out there who care about the community and the platform. I look forward to working with you all in the coming weeks and months.
Joe Brinkman Wednesday, August 13, 2014 5:22 PM (link)
Wes Tatters
Congrats Joe on the promotion ... cant think of a more suitable person for the dnn batton to be passed on to ... look forward to seeing where the future takes dnn.
Wes Tatters Thursday, August 14, 2014 5:21 AM (link)
Mike Cox
My sincere congratulations Joe on the promotion, I think it will be a positive change for the community. You certainly have some tough decisions on your hands. I have been a DNN solution provider for about 10-years, I always found it best to focus on one platform and know it well and for me DNN is that platform. In all honesty, DNN has become a very big drag for me the past couple of years and it is becoming increasingly difficult to sell it as a solution which has left me searching for new direction.

The product is robust and offers some amazing features, but it needs to be completely re-engineered to make it friendly for administrators. I have witnessed release after release that focuses on developer enhancements but the end users are left left out in the cold. In a perfect world I would develop a site, turn it over to the client, train them and they would be relatively independent. What happens instead is the clients call me for nearly everything. I think the biggest issue you need to overcome is how to move away from WebForms, it requires way too many trips to the server, it is antiquated now and it is really holding the platform back. The control panel was still best in version 4.x, 5.x was horrendous and spawned Oliver Hine to build a nice one. Version 6 and 7 looked like an improvement, but are really poor especially in the age of mobile/touch.

Perhaps the community can make a entirely new DNN that gets rid of WebForms, eliminates postbacks, gets rid of popup windows, rad-editors, and offers a touch-friendly, responsive administrative UI. This would require throwing away everything except the database. Keeping the database structure would keep it familiar and might allow a migration path from legacy. This may also purge the module developers who are not serious about the platform.

All my best to you Joe, you are the most deserving of this promotion and I look forward to seeing what you can bring.
Mike Cox Thursday, August 14, 2014 2:24 PM (link)
Lance Long
Congratulations Joe. I like to hear emphasis on community and platform coming from the top.

As for tech, I highly suggest all css is migrated to LESS or SASS. Having used a css compiler on a large, multiportal project for the last year, I can honestly say it would be fantastic (eventually essential) for the DNN platform.
Lance Long Sunday, August 17, 2014 1:00 AM (link)
Robert Fulop
Congrats Joe!
Robert Fulop Sunday, August 17, 2014 8:49 PM (link)

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out