EditorModel Notifications
EditorModel notifications enable you to manipulate the model used by the backoffice before it is loaded into an editor. For example the SendingContentNotification
is published right before a content item is loaded into the backoffice for editing. It is therefore the perfect notification to use to set a default value for a particular property, or perhaps to hide a property/tab/Content App from a certain editor.
Usage
Example usage of the SendingContentNotification
- e.g. set the default PublishDate for a new NewsArticle to be today's Date:
Another example could be to set the default Member Group for a specific Member Type using SendingMemberNotification
:
Notifications
Display models
ContentItemDisplay
A model representing a content item to be displayed in the backoffice
TemplateAlias
Urls
AllowPreview - Determines whether previewing is allowed for this node, By default this is true but by using notifications developers can toggle this off for certain documents if there is nothing to preview
AllowedActions - The allowed 'actions' based on the user's permissions - Create, Update, Publish, Send to publish
IsBlueprint
Tabs - Defines the tabs containing display properties
Properties - properties based on the properties in the tabs collection
And more...
MediaItemDisplay
A model representing a media item to be displayed in the backoffice
Alias
Tabs - Defines the tabs containing display properties
Properties - properties based on the properties in the tabs collection
And more...
MemberDisplay
A model representing a member to be displayed in the backoffice
Username
Email
Tabs - Defines the tabs containing display properties
Properties - properties based on the properties in the tabs collection
And more...
Samples
The EditorModel notifications gives you a lot of options to customize the backoffice experience. You can find inspiration from the various samples provided below:
Last updated