Extension types in the Add-ons manifest
A list of Extension types, that is, valid values for the JSON type property of an Extension in the Add-ons package manifest file, manifest.json. The Extension type determines which extension point your Extension will interact with.
- Content Manager: Application Data Configuration Extension
With an Application Data Configuration Extension (type =CMApplicationDataConfiguration), you can create one or more XML configuration files containing configuration for your custom application data. - Content Manager: Custom Resolver Extension
You can create one or more Custom Resolver Extensions (type =CMResolver) to add your own custom resolving functionality to the built-in resolving provided by the Publisher. - Content Manager: Event Handler
You can create an Event Handler (type =CMEventHandler) and extend the Content Manager Event System. Your Event Handler responds to specific types of events that occur in Content Manager, such as deleting an item or saving changes, for example, as captured by the Event System. You include the .NET assembly containing your Event Handler in an Add-on package and configure its location in the manifest file. - Content Manager: Experience Space Extension
You can deploy extensions to the Experience Space GUI (type =ExperienceSpaceExtension) to tailor the Experience Space user interface to reflect your unique editorial processes and to maximize productivity for authors and editors. - Content Manager: UI Editor (Classic)
An Editor represents a complete GUI extension to Content Manager's Classic user interface (Content Manager Explorer and Experience Manager). This can be anything from a new button in an existing GUI or a completely new user interface built from scratch. The extension point for an Editor is calledUIEditor. - Content Manager: UI Model (Classic)
A Model represents a data model for a GUI extension to Content Manager's Classic user interface (Content Manager Explorer and Experience Manager). The extension point for a Model is calledUIModel. - Connector Extension
An Extension withConnectoras the Extension type extends the Content Service and External Content Library to add integration with an external source of content. The extension point for this is calledConnector. - Content Delivery: Content Deployer Extension
With a Content Deployer ExtensionCDDeployerExtension, you can extend the Content Delivery feature that receives incoming content from Content Manager and stores it in the Content Data Store. You can add to this functionality by, for example, running some kind of processing engine over the published content to extract relevant information such as keywords. - Content Delivery: GraphQL Schema Extension
Extend the default GraphQL Schema with a GraphQL Schema Extension (type =CDGraphQLSchemaExtension) and enable querying of custom content originating from a third-party source. This type of Extension is typically developed alongside a Model Transformer Extension, which actually fetches and transforms the content from the third-party source. - Content Delivery: Mergeable Configuration Extension
Use a Mergeable Configuration Extension (type =CDMergeableConfigurationExtension) to merge your own custom Content Delivery configuration with a corresponding default Content Delivery configuration file. Note that you don't need to use this Extension to addPipelineelements to the Content Deployer configuration file, deployer-conf.xml: you can already do so in the Content Deployer Extension. - Content Delivery: Model Transformer Extension
Configure a Data Model Transformer Extension (type =CDModelTransformerExtension) for the Content Service to transform fetched custom data from the Content Data Store. Typically, this kind of Extension is accompanied by a GraphQL Schema Extension to make the fetched and transformed data queryable through GraphQL queries.