We would like pages created in experience manager to always have certain components: a title block and the seo component for example.
Is it possible for a prototype page to have 2 containers - the first repopulated with these mandatory components, and the second editable in the usual way. Ideally we would like this first container to be ‘locked’, in other words the content editor would be able to edit the properties of those preexisting components but not be able to remove them or add any other components to that container.
Is this possible? If not then is there an established approach to enforcing that certain editable components should be present?
Hello @kfox, it is not possible to lock components in place. This might be added in the future and there is some work being done to support it, but we don’t have a timeline when it will be available.
The closest thing you can do is to add a static component to the template of the experience page, which will be added to every page automatically and will be returned in the Page Model API response. Here is an example of the config:
The component parameters will not be editable by the editors but if this is a common component it might not be an issue, as it would always point to the same document. Or add some business logic in the component to return the desired documents/models.
