Re: Wiki - What??

["Tom Jedrzejewicz" <tomjedrz@xxxxxxxxx>]

Wiki's are pretty slick, as long as you are not concerned with securing
individual pages within the wiki.  If you are, then you are better off using
a more sophisticated content management system.  You can do a trial with one
of the online wikis -- PBWiki (http://pbwiki.com/) is a pretty good one.

Chad Dickerson (InfoWorld) talks about his staff using a wiki for exactly
what you describe in this article ..
http://www.infoworld.com/infoworld/article/04/11/05/45OPconnection_1.html

I use TiddlyWiki as a catch-all for personal documentation, stuff I want to
keep, etc.  It is a standalone wiki, written in javascript, and contained in
a single, standalone HTML file.
--> http://www.osmosoft.com/

Have fun!

On 9/28/06, Turnidge, Dave <DTurnidge@xxxxxxxxxxxxxxxxxxxx> wrote:
> It appears that the brown stuff has finally hit the fan, and someone is
> getting serious about having a place for systems and "repair"
> documentation, and making documentation a top priority, i.e., "You WILL
> document what you have found out."
>
> So, I have read some stuff about Wiki and having it as a data store. Is
> this a good way to handle this kind of information? What do you consider
> the best method? M$FT is coming out with a new inter-office
> communications package "Sharepoint". Would that work for this? We have a
> package called Niku that could do it, and another called Magic... But
> there are too many possible places, and the net effect seems to be that
> you can't find anything, and up until now, it wasn't required that it be
> kept up to date.
>
> The folks on this forum are the ones that I want to hear from - based on
> what I have been reading ...
>
> Thank you for your ideas,
>
> Dave