Blog

Luis Majano

July 01, 2016

Spread the word


Share your thoughts

The new ContentBox 3 CMS editors have the capability to output dynamic settings and even tap in to the ColdBox MVC request context and private context collections. This will allow you to easily output from any of these sources using an easy to use markup.

Settings

Any setting stored in ContentBox can be output using the following markup: ${ setting_name }. This is a great way to create site-wide static settings that can be outputed in any editor.

ColdBox Request Collection

Since ContentBox CMS is built on a solid MVC foundation via ColdBox, you can easily tap into the request structures that power a request. The request collection or usually referred to as rc is available in any editor using the following markup: ${ rc:key_name }. This will allow you to have access to incoming URL and FORM parameters or internal application variables.

ColdBox Private Request Collection

The private request collection or usually referred to as prc is available in any editor using the following markup: ${ prc:key_name }. This will allow you to have access to private dynamic variables that can be set by the ColdBox application eco-system.


You now have more choices for integration with the ColdBox application eco-system. Have fun!

Add Your Comment

Recent Entries

Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern

Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern

Learning a new AI API usually means jumping between scattered documentation pages, guessing at imports, and copy-pasting code that may or may not still work. We wanted something better for BoxLang AI, so we built the BoxLang AI Explorer: a local, browser-based catalog of runnable BoxLang AI examples, organized by category and difficulty, each with guidance, source code, and sample output.

Luis Majano
Luis Majano
August 14, 2026
Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM

Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM

If you've spent years in Spring Boot, Micronaut, or Jakarta EE, "web framework" usually means a servlet container, an embedded Tomcat or Netty, a build step, and a fat jar before anything answers a request. What if you could skip all of that and still be on the JVM?

Luis Majano
Luis Majano
August 12, 2026