Gerhard Fiedler wrote:
> I kind of agree. For a wiki, you have to structure your thoughts, and then
> put it into the form of a wiki. Almost nobody writes in wiki format, so
> that's a translation process that probably almost nobody will make after
> the original document has been written. And if no document has been
> written, it's probably even less likely that someone sits down and puts his
> or her thoughts into written form just to put it in a wiki.
> 
> I'd probably rather see that the already existing "database" of internal
> components gets indexed (not the descriptors, but the contents) and a
> search engine is available for that. This can't (or shouldn't :) be that
> difficult.
> 
> Gerhard
> 

Thanks to those who explained what they use wiki's for at work.  Now I'm 
more tech-savvy than a banana ;>

My company has grown from 2 guys for 10 years to 10 people in 2 years. 
Projects going on that need *lots* of documenting (instead of the good 
ole 'just keep it in yer head' method) are in need of some system to 
make the info available and useful.

Searchable would be a nice attribute too.  Many of our docs are PDF's; 
are there good search tools that can quickly query a directory full of 
PDF's?

Aside from searching, an HTML page linking to the docs seems like a good 
idea but we have not implemented anything yet.

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist