> I don't know too much abt wikis etc but I think
> pointing a beginner to the mailing list archive
> is not so good. You could very easily get lost.
> And I use ant, maven, torque etc but I don't
> even know where their wikis are located. The
> point is the main website of the project is the 
> "chief" source where people look for
> information. In my opinion that information on
> the websites is what has made projects like Ant,
> Struts etc so popular.
> 
> And making html webpages out of information is
> not a big deal. Give me the information and
> I'll make the webpages. 
> 
> I think it is wrong to assume that people would
> take wikis very seriously, typical mentality is
> to look for information on the website. 
> 
> If making the wiki is first step towards making
> the complete website then it is ok though.
> 
> 
> Vikas

As a beginner in Avalon I have to agree with the sentiments expressed above.

I always look first to the primary website for documentation. After reading
the documentation and the FAQ I should be able to get a basic configuration
up and running with a demo app that I can create myself. If I decide to go
further and have difficulties beyond what the documentation and FAQ address
I will then go to the mailing list archive and search and then post to the
mailing list.

If a site does not have documentation that demonstrates how to get at least
a demo application up and running then my first thought is that the
developers don't think enough of their project to want others to effectively
use it and I will typically abandon it. Given my research into other
application frameworks and technologies that will solve my problem set that
is my most likely course of action w/ Avalon as well.

As far as Wiki sites go I have yet to encounter a Wiki site that provided
quality content that is presented in a format that can be easily used. My
experience w/ Wiki sites is that they are ugly and/or empty. It is *NOT*
suitable for end user documentation.

Personally I don't even like HTML documentation. I want a PDF document that
I can simply scroll through and read w/o having to click and click and click
and click.

If you want people to use your project, document it and document it well.

rjsjr

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to