Products

Solutions

Resources

Partners

Community

Blog

About

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.


Community Blog Guidelines

dodontThe DNN Community Blog should be a place not just for news and interesting information, but a source of conversation and sharing of ideas.  The Community Blog exists for DNN community members to post topics, and for other community members to provide the conversation via the comments.  The interaction between author and commenter is what makes blogging great!   

As part of making the community blog great, and to help keep things on track, some guidance is needed.  This applies to posts and comments equally; there’s no special treatment for authors.  The following guidelines will help ensure the blogs are a source of quality information for the community:

DO:

  • Be positive. Communities don’t thrive with a lot of people being negative and depressing.
  • Be constructive. If you want to make a negative comment, or a negative post, do so in a constructive manner.  Instead of just saying why something is wrong, bad etc., provide commentary that shows how things could be improved.
  • Be respectful. People should feel like their participation is valued, even if you disagree with their opinion or feel they have made a factual mistake. 
  • Provide context. If you are posting a link, the context of the link should provide an indication of the destination site, and what the reader is likely to find at the link.  The context should allow the reader enough information to make a decision on whether the link is worth following.  Your links should be a like a term paper reference rather than clickbait.
  • Blogging about Open Source modules is acceptable and encouraged. However, you should limit posts about a single module to no more than one or two per month. We don’t want the community blog to be monopolized by a single module, but rather it should provide a good mix of content.

DON’T

  • Short comments like ‘wow’ or ‘cool’ or ‘awesome’.   While the sentiment is great, it doesn’t really add value to the conversation.
  • Support questions.  A short question to clarify content in a post is OK.  A detailed support request is not.  Please use the Questions and Answers function for asking questions.  It should be obvious that a blog post isn’t the right way to ask a question.
  • Multiple questions by one commenter. We know – you’re too busy to write something short.  Brevity is difficult, but please try not to post endlessly and fill the comments with a one-way conversation with yourself.
  • Really, really long questions. A close cousin to the support question and multiple question: really long comments break up the flow and actively make reading the comments less enjoyable.  Keep it short. Long comments may be trimmed by moderators to keep the comments readable.
  • Personal comments about Dnn community members and Dnn staff members. Don’t be mean or personal.  If you have specific feedback, write them a personal message.  Don’t write anything you wouldn’t want said about a member of your family.
  • Off-topic comments. If you have something to say that is unrelated to the post or another comment, say it in your own Forum thread. Don’t hijack the conversation. 
  • Self Promotion/Advertising/Solicitations/Business link building. Blog posts or comments which are advertisements for a business or product, or are built as gateway linking pages to the Dnn Store are not allowed.  Use the Announcements forum for that.
  • SPAM. We will delete SPAM with extreme prejudice and may ban the poster for repeated or really obvious SPAM. 
  • Excessive links. The Community Blog is not a link farm for people to abuse.  Relevant links to source material in a blog post is acceptable as long as it is not excessive. More than one (1) link in a comment may be considered SPAM and we will take appropriate action.  All links in blogs and comments are subject to being automatically modified to include the nofollow attribute.

These guidelines are retroactive for all existing blog content and may be be updated in the future, as necessary. We reserve the right to moderate content as necessary to match the guidelines and ensure the community blog provides content that provides value to the entire community.

Comments

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

Comment Form

Only registered users may post comments.

NewsArchives


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
https://www.dnnsoftware.com/community-blog/cid/155330/community-blog-guidelines
www.dnnsoftware.com
crawl=CC-MAIN-2020-16
104894
application/http; msgtype=response
sha1:CW7ICXGMHUB2TURQMFMXAKCRVXW6TOKU
<urn:uuid:34463f12-ea16-4313-87b0-5de94639f869>
2020-04-02T13:36:33Z
104.27.130.29
text/html
sha1:72SUAEAI2WAYRDCM3NRQVFYKVNWA33PC
<urn:uuid:f38c90aa-10ae-487e-9786-17f84fb2299c>
https://www.dnnsoftware.com/community-blog/cid/155330/community-blog-guidelines
response
<urn:uuid:228852c7-a475-4f6d-b6e9-e59cec0df1f7>
isPartOf: CC-MAIN-2020-16
publisher: Common Crawl
description: Wide crawl of the web for March/April 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-100.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/