If you ever wanted to modify ColdBricks or BugLog, but didn't understood how these application were constructed; or if you just want to see yet another way of developing CF applications, then this post may be for you.

I just posted some pages describing the framework I use for developing CF projects. It doesn't even has a proper name, I just call it "Core" due to its simplicity and its minimalistic nature. The basic principle of this framework, and the reason why I choose to use it instead of going with more traditional offerings, is that it only focuses on one thing and one thing only: provide a formal mechanism for going from one page to another and for invoking actions.

It doesn't do any fancy things, no complex request lifecycles, no sophisticated caching, no extensive API, none; however, it does provide enough extension points to which I can hook any functionality that I desire on a per-project basis. Basically the framework consists on a Front Controller implementation, a base event handler and a few conventions for directory structure and nomenclature.

Anyway, you can find the code and read more about this framework by going to the Projects section or by going directly here.

I realize I'm a bit late posting this now, but better late than never :) Last week I had the opportunity to do a presentation about ColdBricks to the Inland Empire's ColdFusion User Group (IECFUG). I want to thank Luis and all the IECFUG guys for inviting me and enduring my bad english and my blatant lack of PowerPoint/speaker skills; but hopefully they got to see a bit of ColdBricks in action and got a better idea of what ColdBricks brings to the ColdFusion's CMS market.

Here is a link to the recorded Adobe Connect presentation; also attached to this post are the presentation slides in PDF form. Feel free to take a look as it may answer some ColdBricks/HomePortals questions some people may have.

Again, thank you guys for the opportunity!