Bridge solutions

Many of us have found ourselves in this position. Your business or group make use of an online system, such as a forum, wiki, blog etc., which you then wish to augment or combine with some other system. How you go about doing that, of course, depends entirely on your goals and the systems you’re trying to use together. Design and styling are usually the least of those worries.

The problem which consistently presents itself when attempting such a combination is what to do with the userbase. Whilst this issue can sometimes be simply ignored, in the hope that only a small number of the users of one system will need access to the second, this isn’t always the case. When it comes to one userbase requiring access to two or more systems, the first question that needs to be answered is whether the user information should be shared, enabling a unified login procedure amongst other benefits. Requiring users to sign up to various different pieces of the puzzle is a time-consuming process, and one that many will find confusing and unnecessary. And since different online systems often have conflicting requirements when it comes to usernames and passwords, for example, this can also lead to more lost password checks and work for the system administrator. However, programming such functionality oneself certainly isn’t within the realms of the abilities of all of us, and keeping such modifications functioning across various systems and versions can be a painful procedure.