Apr 9, 2012 at 9:17 PM
Edited Apr 9, 2012 at 9:19 PM
When your content item is being rendered using this template, all of the drivers will have been invoked and the shapes will have been created and added to the local zones of the content item (local zones in this case being Header, Meta, Content and Footer).
So, if one of the drivers created a shape called Parts_Common_Body which was placed in the Content zone, I assume you should be able to access and render it like this: @Display(Model.Content.Parts_Common_Body).
I haven't tried that though, so not sure if it works that way. What I did try before successfully is rearranging using just the local zone names, introducing new local zones as needed.
For example, let's say you wanted to rearrange the template so that a shape called TwitterHandle was rendered below the footer into a local zone called TwitterZone. That would be a 2-step process:
1. Update Placement.info to place a shape called TwitterHandle into a zone called TwitterZone.
2. Update the template to include a call to @Display(Model.TwitterZone).