Browse Category by MediaWiki

BlueSpice, MediaWiki and the outlook for libre knowledge

BlueSpice for MediaWiki is a commercial project. The plan to develop an enterprise distribution for MediaWiki was driven by the aim of making a profit and creating jobs.

Nevertheless, it is time to say a few words about other aspects of the BlueSpice project. For BlueSpice is also a project that should push along the development of MediaWiki and the construction of free knowledge platforms on the Web.

I will consider three aspects here.

1. Wikis are society’s future repositories of knowledge and BlueSpice should make a contribution

An open society needs a place to gather knowledge, to organise it and to map it. In the future we will find society’s memory on the Web. Political Wikis show how important this memory is. Lobbypedia and its English predecessor powerbase from spinwatch are two good examples. NGOs collect information there about lobbyists, politicians and organisations making networks and strategies transparent and making the information available for research. Think Tank Network Research is a similar research project. I could go on and on with this list.

It is not just in politics that we need a central platform on the net where we can collect free knowledge centred on particular themes, but also areas like leisure, culture, sport, business and health. Regional and city wikis have already become the trailblazers here.

And there will be wikis which save content from other websites so that it can be further developed and worked upon.

There is no system better suited to such tasks as MediaWiki software. And MediaWiki has a special role because the software is available under a free licence and, being an integral part of the Wikimedia projects Wikipedia, Wikimedia Commons and Wiktionary, has the best outlook for development.

So that the operators of wikis can carry out their work with significantly less technical personnel and budget than Wikipedia, they need MediaWikis which can be expanded with inexpensive software packages fitting their needs.

So BlueSpice publishes its free version, not only for marketing purposes, but also so the software can make life easier for those involved in such projects.

2. MediaWiki is becoming a software framework and BlueSpice is a step on that road

More and more projects are starting using MediaWiki as a basis and putting further pieces of software on top. With MediaWiki, you can operate an online encyclopaedia. However, if you does not want to do that, you will need another user interface but you can continue to use the basic structure. This means that the basic system stays the same, MediaWiki, delivering authentication, rights management and categorisation. On top of this comes, for example, BlueSpice, making the system into a company wiki.

A couple of further examples:

  • Translatewiki extends MediaWiki into a collaborative translation management system.
  • There is an initiative in Germany, which builds on MediaWiki to safeguard the basic provisions for media. For this, MediaWiki needs a additional layer which can provide and manage films.
  • At Hallo Welt! we are doing something similar, working with the project LinkTank, a collaborative link directory, and with Musikwiki, a place for collecting musical score. In one project one edits music scores and on the other collects links related to a theme.
  • Wikimedia Commons also only needed to further develop the user interface to make a really attractive platform for a picture library beyond Wikipedia.

MediaWiki has a very special role in open source applications. The software is completely unrivalled as a framework for “collecting open knowledge”. WordPress would be comparable as a basis for communication and social networking solutions.

Thus, we see BlueSpice as one of many steps in the development of MediaWiki into a general framework for free knowledge. This process tests out new possibilities and builds up knowledge which can be useful for other projects.

3. MediaWiki needs an ecosystem and BlueSpice is a contribution to this

The most successful and innovative open source software projects have developed a vibrant ecosystem that putting together both non-profit and for-profit agents, each driving the development in different ways. A large circle of developers is created. The software can assert itself over propitiatory systems and even force them back.

MediaWiki has a very underdeveloped ecosystem compared to other software projects. This means that commercial development in the whole project can be put to good use. Many projects need, for example, a user management system in the backend. In this form, this is not necessary or possible for Wikipedia. All others, however, need exactly this extension. Now these were firstly developed for companies and are now available as free software. I could add many further examples from the development of BlueSpice.

We need, therefore, better general conditions and more energy for a MediaWiki ecosystem. It is true that the Wikimedia Foundation has recently invested more money and energy in software development. However, this will not be enough on its own. Even for sister-projects like Wikimedia Commons, the capabilities necessary are often not there. For this reason, the focus is on third party developers and one wants to support the development of a MediaWiki ecosystem.

This is a step in the right direction. The new initiatives from the Wikimedia Foundation, to develop MediaWiki further and to create a new economic setting is bringing new energy to the whole project. This will open up new vistas to free knowledge projects.

Here, BlueSpice is just one cog in the machine. But it can and will be the basis for completely new types of project.

The decision, in the end, will be made by the users and the community.

MediaWiki tutorial – Where can I find helpful information?

www.wikimatrix.org: Comparing wiki software

Vergleich von BlueSpice, Confluence und MediaWiki
Comparison of BlueSpice, Confluence and MediaWiki

If you would like compare MediaWiki with other wikis, you can look at the masks at wikimatrix.org.
You can find innumerable small wikis and also the larger, more well known ones. Both open source and proprietary wikis are listed.
As well as the features of the wiki one also has suggestions for service providers which offer support for the system. A list of other wiki systems comparable to that chosen are also displayed. As far as features go, it should be said that only the standard functions of the software are considered. If a system can do more than this is not displayed on Wikimatrix.

www.mediawiki.org: All about MediaWiki

This is the central page for all questions about the software. The site is in English and many articles are translated into other languages too. A quick tip: start by clicking on “your language” in the box at the bottom.

Mediawiki.org organises the information about the software MediaWiki into three areas:

  • Users: How do I use a MediaWiki? How do I write something in it?
  • Administration: How do I install MediaWiki? Which extensions are there? How can I adapt the system further?
  • Developers: Developers handbook and further help assistance

