I hope you are enjoying Ortus Solutions' ContentBox Roadshow so far. We're had one free webinar already, and a few blog posts, with plenty more to come. Today I'm going to talk about modules a little more. I mentioned them in my "What's New with ContentBox" presentation ( you can read more about it and watch the recording here ), but you might not have known, I got excited about ContentBox and all of the modules before the roadshow even started.
FREE Live Webinars
July 2016 | Every Friday at 11 am Central
We are incredibly excited at Ortus Solutions to be celebrating the 10 year anniversary of the release of ColdBox. It has been an incredibly journey and learning experience. Here is a little video to commemorate this milestone and describe better how we feel after 10 years of hard work and over 57 releases!
We are very excited today to formally announce the availability of ColdBox Elixir, coldbox/elixir. ColdBox Elixir provides a clean, fluent API for defining basic Gulp tasks for your ColdBox applications.
We wanted to provide ColdBox developers and easy way to approach an asset pipeline and task executor. The elixir project accomplished this and we have extended it to match the conventions used in ColdBox but also took it a step further to make it compatible with TestBox and CommandBox. This way you can have a full task runner available to you than can integrate with CommandBox recipes, package management, command execution and also TestBox executions.
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
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.