Today we published our first “monthly” release. This means you can download a BlueSpice free version that reflects the recent stage of development. Please, be aware that the monthly release is for testing only! For productive use, please use releases that you will find directly in bluespice/files on sourceforge.
Amazon Web Services also offers the wiki engine BlueSpice now. Our American partner Orbitera provides BlueSpice in the free version in the Amazon Cloud. This means that you start your wiki with just a few clicks in the AWS Marketplace.
BlueSpice in the Marketplace of the Amazon Web Services
1. Call up the BlueSpice page in the Marketplace and – if you don´t have one already – create an account
2. Enter your contact information (please also read the customer agreement, which is linked there)
3. Choose between “OneClick-Launch” and “Manual Launch” and the appropriate entries (instance, server area etc.). Then accept the terms and conditions and start the system with the Launch button
4. You will receive a confirmation in the system and and a confirmation mail with further information. To login to the wiki, use „WikiSysop“ as user and your „Instance ID“ as password
5. There you go (user and admin manuel for BlueSpice can be found in our BlueSpice Helpdesk)
BlueSpice is – as usual – not restricted in the number of users and you get the full range of functionality of the free version.
The advantage of the Amazon Cloud
The costs are low, because it will be charged per hour, e.g. the full usage with the smallest instance and the server location in Frankfurt/Germany costs only 18,25 Dollar per month. All about the instances and which one fits best for your demands can be read here. With AWS you are free to choose the server location – nine are currently available worldwide, two of them in the EU and one of those in Frankfurt / Germany. The pricing for the AWS usage depends inter alia on the server location.
If you don´t know BlueSpice, you can also test it in a 30 days free trial. You don´t have to pay for BlueSpice in this period of time, but the costs for the AWS usage will be charged anyway (from 9,36 $ for 30 days). Furthermore, AWS offers a free tier. Please pay attention to the offer terms.
By the way, we recommend BlueSpice in the Amazon Cloud especially for start-ups and small businesses. Those will not be bothered with administrational tasks and the system is scalable for the possibly growing requirements. Moreover, the Amazon Web Services offer a special start-up program you can take a look at.
Background information about the Amazon Web Services
Next to some packages for the older version BlueSpice 2.22.x, you can now purchase our most popular packages for BlueSpice 2.23.x in the BlueSpice shop e.g.
- Teamwork: modul for reviews, approvals and workflows in a BlueSpice Wiki. Very important for quality assurance and in combination with the Reminder package you will keep articles up-to-date.
- Bookmaker: combine single articles to an online handbook with an automatically generated chapter navigation. Convert complete books, single chapters or pages into the PDF format and export it including all attached files from the articles, a cover and a clickable table of contents!
- WikiExplorer: browse, sort and filter content according to specific criteria. This is how you identify necessary tasks to administer content in the wiki.
- VisualDiff: compare article versions with colored highlighting in three different views. This is how you detect even smallest changes at first glance.
- Reminder: keep articles up-to-date, because the package reminds you after a certain time period to check the content and to revise it.
- PasteImage: insert and upload images by using Drag & Drop and Copy & Paste
Choose those functionalities you need and combine them to your business wiki.
Just purchase, dowload, install and get started – all by yourself!
Since the beginning of 2015 we welcome service specialist marillabax as a partner at Hallo Welt!
With marillabax we develop a wiki that is not only functionally, but also matches perfectly to the content-related needs of service and support employees. The result of this partnership is called „b-know“, and it is introduced on CeBIT 2015.
Ms. Bax explains:
When companies talk about service and support, they often mean their telephone or e-mail hotline or when the service technician is solving problems right away.
This is why service is still considered as a necessary but unpopular cost center. Successful companies are demonstrating how service can be more than a cost driver – namely a customer oriented department which supports competitive differentiation and adds value to the company.
To achieve this, a lot of companies buy elaborative consulting processes or expensive training initiatives.
b-know is an internal, wiki-based knowledge platform for all service and support processes and the necessary expertise knowledge. With the help of b-know, companies can reorganize their service and position themselves as customer oriented. All concerned parties have quick access to the expert knowledge, handbooks or FAQ’s they need – this is knowledge management at its best.
b-know is available for three industries: IT companies, IT organisations and mechanical engineering. For those industries you will get predefined templates and best practices as a basis, which you can adapt according your needs. New processes can be easily implemented. With the help of b-know companies can profile their service organization much more efficiently, structured and with a higher quality. As a result they save costs and gain additional sales in service and support.
b-know is based on the wiki platform BlueSpice developed by Hallo Welt! and enriched with special service handbooks and contents from marillabax.
More information on the BlueSpice website.
Today we released BlueSpice 2.23.1 on sourceforge. This is a patch release which you can download on sourceforge.net.
However we focused on bugfixing there are also some notable new features:
- Database: added experimental SQLite compatibility
- ExtensionInfo: Added link to Mediawiki version page
- Shoutbox: mentions of users with @ now possible and with ajax autocomplete
- SmartList: Added mode “whatlinkshere”
We set ourselves a couple of goals for 2015 and 2016 at our strategy meeting at the start of January. The most important ones relate to the MediaWiki distribution BlueSpice. We are making this successful product truly open source, offering new prospects for customers and partners.
100% subscription, one product, no more modules.
We have been developing the BlueSpice service model further and further over the last five years. In the future, BlueSpice will be made available in an integrated distribution. This means that the additional modules that require payment will be collected together in a single edition. Customers will thus be able to use all the modules from the outset. And, above all, you will gain tremendously from new developments as all our latest innovations will be contained in this distribution. This means that those new developments will always be available for subscribing customers whenever they want. This will save you the trouble of having to purchase them separately. Furthermore, as there will no longer be costs for each module, getting started with a professional solution will be significantly better value.
In parallel, there will still be the popular distribution BlueSpice free, which is downloaded 20,000 times a year, and used in over 130 countries and more than 20 languages. The free distribution contains the same scope of services as before, and remains the ideal first step in collaborative knowledge management.
Supporting growth and propagation
Why are we doing this? Firstly, because now we can. The major Linux distributions Red Hat and Suse have always been the examples we have followed: The best open source models for customers and developers are made in the Linux environment. However, moving away from project business and without outside capital, we are only now able to take this step.
Another reason is that we want to build the best open source wiki with new partners. This is only possible with extensive openness, technically and economically. The module system has been good for us and our customers. However, it is now blocking us from developing MediaWiki further into the most popular Wiki software for businesses. A module system will become too complex and opaque for customers and developers as we grow further. Also, we do not want to lose our way in administration, but rather to concentrate on development, integration and quality assurance.
Radically open source
For this reason too, we are radically opening the development to external developers. They can, from this year, contribute to all BlueSpice extensions, including those which had been previously unavailable. In this way, we open up the project for other developers, accelerate the programming and improve quality assurance.
Last but not least, BlueSpice should become more compatible with SemanticMediaWiki (SMW) so that customers and partners need no longer decide whether to choose SMW or BlueSpice. Using both is already a possibility. But, by the end of the year both worlds should interlock better.
It will be a busy and interesting year. The new version will already be ready for examination and ordering at Cebit. We have already set out the stages which will follow this. We will be moving towards an ecosystem, which is a familiar concept from other open source projects.
We look forward to all your support and cooperation.
Images and screenshots are an essential part of the content. The visualization of content supports the understanding and the motivation to spend time on the text. But how can I upload pictures in MediaWiki and how do I insert it in an article? I will show you three ways how to display the pictures in your article – one in an original MediaWiki and two in BlueSpice. Also I will give you some background information on images in MediaWiki. Continue Reading
The CategoryTree is a nice feature to list all categories and to give your users an overview of the topics in your wiki. But if you are using BlueSpice, it also provides a tag cloud for categories, which looks more fancy and can be configured and designed like the minimum font size, the increase factor, background or you can exclude categories from the tag cloud. To include the standard tag cloud in an article, just insert
at the position where it should be displayed.
The style definition is placed in the opening tag, e.g. <tagcloud style=”background:black;”> and the definition of the output can be written between the two tags, for example:
Read about the capabilities how to configure the tag cloud in our helpdesk article.
In BlueSpice and MediaWiki you can display the category system as a category tree. With the category tree, the user gets an insight into the structure and the yet available categories and articles. To insert a category tree into any wiki page please use the categorytree-tag and one of the existing categories from which the category tree shall start. In this example it is top level
There is also a special page for displaying the category tree – just call up “Special:CategoryTree”. This page provides a form where you can type in the category you want to be shown. You also have the choice whether all pages of the category, only the category (with subcategories if available) or all pages except the files should be shown.
For more detailed information and attributs for the categorytree-tag please have a look at mediawiki.org.
If you click on an image, which is uploaded and linked in your wiki – you will be redirected to the meta page of this file. Here you can discover a lot e.g.
- size of the image
- meta information of the image
- you can see on which pages the image is used
- and it is also possible to upload a new version of this file
Especially this last point is very important not only for images but also for files. Because if you have a new version of this file, which might be linked or used in several other pages, just click on „upload a new version“. Afterwards upload an „updated“ modification. Now, in every page this file is used, the new version will be shown – you don’t have to edit and update every page.
So you avoid spamming your wiki with too many files that might be named like „photo-account-manager“ „photo-account-manager-new“…. Just replace the original file with this functionality and you have replaced the file. Like you know it from the version history of articles, also the files have their own version history with the time a version has been uploaded and the user who did that. In the same way as you do it for articles, you can also rollback to a former version.