Design Approach to Marionette Behaviors
<p>We initially approached Marionette Behaviors as a tool to build modular components for our views but that's the thing -  only to create behaviors for re-usability. There are still specific behaviors I would like to build in order to separate the view from event driven behaviors however, they would be considered too specific ie. events driven behaviors on a form that interacts with a complex template with complex business logic.</p>

<p>But looking past my situation, is building only modular behaviors the right path? Apparently, Marionette gives the users the freedom to use behaviors as they see fit but should we build a behavior even if its used only once?</p>