Under the generic term “BlueSpice Social”, a whole series of functions converge in BlueSpice 3. The goal is to support teamwork and collaboration among wiki users and thus improve the quality of wiki content. An interview with Dr. Richard Heigl, CEO of Hallo Welt!
It doesn’t always have to be text. A smart mixture of written and graphic content is recommended to overview information and quickly absorb knowledge. Markus Glaser, CEO of Hallo Welt! GmbH, explains the possibilities of visualization in the BlueSpice enterprise wiki.
In short interviews with our employees we illuminate aspects and questions of our daily work with BlueSpice and our customers. Today’s topic: rights management. An interview with Florian Bäckmann, responsible for technical support at Hallo Welt! GmbH.
For ten years now, TenneT TSO has been relying on a BlueSpice MediaWiki from Hallo Welt! GmbH. From a reference book for the network operator’s construction and operating guidelines, the wiki since then has developed into a company-wide encyclopedia with currently around 11,000 articles.
In short interviews with our employees we illuminate aspects and questions of our daily work with BlueSpice and our customers. In this article, we will focus on the topic of customizing. An interview with Sabine Gürtler, Team Lead Service & Support at Hallo Welt! GmbH.
In short interviews with our employees we illuminate aspects and questions of our daily work with BlueSpice and our customers. This article deals with the topic of data migration. An Interview with Robert Vogel, Team Lead Product and Software Development at Hallo Welt! GmbH. Continue Reading
The Munich software company Ryte has been using a BlueSpice 3 wiki from Hallo Welt! GmbH for its reference work on digital marketing. The resources maintained in this way are regularly cited in academic theses and make up a large part of the sessions logged on the Ryte website.
“At the start, our developers simply built and maintained a wiki just for us. We had nothing like we have now,” explains Pauline Mitifiot. She is a marketing expert at Ryte GmbH in Munich, a SaaS (Software as a Service) company founded in 2012. Now, Ryte’s wiki has become an important treasury, a leading online resource of its type. In February 2018, the encyclopaedia was transferred to a BlueSpice MediaWiki wiki from Hallo Welt! GmbH. The reason: “the wiki had started to consume too much of our developers’ time and energy. And we needed them to concentrate fully on our product,” said Mitifiot.
Over half a year ago, “Wiener Wohnen”, Europe’s largest public-housing management service, transferred their company manual and their complete process and document management system onto a wiki platform. Here is a progress report.
“Introducing the wiki was a bit like doing a clear out,” says engineer Dietmar Milkovits. He is the head of the quality management department at “Wiener Wohnen“, a company full of tradition which can trace its roots back to the 1920s. As an agency of the municipal authorities of Vienna, “Wiener Wohnen” manages, renovates and operates about 220,000 council flats in 1,800 residential areas, making it the largest public-housing management service in Europe. During their work, about 750 employees are faced with a multitude of regulations: the Word document in which they used to be collected together was a good 600 pages long. Manipulating this data was thus very laborious, as was searching for regulations and using the connected documents required.
“More than just hype”
“The greatest challenge for the future was to make this mass of information understandable and transparent for our staff, and we wanted to make use of a well-known and proven tool,” said Milkovits. For this reason, in 2017, the company management decided to transfer this company manual and all the document and process management systems into a BlueSpice 3 wiki from Hallo Welt! GmbH, known as MAAS (this is short for the German word MitarbeiterInnenanleitungssystem meaning “Staff Instruction Manual”). Even the in-house intranet was replaced in the process, as though in passing, and since May 2018 “if I need anything, I look in MAAS.”
“A wiki is more than just hype. It is something stable, lending itself to extensions and being customised for future challenges,” says Milkovits, whose department looks after MAAS and operates the platform. He names the fundamental plus-points as the search function, the simple structure with many cross-linking possibilities, the function to print documents as PDFs, a pleasant layout and a rights system which is easy to adapt.
Experienced and creative authors already got to know the diagram editor draw.io a long time ago. It is based on a web application, already developed by the company JGraph as free software, and it is already compatible with diverse applications like, for example, Confluence.
draw.io is also available for MediaWiki, making is possible to display processes, elaborate flowcharts and much more and in many ways. This fulfils the desire of many wiki users to create and present clear graphics like flowcharts, process chains and decision trees, working collaboratively in the wiki.
We have had a look around at what interesting skins are available for MediaWiki and here we present those we think are the ten best.
But first, we will say a few words on MediaWiki and skinning in general. When comparing new MediaWiki skins, one always comes back to the following three themes:
- Navigation: Orientation towards mobile applications has significant consequences for the layout and design. It becomes “flatter”. The edit functions are in the background so as not to overload the small screen, and to reduce complexity. In this way, the pages appear more attractive on the web, and the “Mobile First” skins are more handsome, particularly for the reader. A power user wanting to work in the wiki will often find such skins problematic because they need extra clicks to access the functions they need.
- Semantic support: Many wikis use Semantic MediaWiki to work with metadata. Some skins integrate functions from the semantic extension into the skin or customise the layout in such a way that it does not break the optical design.
Let us now look at a few skins.