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.
Would you like to learn more about BlueSpice and how to install a test system? Here is our step-by-step guide for an installation on Windows. At the same time, you can also find the installation steps on our Helpdesk.
When working with longer texts, it is not unusual to have to change a common term because it has been written incorrectly or because it is no longer up-to-date. Common word processing software packages like MS Word have a “search and replace” function so that you do not have to go through the whole text and change everything by hand.
There is a similar tool for MediaWiki users called ReplaceText. This is a small but powerful MediaWiki extension allowing you to search for specific combinations of characters, whether it is text, code or spaces, and to replace them both in wiki articles and in article titles. It is also possible to use complex algorithms which recognise patterns in the form of regular expressions so that you can undertake more sophisticated search-and-replace tasks.
Now even more user-friendly with impressive new features
We have great news: we are proud to announce the new BlueSpice release 2.27.2. After scarcely three months, we are already publishing the second release of the year.
Looking forward to the release of BlueSpice Version 3 in 2018, we are already working hard on many small adjustments, making BlueSpice even more user-friendly, so you can operate it more intuitively. This means that the new version already contains valuable features and improvements, so it is more convenient to use and working on it is more efficient.
Vienna! A city of music, culture and avant-garde. And, notably, the host of this year’s Wikimedia Hackathon, an annual tech event where roundabout 200 developers, maintainers and users of MediaWiki gathered to experiment, discuss, plan and, of course, enjoy the company of like-minded people. Naturally, BlueSpice, being the largest professional flavor of MediaWiki, was also represented in various ways, getting glimpses at the most recent turns in development, making connections among colleagues, and exchanging experiences and ideas. Continue Reading
In this two-part article, we give a detailed comparison of the wiki top dog MediaWiki and Confluence.
We already wrote a few words about MediaWiki and Confluence some years ago. At that time, we wrote about the main objections to MediaWiki.
That article is still worth reading and remains largely valid. Ultimately the key argument then was that the choice of tool did not depend only on features, but also on the concept behind the software. This is a timeless truth.
However, MediaWiki does not need to fear a direct feature comparison. Importantly, the enterprise distribution BlueSpice has already decided the feature question in my view. This can be seen on our newest internal feature-comparison table, published here and offered for free download:
Administering several individual wikis is technically intricate because all too often, a confusing “wiki chaos” develops, which is difficult to take care of. In this area there is already a concept which has proved itself: the wiki farm.
Several wikis can be created, archived or deleted quickly and easily by using a wiki farm. When creating wikis, the user has the option to create an empty wiki or to clone what is known as a “master wiki”. Such a master wiki can be already filled with content (e.g. handbooks), or contain files and configuration data, all of which can be transferred and supplied.
From a technical point of view, by using the farm concept, one can provide several wikis with just one wiki installation. The wiki software is only installed and saved once on the server and all the wikis use this installation together.
We have had an increasing number of enquiries from customers over the last few years for whom the best possible solution is provided by a wiki farm. Many have the problem that a single wiki is no longer sufficient, because they need to reflect the most differing topics, languages and permissions concepts. In such cases, we always recommend the use of several wikis via our wiki farm solution.
It is that time again: we are very pleased to announce the new BlueSpice release 2.27.1, and it is difficult to believe that this is only a patch release.
When we consider the new features, Version 2.27.1 is right at the forefront. The first release of this year focuses on the optimisation of usability and applications in quality management, alongside bug-fixes.