You can override BeforeRenderContentAreaItemStartTag.

protected override void BeforeRenderContentAreaItemStartTag(TagBuilder tagBuilder,
            ContentAreaItem contentAreaItem)
        {
            tagBuilder.Attributes.Add("id", id);
            base.BeforeRenderContentAreaItemStartTag(tagBuilder, contentAreaItem);
        }

Hi,

Great - is there anyway that I can prevent this outer div from being created?

Jon

The DIVs are required for the CMS experience and so are rendered in to the CMS editor to be consistent. As a note when using @Html.PropertyFor you can passing an object which dictates what the surrounding element and css classes should be e.g.

 @Html.PropertyFor(model => model.CurrentBlock.ClientLogos, new
{
    CustomTag = "ul",
    CssClass = "list",
    ChildrenCustomTagName = "li",
    ChildrenCssClass = "list_item"
})

CustomTag = The outer wrapper for the ContentArea
CssClass = Is the class on that outer wrapper
ChildrenCustomTagName = The tag for each block that's rendered out in the ContentArea
ChildrenCssClass = The css class for each block that's rendered out in the ContentArea

In your PropertyFor you could also add "hascontainer = false", this will remove the container div that wraps the content area.

Yes it is possible to remove it but personally we prefer not to. The DOM structure that is rendered out should be consistent against the front end and the back end preview IMO and though it's unlikely removal of a wrapper element would make the differerce keeping things consistent helps to mitigate issues

Hi,

I understand your concerns but this is for a Block inside a block and the extra divs mess up the designers markup.