| Kind of Install |
Developers do |
End users do |
Types of users |
Examples |
| Form-based apps |
TWikiForms, templates |
Filling out forms, possibly using simple mark-up in text area fields |
|
the Bugs database, BlogUp |
| scientific document preparation |
|
weekly notes write-up, journal and conference paper preparations |
|
Extensive use of templates (both TWiki front-end and LaTeX back-end) to separate content from layout |
| team management |
|
share minutes, actions, evets, news, discussions through forms and comments |
|
form creates page with comment boxes and twisties in the right places, pages are automatically indexed in dashboards. no 'edit' needed. |
| engineering knowledge base |
form-based wikipedia |
share basic knowledge, cookbooks and practical experiences on a specific field |
|
Basically how Codev is used, with some additional plug-ins for the requirements of the engineering community |
| Software Development |
1 form-based app, 1 application that combines topics and plugins, XpTrackerPlugin |
Creating tickets for the software product being developed, tracking changes to each version, tracking progress on the development plan |
|
The ticket system is much like the Bugs web. |
| quality management system |
Standard TWiki with customised skin. |
Writing text, collating processes, forms, templates, examples, boilerplate documents and so on. Could be called a knowledge base. |
|
Published every 6 month as a static html site to the corporate extranet. Published on Cd and distributed to sites without internet access. |