Container component - column policy

[VjekoSulentic]

We should adjust our container component to include the columns as a container type on which the policies can then be defined separately.

[gabrielwalt]

On the template editor, the email container component should be able to be unlocked at two levels:

• Either on the container:
  • On the template, the allowed components can then be configured, and this configuration then applies to all its columns.
  • On the template, the policies of each allowed component can then be configured, which then applies to all columns.
  • On the template, ounce the container has been unlocked, the policy of the individual columns cannot be configured more specifically.
  • On the resulting pages, the container is then a mandatory component that authors cannot remove but still can edit, like for e.g. change how many columns it has.
• Or on individual columns:
  • On the template, the allowed components can then be configured specifically to that individual column.
  • On the template, the policies of each allowed component can then be configured specifically to that individual column.
  • On the resulting pages, the container is then a mandatory component that authors cannot edit. To the columns that have been edited in the template, authors can only can insert the allowed components, as configured in the policy of each column.

[VjekoSulentic]

Added initial policies for each of the three columns of the container component.
The same approach can be used by developers in solutions which are proxying the email container component.

If the template editors need to edit the template policy for specific column, they can lock the container component on the editor, which will then give them access to unlocked column components.
They can change the policy for each column and then unlock the container component again.