Blog

We enjoyed bringing you tips for CommandBox and ContentBox last year for the 12 days of Christmas so much that we decided to do it again! This year, I'm happy to show you 12 different modules currently hosted on ForgeBox just waiting to make your life easier. So grab a hot drink and cozy up for the 12 Tips of (ForgeBox) Christmas.

Here are the slides from our presentation at CFCamp 2017 Day 2: ColdBox Hierarchical MVC. You can also find the source code for our demo here: https://github.com/lmajano/hmvc-presso-demo or you can use CommandBox to install it: box install lmajano/hmvc-presso-demo

The ColdBox Platform was the f...

Here are the slides from our presentation at CFCamp 2017 Day 1: A Tale of Legacy to Modernization.

Evolve or Die! How many times have they told you, You still coding in that?. Come to this session to discover the infamous land of legacy ColdFusion applications, their why and existence motivations. We will then discover how to finally evolve them and take them to the wonderful land of Modern ColdFus...

ColdBox Relax

ColdBox Relax Moldule v3.0 has been officially released, which includes native support for the OpenAPI/Swagger specification, in addition to a variety of feature upgrades and enhancements.

Version 3.0 makes the OpenAPI/Swagger specification the default documentation format for describing your APIs, while deprecating the Relax programmatic DSL ( scheduled EOL is v4.0 ). In addition, the release includes a complete overhaul of the user interface and Relax API Test Tool, to provide users with a seamless experience for documenting, viewing, testing and exporting in a variety of formats.

Ready for part 4? Yes, part 4. We continue our small walkthrough of building your own Admin Module in ContentBox 3. The last few blog posts we learned the minimum requirements for a new module, to be controlled from inside of ContentBox. Then we learned how to add a handler and a view, and how to access the module from the front end entry point, and through the ContentBox admin entrypoint. In the last blog post in this mini series, we looked at adding a Submenu for your module, to an existing top level Menu item inside of the ContentBox admin. This blog post is going to show you how to add your very own top level Menu item, give it an icon, set permissions, and then add Submenu items to access your module.

In previous posts, we learned how to create a module inside of ContentBox, and then we added a handler and view so we could view the module behind the security of the login, but having an admin module, without menu items, is fairly silly ( usually ). In this blog post, we'll learn how you can add Submenu items to existing menus, like the Modules Main Menu.

In our last post, we started building an Admin Module. This process isn't actually that difficult or long, but we have broken it into separate blog posts to make it easier to read each piece. We have built our basic ModuleConfig.cfc, now we need to build an event handler and view, so the default action when you hit your new module have something visible. Our module was called mySecrets, so lets move on.

In previous posts, we looked at how to extend ContentBox 3 with ColdBox Modules, installing from Forgebox with CommandBox, or creating your own. In this post, we're going to look at how you can create your own Admin Modules, add Menu Items into the Admin Interface, use ContentBox admin Users and Permissions instead of building your own security by extending ContentBox.

Friday, July 29th is the last of our webinars in our ContentBox Roadshow, which has been pumping out blog posts and webinars all throughout the month of July. In this last webinar I'm going to do a deep dive into modules, providing a walkthrough on how to create modules, and use them in your ContentBox site, hopefully that sounds interesting, and you'll join us.

Register now for free - get reminders and all of the recording links.

Modules are one of the key components of everything ContentBox. Adding a module into ContentBox is fairly simple, we have a few blog posts already outlining some of the different ways you can create them, but we have left out one very important piece so far ( we actually had a few questions about it on the CFML Slack Channel ), how do we theme our custom module output? Theming your custom module, so it uses the same theme/layout as the rest of your ContentBox site is now a reality. This is vital if you are going to be extending your site with your own modules, and you would hate for your module to be tightly coupled to the current theme, making it harder to change themes. This could be difficult, but luckily for you, its simple.