TWiki Success Story of SEAL Systems
We have started with TWiki in December 2000 at S.E.P.P. AG. Now, after a merger, we have about 80 people in our company SEAL Systems AG
. Starting with only two users, we wanted to write down some step-by-step documentations for internal work instructions and make them online in an intranet. We already had a Linux box with some static HTML pages, but there was the 'one webmaster syndrom' - it was hard to change some pages.
In January we made a presentation for other colleages and showed the extra feature you have in TWiki - change everything you like
Over the months we have filled our 'Startbox' for new colleages with more and more informations and instructions. And we have removed more and more 'Office' documents from our file servers. Now we have a TWiki web for the everyday use:
- telephone lists
- information about who is doing what
- some shared 'bookmark' pages for developers with intersting Internet links
- information about our QA department
- and so on...
All information is very fast to find and more up-to-date than our other documents have been. And it's very easy to link some existing informations together (from one Topic to another).
We are using TWiki in a mixed mode with remembering IP addresses plus using cookies in the browser. One department is using TWiki through a Windows Terminalserver, where more users are using TWiki with the same IP address.
Now there are about 50 people registered in TWiki. And there are more and more contributors to the contents of our pages (so the one webmaster syndrom has gone). There are about 1000 views each month in each TWiki web.
Our development department is using TWiki as a knowledge management tool:
- adding programming tips and share it with other colleages
- programming rules online
- small internal documentations of source codes are done in TWiki, with hyperlinks into our CVS sources (yes, even the code examples are up-to-date)
TWiki is very useful, because you can link to other HTML documentations (Qt, TAO, Javadoc, Doxygen, ...) without leaving your viewing tool - the browser.
Our latest modification to TWiki is an integration to our new nightly build and testing
machines. For our new development projects we use a new TWiki web where you could
- see the state of the last build of each machine
- view the logfile of the last build in a TWiki topic
- subscribe to another email notification (for receiving the logfile of the nightly build)
- trigger a new build at once (eg. after fixing some bugs)
Have a look at this screen shot:
With this TWiki interface, every developer could test the latest code on every build machine by one mouse click
. You don't have to checkout the sources, build all by yourself and run unit tests by hand. Just one click, wait some minutes - and TWiki shows the latest state.
- 20 Jul 2001
We have recently updated to TWiki 4.1.2 with great success!.
In the meantime we get used to the KoalaSkin and used the tabs. With the update to TWiki 4 I've written a small plugins to get the information from the WebList
page and fill a CSS styled tab for the same effect.
The look and feel with Koala Skin was like this:
New TWiki 4 look and feel with additional tabs looks like this:
- 26 Apr 2007