New Qt Wiki Now Available

We are continuing our site unification to qt.io and we have now migrated the content from qt-project.org and today opened up the new Qt Wiki under qt.io. We invite all of you to start editing the new Qt Wiki under qt.io using the new MediaWiki implementation.

This is the first phase launch of the wiki under its new home, and therefore, you may find some things currently missing or not quite like they were before under qt-project.org. There are a variety of reasons for the latter. One main one is that our goal has been to make things easier than they have been before, providing wiki users a better editing experience, as well as more flexibility.

MediaWiki is is one of the standard wiki formats, which is a more familiar format to use for many than the wiki that has been used under qt-project.org.

MediaWiki benefits:

• Open source platform
• Active development of the platform
• A wide range of plugins to extend the wiki functionality
• Version control
• Better tools to follow and automate working on the wiki

What you will find different

In this new wiki, we will all be able to keep track of active editors directly in MediaWiki where it will be easier to follow who has edited what and when, as well have better control of versions.. Unfortunately, in this first phase, you will notice that the edit history of past articles has not been migrated over. As the old wiki system (Expression Engine) and MediaWiki are very different it has proven very difficult for the migration team to combine history from the old system into the new one. Our team will continue to look at this as we move along to see how we can best manage this. However, we do feel that manage wiki posts and edits from now and in the future will be much better, which outweighs in part the possible loss of past article history.

Using Qt Account for editing

The biggest change that the wiki introduction brings to you as a user, is that we are moving to using Qt Account as the identity and login service for the wiki.

Qt Account is in essence the gateway to what we are building as a new Qt developer portal. We have already started using it for commercial evaluators and customers in the past year. Currently, the Qt Account web portal provides users with license information, account and payment options. It is also provides access to The Qt Company Support Center where commercial users can submit support issues.

This is just the beginning, however. Our goal is to add valuable Qt information and resources, early access benefits, programs and the like into the Qt Account developer portal, making it your one-stop-shop for up-to-date Qt info and goodies.
I'll say something in big bold letters here:

When you start to edit, you will need to create a Qt Account. Please make sure to use the same email as you had on qt-project.org, that way you will get your nickname to come along with you.

Previously you logged into the wiki with your qt-project.org account details. Now you will be directed to the Qt Account login page.

If you do not yet have a Qt Account, you can create an account from the login page. If you have been active on qt-project.org, your username has been reserved for you, if you use the same e-mail address as on qt-project.org.

Our next item to migrate over is the Forums. When they move, they will also use Qt Account for login services. This is also the reason to use the same email on Qt Account as you did in qt-project.org. When the forums migrate under qt.io, your nickname and posts will move with you. However, please note that if you use a different email, we can't connect your nickname automatically.

Migrated content

The old wiki contained over 3000 pages, which were processed and migrated to the new wiki. Some of the pages are quite old, but we know people work on old platforms and with old software releases, so we didn't intentionally delete pages.

Some old pages were not migrated, but that decision was based on browsing data. If the page had very low, or no, visitors in the past year, it was deemed to be of low value and sadly left behind.

As with any migration there are some few issues. We are aware of challenges in at least the following:

• Image links are broken.
• Code blocks have been split into parts
• Special characters have been encoded as HTML character codes
• The way Category pages used to work is not the way MediaWiki works, so some Category pages contain double information

Therefore, we would be grateful if you could help us with the following:

Cleaning up the content

If you maintain or edit a page(s), please have a look next time when you edit to see whether there are issues on the page. Open the same page on the old wiki and take a look if something is missing or if it looks wrong, and please fix it.

We opened a wiki page where you can mark your page updated. Once you have looked at a page and edited it to an up-to-date state, please take a minute to add it tothe page list here. (I will be looking at the page edits and updating the page, but I do appreciate if you help me out there)

A helpful page that the wiki itself provides is the list of pages with broken links. If you can help out, you can go through the pages listed there and grab the content/links from the old wiki and upload it to the new wiki. We now have proper image uploading in the new wiki, a great new benefit. Also if you do not wish to upload images to the Qt Wiki, we enabled linking to external images, by just pasting the direct image link to the wiki text, this should be practical for logos and images which may change.

Also, if your favourite page did not make it to the new wiki due to very low visitor count in the past year, we encourage you to re-create the page on the new wiki.

Old wiki still available

The old wiki will stay open for reading until the end of March. That means that you have a month to make sure your favourite pages have not lost content in the move.

After that, the old wiki will be retired and redirects will be set in place.

We really appreciate your help in cleaning up the content and also welcome your feedback. It is lots of content, so we can’t do it alone. Thanks for your help and support!