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.

DNN Trademarks

When DotNetNuke was originally announced in February 2003, the developer community in its insatiable appetite for simple concise technology acronyms, immediately abbreviated the DotNetNuke name to 'DNN'. This short-hand reference has been synonymously linked to the project ever since, especially in on-line communication channels such as the forums and blogs hosted on

As this term gained popularity in the community, it became clear that the 'DNN' acronym had established itself as an essential part of the project branding, and as a result, when we embarked on the legal process of protecting the intellectual property of the project in 2005, we submitted trademark applications for both 'DotNetNuke' as well as 'DNN'. Both of these terms gained official registration status in Canada, and later 'DotNetNuke' gained official registration status in the United States ( unfortunately due to an oversight on the classification description for 'DNN' the application had to be abandoned and resubmitted ). And for those of you who read the first chapter of the Professional DotNetNuke 4 book, you know that we also submitted an application in Australia in order to block a third party from acquiring ownership of the marks. Protecting the identity of the project has been an ongoing challenge, both in terms of effort and financial expense, however we realize that it is a responsibility which is essential to our ongoing stewardship of the project and ecosystem.

In the last newsletter, I mentioned that we wanted to try and do a better job of highlighting good citizenship in the DotNetNuke community; therefore, we are very pleased to announce that we recently reached an agreement with Gavin Smith of Executive I.T. Ltd for the transfer of the domain name ( click on and you will be conveniently redirected to ). The domain name was obviously an attractive acquisition, as it contained both the 'DNN' trademark as well as the '.NET' reference which is fundamental to our platform. As a long-time community member, Gavin indicated that he deeply respects the contribution that DNN has made to the development community, and as a result, he was willing to respect our rights in the DNN mark and give up the domain name in the spirit of the open source project. We definitely appreciate the professional integrity and ethics demonstrated by Gavin, and look forward to helping support his future endeavours in the DNN community.

Since we have been fielding a variety of questions lately in regards to the DotNetNuke Trademark Policy, it may also be useful at this time to highlight a few of the more commonly misunderstood items.

In stark contrast to the more heavy-handed policies which most vendors impose as part of their trademarks, we have always taken a more practical approach, as we realize that vendors within our ecosystem need to be able to clearly express their support for the platform. Our trademark policy was introduced in 2005 and is actually based on the Mozilla trademark policy for FireFox and related products, although we did introduce some custom modifications in order to provide more freedom to the members of our community.

For example, we provide the DNN community with explicit permission to use our trademarks within their domain names or company names. The only exception are top-level domain names or company names which consist solely of our trademarks. For example, it is acceptable to use a domain name such as '' but it is not acceptable to use a domain name of ''. This policy attempts to balance the overarching requirement that trademark usage must be non-confusing, while still allowing community members to describe their affiliation to the project.

In addition, we also allow third party developers who are building product extensions for the DotNetNuke platform, and offering them to users as independent product packages ( seperate from the DotNetNuke application ), with the ability to use the trademarks in their product names. For example if you have a custom extension for DNN, it is acceptable to show affiliation to the platform and refer to the product as 'DNNExtension' ( although we would much prefer if you used the phase 'Extension for DNN' as it provides much more clarity for consumers ). Again, this comes back to the general requirement that trademark use be non-confusing.

The only instance where trademark usage is strictly prohibited is in situations where third parties want to offer customized versions of the DotNetNuke application to their users. This may include custom modifications to the core application and/or bundling of the application with proprietary intellectual property. Since the customized product is no longer an accurate reflection of the official DotNetNuke application, it would be misleading to refer to it as such. As a result, we kindly ask that organizations use their own distinct branding to refer to these custom products.

The items above help clarify the majority of questions we receive on this topic and I hope exemplify the lengths we go to, in order to allow the community to obtain the maximum benefit of the DNN brand in their business pursuits.



There are currently no comments, be the first to post one.

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)
Timo Breumelhof (24)
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