A wiki is the central tool for sharing information about changing products and services centrally, efficiently and systematically. Are there best practises? We have compiled the most important questions.
When companies develop their services and products, there are many questions that need to be answered quickly and communicated to the relevant departments and teams:
What is included in the product?
How is the product calculated?
How does the product differ from competing products?
Is there a need to observe certain procedures and requirements at the time of delivery?
Where is there additional information about quality features or about similar products in the product range?
What are the experiences with this product and how should it be further developed?
Sales, development, project management and support depend on up-to-date information in order to carry out their tasks efficiently and efficiently. Continue Reading
The Wikipedia software MediaWiki is a well known solution for collaborative knowledge platforms. It is less popular, but not less ideal, for the development of prototypes and new platforms.
At this year’s Semantic-MediaWiki-Konferenz (SMWCon) in Frankfurt, our Hallo Welt! Technical Manager Markus Glaser talked about this connection between MediaWiki and prototyping. Here are the slides of his presentation.
Markus Glaser started his presentation explaining different forms of prototyping. His introduction was followed by showing MediaWikis richness of functionalities. By combining and expanding these functionalities, you can develop new and very specific applications. MediaWiki already provides a large toolkit, which allows quick adjustments without having to program completely new functions.
The semantic MediaWiki extension packages, which can be used to capture and query metadata, are certainly worth mentioning. Those are very useful, if for example data models are being modeled or user interfaces and operating elements still have to be positioned. Of course BlueSpice for MediaWiki supplies a wide range of options. Responsive skins like Chameleon are the basis for stylish surfaces. And with Lua you have a script language, with which the construction of a page can be designed very dynamically.
That means MediaWiki is an ideal base to build agile new knowledge platforms. The flexibility of MediaWiki means a great advantage in time. You don‘t have to be a programmer to build these prototypes, because a lot of these things can already be done with the integrated tools of MediaWiki. Like this you get a working system at an early stage, with which you can gather important experiences.
Nevertheless users should be aware that, despite the variety of integrated tools, developing a new knowledge platform is always complex and cost-intensive: planning, meetings and adjustments take time. After the development of an alpha or beta version, individual functionalities have to be professionalized and programmed independently.
You might say that the development of a stable productive system takes as much time as the development of the beta version for the first test users. However, the time and the risks of development are significantly reduced with the prototyping based on MediaWiki.