twiki_application1Add my vote for this tag create new tag
, view all tags

TWiki Applications Showcase

This topic is intended to showcase new and interesting TWikiApplications. TWiki Applications are specific applications of TWiki technology to user problems. A TWiki application is usually built up out of the building-blocks found on this site (TWiki core and plugins) but will sometimes use external technologies, such as homebrew plugins or interfaces to external tools. If you have an interesting application of TWiki, please add a link to this page!

TWiki Applications showcase:

  • HeyHoPress - AndrzejGoralczyk An editorial control system I'm implementing now in my CXO magazine, and also a working expert system for management techniques.


My employer has an interesting question: (how) can twiki be used for an online banking to consumer web application? For instance by an account manager that want to track customer requests and feedback? Anyone experience in this field? Or ideas?

Perhaps broader: what kinds of internet applications outside of the intranet domain?

-- ArthurClemens - 25 May 2004

Arthur: at first glance it seems to me that using an enitre twiki installation, just for gathering feedback from customers seems like trying to lighting a cigarette with a flame thrower (simply put, its overkill), however upon further consideration I was thinking that one obvious method to doing this would be to install the twiki in "the background" and utilize CommentPlugin, Threads and Includes to allow customers to post feedback and comments (or suggestions) to the twiki (which could then be included back onto the main page from that twiki). ofcourse other aspects might be useful aswell (such as Notifications etc.)

Doing so in a transparent way so that submitted items go directly from the main site via a comment form to the twiki and then including some or all of that information back into that main page gives the advantages of having a uniform looking website (and security) while taking advantage of many of the desired twiki features.

To the second question; about using twiki on the internet in general, I have found that a nicely skinned twiki is fully capable of displaying itself as a "normal" website, while at the same time providing wiki features to those who would be interested in using them. Again, I suggest heavy use of CommentPlugin and Threads, but also TreePlugin is useful in this area aswell.

-- TravisBarker - 26 May 2004

Arthur, on customer feedback: I see it similar to Travis. Web pages (static or dynamic) have comment boxes to provide feedback. For doc pages it could include also some checkboxes like "did this answer your question?" etc. The data can be gathered behind the firewall in TWiki pages where employees can act upon and add additional content. This could be in the unstructured Wiki way, or with some structure provided by a TWikiApplication.

TWiki on Internet: I see several use cases.

  • A publishing tool for FAQ and knowledge base. That was TWiki's initial use, see TWikiSuccessStoryOfTakeFive
  • A web authoring tool where the webmaster controls the layout and domain experts contribute content. The website are generated HTML pages based on TWiki content. See PublishAddOn
  • As an extranet where partners work together on a protected TWiki installation. Many outsourcing firms do that. Often involves a custom TWikiApplication to track projects.
  • As a Wiki to gather feedback on a product. I have not seen that much, this requires a more pervasive understanding of how Wikis work (a matter of time; the recent BusinessWeek article helps). One example is the web site of the GPLed IPCop Firewall

-- PeterThoeny - 29 May 2004

Arthur, rewinding to your question about uses of twiki, above. What you are describing is one aspect of customer relationship management (CRM) and yes, people have used it this way. The solutions range from a simple informal DB of customer contacts, feedback, and documents, to a full-blown CRM database with process tracking.

Depending on how "formal" you want your process to be, TWiki has a range of solutions, from "bantamweight" using twiki topics to store customer info and some naming scheme for each customer, through "welterweight" using SEARCH to infer links and collate summaries, through to "cruiserweight" using plugins such as FormQueryPlugin to build "database" solutions, and finally through to "heavyweight" using integration of bespoke DB-based CRM solutions.

Exactly where you start depends on what you want i.e. your question is a bit too general.

-- CrawfordCurrie - 25 Jul 2004

As SteffenPoulsen mentioned above, Wikis are placed by Gartner in the "hype cycle" of emerging technologies. Better address to check is here (look at the list in bottom part of the pop-up page from "Hype Cycle for Emerging Technologies, 2004" link if You are not registered).

Gartner expects that during next several moths Wikis will attract much attention of business sector, and their advatages will be overestimated; then there will be a period of disillusionment, and then a plateau of mature business applications. So, for the best advocacy during this turbulent period we should prepare and present as mnay as possible real, working applications. Noting is better to promote product among business people than the real case and real experience of the company using it.

From my side, I'm going to present in the Sandbox (later this month) full editorial system I'm implementing now in my CXO magazine, and also a working expert system for management techniques. I already presented some features of TWiki in good and famous conference on Mind Mapping in Warsaw this summer.

-- AndrzejGoralczyk - 10 Aug 2004

Good summary. Yes, we definitely need good examples of applications and websites/intranets. And working examples of plugins, not targeted towards collegue TWiki users, but towards laymen, managers, etc.

I have layed down an outline earlier in CommunicatingTWiki. Other work to do is in TWikiBrand. Once Cairo is finished, this is one of the main tasks of the coming months. Everyone is invited!

-- ArthurClemens - 10 Aug 2004

As promised on 10 Aug. above, I made a copy of full editorial system in the Sandbox. The main interface HeyHoPress, and about of 40 topics making all the machine, are translated from Polish; I'm not so good in English, so please correct me as required.

The application, albeit rather big, is quite simple but looks complicated; so I'm going to write HeyHoPressDocumentation as quickly as possible. I also have to type the copyright note in.

-- AndrzejGoralczyk - 29 Aug 2004

Your English is just fine; infinitely better than my Polish! frown

The application looks really interesting. It would be good to have a simple statement of the goals of the application (how you intend to use it). I think I understand just from browsing the pages, but it would still be very interesting to see a rated features list that you are targeting. For example, you have limited project planning and tracking, but that may simply not be on your radar.

-- CrawfordCurrie - 30 Aug 2004

Right, Crawford. Project planning is rather rare activity in everyday life of editorial team. The main purpose of this application is to track multiple workflows, mainly the editorial work on the issues and texts. This is production process, similar to that in any industry: we process the material (texts), and assembly the successive specimens of the product (issues).

-- AndrzejGoralczyk - 30 Aug 2004

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r4 - 2006-02-14 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.