Use Cases


Without objectives in mind, the Cross Lingual Wiki Engine Project is impossible to shape. Target sites and use cases will orient the development priorities. This page explains the objective of use cases, explain how to contribute your use case and lists the current use cases.

Proposed methodology

  1. Allow anyone to contribute their use case for wiki translation
  2. Classify and group the use cases
  3. Identify tools that could be used
  4. Track successes and failures after deployment
  5. Improve tools, documentation and selection criterias

Our list of use cases

Add your use case below.


Any use case is welcome. The more we have, the easier it will be to identify recurrent needs and to define priorities. Here is a suggestion list of information that could be useful.

HINT: Make the Use Cases as concrete as possible. Write them as though you were a novelist trying to write a compelling and believable story. Instead of talking about "the user", talk about say, "John from Marketing". Make these people sound like real people. Heck, if you can think of actual people who fit the bill as actors for the Use Case, use them!

The questions are not meant to be answered directly, instead, they should be used as a guideline for the information to provide.

Site: ?
  • For which site? What's in it?
  • Is the content specific to a field of expertise? Which one?
  • How much content has to be translated?
Current wiki engine: ?
Contributors: ?
  • Who are the contributors?
    • Volunteers or employees?
    • Experience level?
Translators: ?
  • Who are the translators?
  • Are they the same as contributors?
Translation tools used: ?
  • Do translators use dictionaries, translation databases or automatic translation tools? Which ones?
  • Which techniques are used?
Maturity stage: ?
  • Is content currently translated?
Peculiarities: ?
Contact person: ?
Priority needs: ?

To contribute your use case, simply create a page and add it to the list at the top of the page.


After a brainstorm session during CodeFest 2008, a few differences between types of usage have been outlined.

  • Amount of content consumers vs amount of content producers
  • Mandated vs non-mandated
  • Document is an end in itself vs a way to achieve results
  • Translations must be aligned vs used in a synergistic way
  • Control is top-down vs organic
  • Content quality is important vs draft sufficient for communication

Upcoming Events

No records to display