By default, field drivers will execute to build the shape for the field. If you want precise control over where this shape is rendered in the content shape template, just render a zone there and update your placement.info file to place the shape in that
zone. For example, given the following:
- Content type:
- Content Field:
- Local zone:
Then your content view could look like this:
And your placement.info like this:
<Place Fields__AlphaField="AlphaZone:0" />
This gives you control over where the field is rendered in your content template and have the field driver still execute.
Now this placement won't work outside the context of a content shape template, so if you ever needed to generate the shape(s) of some content field from an arbitrary location in code, you could leverage the
service that lives in
. That one lets you render individual fields and gives back a root shape, which you can render anywhere.