You can search text but that is messy and tends to give messy
results. Having a more structured approach tends to return more precise
data. At the same time it is useful to have direct links from the
structured results to more generic discussions as you catch bits and
pieces that haven't ever made it into the manual and can learn a little
bit of the debugging process by following other peoples discussions. A
good site should tie it all together. :)
*^*^*^*
Was it a dream where you see yourself standing in sort of sungod robes
on a pyramid with a thousand naked women screaming and throwing little
pickles at you? -- Real Genius
On Thu, 5 Oct 2000, Ronald J. Hall wrote:
> Michael wrote:
> >
> > There have been several stabs at such a project. The hard part is getting
> > people to contribute. It might work fairly well to copy the PHP manual
> > approach where people write/correct the real manual in CVS but each page
> > of the manual can have comments attached by anyone. So have each HOW-TO
> > owned by someone in charge of maintaining it (possibly via CVS?) and let
> > people add link, examples, and comments as desired. Then have the whole
> > thing searchable.
>
> How 'bout just using the Mandrake sites existing digests...don't they already
> have tons of info in text format, easy to search by keyword? Just a thought.
>
> --
>
> /\
> Dark><Lord
> \/
>
