Yes, currently LIMB is all-sufficient. And that's no good, we never wanted to isolate LIMB!

In the nearest future we're planning to use LIMB as a glue around several excellent products as WACT, Propel, PEAR shipped with Simpletest test suites. That's why we need professional developers support.

The main aim of LIMB is to build scalable, extensible and easy-to-update websites(CMS). LIMB uses the following simple metaphor: "Every piece of information is an object". Every object has set of actions that user can perform, like display, edit, delete etc. LIMB uses internal access system to determine if the user is allowed to perform action or not. This access system is suitable for creating flexible access rules and maintaining documents flow.

LIMB is build with scalability in mind. This means that it is suitable for any kind of project from simple websites to corporate portals. Development of LIMB was conducted with modern principles of programming, like object oriented programming, design patterns, test-driven development.

Using site objects concept allows to develop/reuse/maintain different modules, such as articles, news, press releases, products catalogs and many others. LIMB offers user friendly interface to add/update information on the website. Administrator can use either back office to add/edit/delete information or manage information from front side using JIP (just in place) managing feature. JIP edition allows dramatically decrease time of learning the CMS and decrease administration time.

LIMB is WACT based which implies very powerfull and extendable templating system. By the way, you can see WACT template components of every page - click [Template source] link in the top right page corner.

Well, actually we use heavily modified version of WACT, only templating engine in fact.

OK :) JIP stands for Just In Place. In practice this allows you to handle CMS content directly in the front office! Actually, we don't have special administrating area in common sense. In terms of our metaphor we don't have a strict separation between front office and back office, it's just the matter of templates and access policy.

Once you're authorized to modify a site object you can see JIP control panel nearby(if it's provided by template).