Ok, that explains much of it. What I thought that it would be the relative effortlessness in developing a wiki or something. Every programmer who wants to try their teeth on a new programming language goes ahead to write a wiki using that language :)
SocialText and ProcessWiki are new to me. Had been trying some wikis recently and found that instiki and dokuwiki are quite good. But I am just overwhelmed by the sheer number of wiki software... I think someone like me who just needs to setup a wiki for their projects will need to do a good amount of experimentation.
Specifically speaking neither socialtext nor processwiki are engines, but extremely modified products. Mediawiki has a lot of issues that made us terribly unhappy because it works on a 'storage of knowledge' basis, as opposed to processwiki, which accepts a more dynamic usage of the data. Because I am involved in some amount of Process Documentation (typically involves tracing genesis of idea, team, timelines, obstacles and various levels and stakeholder perspectives), an engine like processwiki was pretty useful.
The way I see it, even Wiki 'development' has gone into the supposedly non-techie turf. You should see the way we marauded the engine into accepting our needs. :)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
SocialText and ProcessWiki are new to me. Had been trying some wikis recently and found that instiki and dokuwiki are quite good. But I am just overwhelmed by the sheer number of wiki software... I think someone like me who just needs to setup a wiki for their projects will need to do a good amount of experimentation.
no subject
The way I see it, even Wiki 'development' has gone into the supposedly non-techie turf. You should see the way we marauded the engine into accepting our needs. :)
Go forth and wikify. (Or, something like that)
no subject
Doing it, doing it :)