Binding objects on the Node is a smart way to store your page's relationships.  However making sure the bound objects are synced up with the document can be tricky and require some custom coding.  In this article i'll take a deep dive into the Staging Module, how it works, why Node binding is unique, and how to make your Node-to-Object bindings stage properly with your document.

Many of you have probably used the ControlExtender class to extend Kentico’s various User Interfaces, such as the Edit Binding template, or Object Listing.  Or maybe you've even used it to extend an inherited Form Control.  But how many realize that this ControlExtender can really extend any control?

In any Site or Entity, there are Many-to-One or Many-to-Many relationships.  Whether it be something as simple as “Multiple Banners to display on this page” to the more complex relationships that are needed to do custom ups (such as “Multiple states this dealer serves”).  The tricky part is, there are multiple ways to handle multiple relationships in Kentico, each with pros and cons.  By the end of this article however, you should be able to know which is the best thing for the situation!

Sometimes the best way to really understand how something works is to take it apart, see the nuts and bolts and really understand how something works, instead of just knowing that it works.  In this series, I want to show you all how Kentico does what it does.  Ultimately knowing how it works will lead you to develop and build your sites in a way that will be consistent with Kentico’s framework, and give you the power to leverage systems and resources that are inside of Kentico to do amazing things.  Many of my tools were built using this deeper knowledge of Kentico, and I hope it will help inspire better sites and better tools in the future!