I have been using SOBI as a de facto CCK for ages. Works really well once you grasp the templating logic (which is well documented).

I have SOBI sites that display content based on user's Community Builder profiles, access level etc.
I have SOBI templates that conditionally display content based on category and other field values.
The options are endless.

The interface is in German. I can't see any option to change the language.

The concept is fantastic, and will, in time, save template developers a lot of guesswork and coding cycles.

The problem is that the code is intended to be displayed in a standard content area. However, it contains classes for menus and other items that appear in the module spaces.

In most templates, the styling of the module content (including menu modules) is inherited from the module.

So, displaying, for example, .mainlevel inside the content will not give the same visual result as displaying it inside a module space.

The solution would be to release the code as a component that displays in the mainbody, and a module that displays in a module space.