In previous posts we have talked about creating a ColdBox module from scratch ( ContentBox - Extending ContentBox 3 with your Own Custom Modules ), one file at a time, to see the minimum files required to make the module work. That was a great educational exercise, but lets look at another way to create a module, with CommandBox's ColdBox scaffholding commands. 

In our last post on Extending ContentBox 3 with your own Custom Modules we learned that you could build a custom ColdBox Modile with amazingly, just 2 files. You could paste in your legacy spaghetti code right into your default view, and it would work. Of course, we probably want to dress it up a little more, and add some more functionality, so lets look at the layout first.

We are so excited to bring about the release of ContentBox 3.0.0 Release Candidate to you today. It has been a monumentus milestone for us at Ortus Solutions as we have devoted almost a full year's worth of development, which has been unusual for our releases, but so worth it for ContentBox ColdFusion CMS.

This release candidate is a major release and with a completely rewritten administration module and with a collection of more than 150 tickets resolved. It has been a massive undertaking with some great results. We also are in the documentation process and our book is available as well now: contentbox.ortusbooks.com

Download ContentBox 3.0.0 RC Today!

What's New

We have created a very comprehensive what's new guide in our documentation book here: http://contentbox.ortusbooks.com/content/introduction/whats_new.html.

In a previous Post, we talked about extending ContentBox easily with modules, and showed you how you could just download a module, activate it and use it in minutes. In this post, we'll look at how to add Modules into your website, by building your own, and how to leverage Module Layouts.

Whether you have used ColdBox before or not, using Modules with ContentBox and ColdBox is fairly straightforward, in fact, I think its a great way to dip your toes into using both technologies. Working with Modules is like everything else in ColdBox, you work with conventions, but you have control. In this previous post, 'Modules Modules everywhere, Extending ContentBox', we show you how there are 4 locations for modules in ContentBox, and depending on how your module will work, you should choose the appropriate location. In this post, we're going to build a custom ColdBox module, which it not managed by ContentBox Admin's Module Manager.

In the last blog post, we talked about extending ContentBox with modules. With ContentBox being built on top of ColdBox, and integration with ForgeBox using CommandBox, there are a lot of modules ( and module locations), and how those modules interact isn't obvious at first. To be honest, with ContentBox 3, we only just decided to move the core contentbox modules, to provide clearer separation, and easier source control management... things are changing, so I thought this would be a great time to explain about the different type of module locations, and why you should use one over another.

We recently announced the availability of CommandBox 3.1.0 beta for testing.  We've make a screen cast also showing how to start Adobe, Lucee 5, and Railo servers which you can

As we begin our ramp up to the release of ContentBox 3 ColdFusion/Java CMS, here is a nice gallery of images of our new UI and major admin UI feature sets. Enjoy!