Slashdot Mirror


Other Uses for Wiki Software?

CodeMonkey22 asks: "The much-discussed Wikipedia could be considered the quintessential definition of what Wiki software is capable of. More recently, however, a plethora of specialized reference websites, such as Wookieepedia (Star-Wars) and the Marvel Database (Marvel Comics), have popped up. This got me to thinking, are websites the only viable use for wiki software? Working in an IT department, the first alternative that came to my mind was an intranet knowledge-base. TWiki, for instance, touts itself as 'an Enterprise Collaboration Platform'. What other uses could take advantage of Wiki? What changes would be needed to make it more applicable in other areas of use?"

5 of 113 comments (clear)

  1. Collaborative Documentation by tonsofpcs · · Score: 4, Interesting

    Documentation for open source projects, such as this example from VideoLAN's wiki. Also, collaboration on new features

  2. TiddlyWiki by belroth · · Score: 4, Interesting

    TiddlyWiki (http://www.tiddlywiki.com/) is effectively a wiki in a single web page. It sounds odd but is very impressive, it can be used for free format note keeping with all the linking etc that a wiki implies. There are a number of enhancements on the web - various customizations including skins.
    It's obviously not for multi-user use but great for personal stuff.

    --
    I hereby inform you that I have NOT been required to provide any decryption keys.
  3. Some wiki uses by JoeCommodore · · Score: 4, Interesting
    At LinuxWorld I saw the Twiki demo and it got mymnd racing, a couple of these were from it.

    Agenda tool, (non-profit here, lots of meetings), you create an agenda wikipage for the next meeting, participants add or make changes to the topic list after the meeting the notetaker completes the page by ading in the outcomes and creates the next agenda page, not only do you have less paperwork you also have a building history that all can refer back to without hving to look up file names.

    Staff directory - (assuming you don't have like AD or LDAP), includes addresses emails, etc. Changes are made on the spot and therefore most up to date.

    Knowledgebase - either a replacment or an extension to the job procedure manuals, all staff can add into it and make changes as needed, as well as add content as special circumstances arise.

    Documentor - if the apps are web based you can even program wiki links into your pages to the documentation (as well as link in your job procedures if on the same wiki) As program changes or as better instructions/definitions the documntation gets updated.

    Project notes repository - self explanitory

    Simple CMS - Keep the editing behind a password/access system but offer up the content as read-only to the public, opens the sirte for editing beyond just the webmaster.

    I like the story board idea.

    --
    "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
  4. Re:Tech Support? by Anonymous Coward · · Score: 5, Informative

    See Trac ("an enhanced wiki and issue tracking system for software development projects"), which integrates both a wiki and a ticket system (among other things such as version control) together. This means you can use wiki markup in tickets and commit logs, and link from wiki pages to tickets etc and vice versa. Nice :-)

  5. Wikalong - Collaborative Annotation by phUnBalanced · · Score: 4, Interesting

    I just released a new version of Wikalong that is compatible with Firefox 1.5 last night.

    Wikalong is a Firefox Extension that embeds a wiki in the Side Bar of your browser, indexed off the url of your current page. It is probably most simply described as a wiki-margin for the internet.

    Wikalong