Robert Van Overmeiren wrote:
Amen.
There are so many topics and sub topics and information all over the
place. If you could just go to one place and drill into what you need...
Have you ever seen the Microsoft Developer Library (are you allowed to
say the M word here?)? It's a huge tree that you can drill and drill
into. You can search, synchronize, and access a vast array of
information.
I know you're thinking I could volunteer to assemble it, but I wouldn't
know how to systemize the whole thing.
I am not familiar with the MSDN library, but I know this: One of the
worlds largest digital knowledge repositories is run on a wiki. You got
it! wikipedia.org. This proves that a wiki is an excellent repository
for contributal knowledge.
The wiki has long been synonymous with documentation of open source
projects. It does the job and does it good. One of the bad things (or
good things) about the wiki is that the quality and structure of the
knowledge is only as good as the effort put into maintaining it.
The developer documentation is much harder to maintain and update. The
wiki should always be several steps ahead of the dev docs. Imagine that
the best of the wiki goes into the dev docs, and the bug-fixes, hacks
and work-arounds are kept out. The dev docs are something you can rely
on when using a stable release version ("stupid" users shouldn't have to
use the wiki).
Summary: Update the wiki more, lazy people :)
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
