Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why cant we keep the documentation up-to-date?Why cant we keep the documentation up-to-date?
Previous
 
Next
New Post
9/20/2008 2:11 PM
 

Jan Olsmar wrote
 

Regarding NAV its a scandal its not documented in my opinion.

There are books available:

http://www.packtpub.com/dotnetnuke-4.0-skinning-tutorial/book

No project of this size that gives the software away for free should be expected to provide complete free documentation.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
9/20/2008 2:30 PM
 

Michael I have most books , not this one I will buy it.

However most books are just basic and not useful for me. Maybee this one I will see.

Still I think if DNN change meny system one of the most vital parts of DNN some accurate documentation had been positive for the trademark DotNetnuke.

If the corporation does not think so Im afraid what will happen in the future.

 
New Post
9/20/2008 3:05 PM
 

Jan, the corporation do see the need and value in quality documentation - to quote Joe Brinkman earlier in this thread

"Carlos,

This is a known issue and we are attempting to address it.  There is a project that is just getting underway which will provide access to various pieces of documentation and which will provide more access to keeping the documentation up to date. "

Personally speaking I like that there are a large number of books on dnn now, but recognise that it's hard for books to be cutting edge due to the time involved authoring them and print cycles (the same applies to pdf documentation too, though the lagtime is shorter than for print books). That's why online materials are typically needed to ensure accurate, current information, and this is what the corp are working towards. Much of the information is out there in blog posts and forum entries, it needs better organisation & structure, and IMO a wiki to allow the community to contribute, as well as allow the core developers somewhere to document new enhancements quickly, without having the overhead of creating docs. As indicated by Joe, and other core members, we are making efforts in this area.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
9/20/2008 3:26 PM
 

Cathal, thanks for you answer.

Good to hear one more time that this will be addressed. I like books too. But most of all I like accurate information.

I will sleep well tonight ...

Thanks

 
New Post
9/20/2008 3:42 PM
 

I guess I'm coming from the viewpoint of a person who has spent hundreds of hours documenting DotNetNuke for free over the years. The fact that alternative information was not available was a big motivation for spending the time to create documentation.

That has changed greatly in the past few years. As I stated before I don't create documentation just so some will have a free resource.

It is true that the core intends to provide a central location for documentation, however I can't imagine that it will be complete and up-to-date all the time. The complaint seems to be for up-to-date information and I do not see any possible way that can be done without paying someone to do it. DNNAngel basically has a system that works.

I have to disagree with these points:

  • DotNetNuke will be "harmed" by the lack of free information. Serious users are willing to pay.
  • Other free Open-Source projects of this size have free complete up-to-date information.

I feel that I have a good idea of what motivates people to create free documentation and keep it up to date, it is the lack of ANY alternatives. I am spending most of my time writing Silverlight/DNN and Workflow/DNN articles because there are no alternatives. As soon as the book publishers catch up believe me I will find something else to write about.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why cant we keep the documentation up-to-date?Why cant we keep the documentation up-to-date?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out