Hi, Elin,

One option you have is to use EPi blocks as "local blocks". When you are defining a block, you can set AvailableInEditMode to false, ie:

    [SiteContentType(
        GUID = "751FCE02-423B-4409-9CC5-744A37BAD015",
        AvailableInEditMode = false)]
    [SiteImageUrl]
    public class ImageBlock : SiteBlockData
    {
        [Display(
            GroupName = SystemTabNames.Content, 
            Order = 1)]
        [UIHint(UIHint.Image)]
        [Searchable(false)]
        public virtual Url ImageUrl { get; set; }

        [Display(
            GroupName = SystemTabNames.Content,
            Order = 2)]
        [CultureSpecific]
        public virtual string ImageAlt { get; set; }
    }

When you want it to be displayed on the page, you define a page property:

        [Display(
            GroupName = SystemTabNames.Content,
            Order = 300)]
        public virtual ImageBlock Image { get; set; }

So, you don't have a ContentArea, but an image block as a property.

This is a bit inflexible for your use, as I understand it, as it gives you exact number of properties on the page. However, it will have the same lifecycle as the page and will be present as a part of the page.

If you, however, need to add blocks to ContentArea only on one page, as you described, I don't think there is this "PageBlocks" functionality.

You can simulate it, by hooking to ContentCreated event and create a folder for each page and delete it on ContentDeleted by page name or so. It seems like a bit of overhead and also, as far as I can see you can't set access rights to the whole folder, only to each block, so you don't gain much and you still need to cover the pagename changes etc. So, basically, you help editors by creating their blocks folder inside a folder called, let's say, "Page blocks" and later cleaning it up for them by deleting this folder.

If you have a block that displays some page specific data, like price, name, etc and it's always on the same place, local block as described in the example is perfect, no need to overuse this new functionality of "shared blocks". If you don't have a specific structure, than I think you need to build up this functionality.

Hope this helps,

Marija

Pagefiles are not deleted when you delete the page though. But they do inherit the page's access rights.