Last updated by senpai on Sat, 2007-02-24 23:46
As an experiment, I have created a new content type called 'wiki page' and given everyone the permission to edit them. This post is an example of one. Feel free to edit it, within reason. Your edits don't generate email notifications but might generate items in rss feeds depending on reader preferences.
One gotcha that is eventually fixable is that anyone can edit a wiki page, and not just a group subscriber. Thats not a big deal on g.d.o, since we almost all groups are open subscription anyway. A workaround is to make the post Private, and thus restrict viewing and editing to subscribers.
Ideas for improving the usability of the wiki pages
- provide some UI that clearly indicates they are a wiki page such as the "This is a wiki page - you can edit it." with the "edit it" part linked to the edit function
** one idea is to override the theme_menu_local_task function and use a different CSS class for the local task tabs on wiki node types - Diff would of course be nice, but I hear that it's borken right now (?)
** Ideally, I'd like to see a 'side-by-side' diff, similar to that used in MediaWiki. I've looked at the DifferenceEngine.php file in MediaWiki, but it is way beyond my PHP coding level. (gmak) - It feels weird not having comments. I think comments could work similarly to the "talk" pages on wikis, especially if provided in a collapsible/collapsed fieldset
** is there an easy way to list comments as a local task link, as opposed to below the node? This would be very similar to the 'discussion' tab on mediawiki, for example. - would it make sense to allow a wiki to be anonymous? being that a wiki is collaborative by nature, the doc could evolve into something completely different than what the original author posted.
** Senpai sez: Yes, Wiki posts on g.d.o should be anon, so that the document can take on a life of its own. I feel weird editing this page, because it's gonna look like Moshe originally wrote this sentence. Let's make a wiki setup that d.o can eventually adopt, and start by making wiki pages a-nony-mouse. If it's absolutely required to know who wrote it, start with a "posted by:". Remove that info once the page is re-written my anyone else. Or, better yet, maintain ownership info for site admins, but theme the g.d.o site to remove that info for wiki content. - what else?
I'd love some suggestions for how to present wiki pages differently from other pages and also additional features like real wikis. We already have markdown input format, in case you never noticed that. I'd love a 5.0 version of tweakbox module which provides a Table of Contents filter.
*** There is a hacked version of the TOC module (from TweakBox) which I have managed to make work with Drupal 5. You can find it here. (gmak) ***
Also, folks might want to experiment with group specific categories (see the categories tab on group home page) in order to help visitors navigate your group and its wiki pages.
This is very cool! I wonder if this change shows up in the diff...
Apparently down here we can do whatever we want and it's outside of the diff. is that on purpose. m3avrck smells bad! (<-nobody knows that I wrote that!!!)
I don't see anything wrong with enabling comments... seems to make a lot of sense on the drupal handbook interface -geilhufe
I'm writing over some text to see if it shows up on a history page. Is there anyway to view the history overview presently?
This may be a stupid question, but how do you tell the difference between a wiki node and a story node, or does it matter?
How about getting something like mediawiki input format working - I tried but it requires a bunch of other php/wiki files and the directions are skimpy. -harriska2 (nevermind, motzi created a module for PEAR wiki which includes tikiwiki and mediawiki syntax along with a bunch of other types - works great) -harriska2