TWiki Reviews

I have used other collaboration tools, but believe me, TWiki is a gem for developers. The way it provides the option to extend features or content management in a secure manner is incredible.

if you new to TWiki you need to give time

if you are concerned about your content, you should use it. personally, i like it

I am admin for TWiki in a MNC and daily fixing lot of issues reported by end users

I like the best thing to see each subheadings for all skills to learn and made easy to search. lot of information to learn

I like to see more videos..also i see just Home button at top...try to add more there and some some heading are not working

Best way to web search about my work skills

Internal wiki contents, easy to modify, scalable, and has coding similar to WikiMedia, have all features that support the entire feature wiki.

Updating Twiki content template is quite challenging for newbies

I will recommend for Linux version TWiki

Twiki used during my work at RV-VLSI Design Center and enriched rich experience in modifying and upbringing wiki

Twiki is a powerful platform to visualize the data from different sources. Connection to database. Very easy to plot different charts.

Easy queries.

The error messages from twiki can be improved.

Plotting charts from a database.

Helps in my presentations to the management.

It is a great tool to manage the test planning and design documents.

It would be nice if Twiki would have Bugzilla/Jira plugins that can be integrated so that updates to documents can be easily synched.

Easy to manage multiple process documents. Twiki has rich features that give us the flexibility to maintain process documents.

Some of the plugin used were:

ChartPlugin: helped to plot charts to analyze data.

SlideShowPlugin: helped to created a nice presentation out of design documents.

I enjoy the kbs knowledge bay where you can get answer to common FAQs

Some of the interface is slow on loading content

Nothing at this time

Adding additional knowledge and documentation. Very good reference bank.

I like that multiple people could access and contribute to the documentation in our department.

Perhaps the original setup is a little tedious but if you take the time to make it right you good to go for duration of the product.

Great product for collaborating team tasks

Collaborating together as a team for a single cause to have the best documentation that is specific to our purpose.

It was simple and easy to use, and You can install own version of your TWiki in your organization, It also has various plugin supports and and can be integrated with other software's like LDAP etc.

To efficiently use the features of TWiki it require certain level of training, it will not be a straightforward things. Users need to understand how the Concepts of Web, Topic and attachment is linked. and there could be the cases where One Topic acts as a Parent for another Topics. So this architecture will involve certain learning curves.

Also initial setup will require certain efforts, like setting up Apache Web server first, then we need to install perl module / compile the perl module in apache.

It is nice to have exposure of PERL for a TWiki administrator.

TWiki as a Content Management option could be great, but you need to have a good administrator who can smoothly setup TWiki for you and can look upon issues on day to days basis.

We were trying to develop plugin in TWiki which will serve the Topic content to 3rd party software's like Google Search Appliances and other search engines. As TWiki pages are rendered from template it cannot be a straightforward web crawling, by crawlers. as 'view source' operation on TWiki page will just render template code, without any html body it's difficult to crawl the page.

The plugin which we developed help the Google Search Appliances and other Search engines to get the exact content from the template so the search can be fired upon such content.

It can either store the data in a database, or in files directly. The latter is also the traditional way for TWiki to store data. I prefer the latter since it's very easy to manage those directories and files, and problems if any can be fixed very easily. Storing data in database may sound convenient since you can query the data easily using SQL, but when it's not a short string or some numbers but a whole article, then personally I think that storing in files is a better way. This distinct it from other wikis.

It is made in Perl in the CGI way, which is kind of a very old technology, and it could be slower comparing with wikis made in PHP or other languages. Personally I used mod-perl to solve this problem, but other wikis can achieve similar performance without such additional effort.

I like TWiki and I am still using an old version of it (with many modifications by me) at home to keep my own information. I'd like to recommend it to anyone interested in finding a wiki tool to manage documents.

When I joined Lehman Brothers and started a new project, I found that there was no official way to keep and share documents (at least in that department). I prefer to document important things for my own use as well as sharing with other people. So I installed TWiki in a Linux box. It became so popular that I was asked to create some separate topics for other teams. Eventually the company adopted it and asked system admins to install it officially for teams to use.

Easy markup like feature.

Makes documentation & tracking easy

Was not in a position to upload any pictures

Project co-ordination