Once can find a user handbook and a technical handbook here too. Of course, there is a MediaWiki hand book in the Wikibooks project.

Wikipedia’s help page: Help on working in and with MediaWiki

As Wikipedia is the biggest and most famous project in the world, it has innumerable help pages available. Many users look here first as the articles are very well written. And also because mediawiki.org can be too technical or simply too “English”.

However: MediaWiki is the software on which Wikipedia is based, not Wikipedia itself. People often ask us: I have seen this in Wikipedia, where is that in my MediaWiki? The answer is: Wikipedia uses a specially adapted form of MediaWiki with specific extensions, integrated templates and configurations, which do not come automatically with the standard software. For this reason there may be differences.

The help pages from Wikipedia give an overview of all sorts of different topics. The pages are organised under “Help:”, which is called a namespace. This means that everything which has something to do with the topic “help” is found in this “space”.

  • Help on editing: How do I add a new page? How do I format the text? How do I add pictures? and much much more.
  • Using templates: Text blocks like info boxes to copy and paste and further tips.
  • Guidelines for good articles and basic principles – really worth reading.
  • Explanation of the software’s features, like for example namespaces.

Anyone who is fairly new should definitely start by clicking on the links you can find there. This takes you to the relevant portal where you can find many more important links to take you further.

YouTube: Screencasts for differing themes (the good ones are generally in English)

This introductory video is very good: What is MediaWiki?

On you tube you can find some introductory videos. However, these are often about installation. Like this one for example:

There are also some videos about working in MediaWiki – for example creating and editing with templates. There are many tutorials on various themes in English; for example the youtube user “Kristinpedia” has posted many.

Help for BlueSpice for MediaWiki

And last but not least, advice on BlueSpice for MediaWiki. As this distribution is set up on MediaWiki, all MediaWiki help is also valid for BlueSpice. If one has BlueSpice installed, one can see some changes which affect how the wiki handles. A great deal is simplified, for example uploading and inserting images. You can find your first help desk for BlueSpice at hilfe.blue-spice.org. As far as the free support for BlueSpice is concerned, we are still very much at the start. Thus for all who want to spread their knowledge: Join in and make articles, videos, screencasts and so on about working with BlueSpice.

PDF Export for MediaWiki

There are lots of possibilities for exporting MediaWiki articles as PDF documents.
Some further developments I want to outline here:

Wiki as the central source of knowledge

There are many good reasons for supplying a Wiki with a PDF export facility:

  • Extracts, logs, check lists or short descriptions may be needed on paper or may need to be sent via e-mail.
  • Whole topics or areas of knowledge may need to be made into brochures or books so they can be available, for example, on the website for users, service providers and partners, or offline for field staff.
  • Intermediary versions of handbooks might need to be kept, for example, to supplement contracts and invitations to tender or as documents giving a basis for auditing.

Using a wiki as a central medium here has the obvious advantage that rather than having innumerable PDF documents flying around, the texts can be developed in the wiki and kept up to date. The PDF export function will then give out the most up to date version.

How to create my first PDF export

If you want to add a PDF export facility to a wiki, first work out whether you just want the readers to be able to export individual articles as PDFs or if you want to give them the opportunity to put together a selection of articles in a “book”. The second option is a more technologically complex.

Furthermore, decide whether the firm’s CI should be used and how far you want to go with providing the user templates. Will the PDFs always have the same layout? Do they have, for example, the same coversheet? As soon as this is decided you can get started.

MediaWiki has no PDF export facility in the standard software. However, you can find a whole set of PDF extensions at MediaWiki.org with individual installation instructions: Continue Reading

MediaWiki vs. Confluence? Not a question of features

When businesses want to make use of professional wiki software, they come quickly to the question of whether they should choose MediaWiki or Confluence. Confluence is a wiki specially developed for the needs of businesses. The concept for MediaWiki is, on the other hand, for the huge online encyclopaedia Wikipedia. Having more than 750,000 downloads per year, MediaWiki has a decisive lead as the standard wiki software, in business too.

Fans of Confluence used to complain that MediaWiki was not really suitable for businesses. And one can find serious comparative studies which completely ignore the possibility to extend and adapt MediaWiki. However, the extendibility and adaptability of MediaWiki is an essential feature of the software. The project page MediaWiki.org alone lists more than 1,800 extensions.
And, since the publication of BlueSpice, there is a completely free enterprise distribution for commercial users, which can be extended to suit individual needs via modules.

To show how MediaWiki really is a solution for business, I have collected together the most common objections to MediaWiki and I comment on them below. Continue Reading

MediaWiki Skins – A visual feast

The structure and design of most wikis looks like Wikipedia, which is now over ten years old. It does not have to be like this. If you want to give your wiki a different look, you need to use a different skin. Changing the appearance of a MediaWiki (and also BlueSpice) installation also changes how it handles. I have collected together a few tips and ideas here and I also explain the steps planned for the BlueSpice skin.

Update 2017: Please see also the recent article The top 10 MedaWiki skins.

MediaWiki is becoming more diverse

Look at these wikimedia projects which all use the current “Vector” skin. Vector was developed in 2009 for MediaWiki 1.16+ as part of the Wikipedia Usability Initiative and improves on its predecessor Monobook, giving a clearer presentation and better usability. In addition, some special functions can be downloaded as vector extensions.

MediaWiki is already working on the further development of the standard skins. The next stage, the Athena skin, will support mobile devices, amongst other things. You can get a visual impression of Athena here. Continue Reading

  • 1
  • 2