Brix CMS for Wicket

The main problem with almost all the CMS out there is that they are optimized for building websites. They are not optimized for building web-apps. In fact, for some of the most popular ones (e.g. Drupal, Joomla), they require software engineers to commit to huge compromises when they want to build a web-app. Why should software engineers have to compromise just because they need CMS functionality? That's a question I've always been asking.

My favorite web application development framework is Apache Wicket, which allows web applications to be built in a truly object oriented manner, and all I need for some of my projects is to be able to build a web-application with some CMS capabilities without having to go slumming with PHP or do some crazy hacks to integrate a CMS with the web-app. I'm just so sick of all the "our way or the highway" (The "Drupal Way" *rolleyes*) approach to developing web-app functionality into CMSes.

Brix CMS claims which I like and find promising:

1. "Most CMS are for building web sites. Brix CMS is for building web applications."
2. "BRIX is not a standalone CMS, but rather a CMS framework which allows for easy integration of CMS functionality into existing Wicket-based applications."

Obviously these claims will have to be examined, something which I will be doing soon:

Links:

1. http://blog.dreamcss.com/content-management-system/brix-apache-wicket-based-cms-framework/
2. https://github.com/brix-cms/brix-cms
3. https://github.com/brix-cms/brix-cms/wiki