I do structure my code in a similar way. All the elements in a view, that have to deal with data, are treated as a separate view module. Each module will have it's own view, template, model and style.

The template for the main view, or the subview that can hold modules,is structured in such a way to have a .container to append my modules into.

The main view is usually rendered only once and behave as a proxy for the various modules relying to the events.

The great benefit form this approach is that it's quite easy to maintain/replace a single module as long as the events api don't change.