"yo, check this stuff out! alternate energy, cool stuff! You get free electricity, you get more from your crops, keep your cash, don't ship it to bigagco! Composting! Methane digesters! solar PV panels!," and etc etc This is me, 30 years ago, talking to my boss, farmer smith (no lie, his name really is smith) This stuff exists in every field, not just white collar office work One way or another, a Wiki design is definitely the right idea for corporate "document" databases.
#TWIKI VS MEDIAWIKI UPGRADE#
The disadvantage is that another rewrite might leave you stranded with a difficult upgrade path. The advantage is that it got that way through several rewrites and careful coding by its maintainers. MediaWiki is clean, easy to use, and (always important) extremely feature rich.
If I had to choose, I'd probably say that extending MediaWiki would result in the best option. MediaWiki (the Wiki that runs Wikipedia) is probably the best compromise, but it lacks some of the security features that make TWiki viable in a corporate environment. PHPWiki solved many of the problems by taking the KISS (Keep It Simple Stupid!) path, but lost a lot of functionality along the way. Something like it perhaps, but TWiki itself tends to be unwieldily, visually confusing, and ugly.
OTOH, I don't know if TWiki is the answer. It stops working whenever it feels like it, and occasionally corrupts the database just to make your day. S the whole world going to be using wikis instead of the proprietary dinosaurs like Lotus Notes?