Components templates and the component service
Component templates already exist within Content Management.
The Component Service is an evolution of this with additional functionality.
The Component Service
The Component Service sits outside of Content Management, allowing developers to deploy, and stakeholders to preview, components without using the CMS.
The Add a component side panel on a standard page displays the following components:
-
Built-in components under the Basic header.
-
Component templates under the Custom header.
-
Components from the Component Service under the Component set name.
On a standard page asset, you can use any combination of the core components and DXP enablers, the component templates, or the Component Service components.
Component templates cannot be used on content page assets.
Component templates
Current component template assets are not being deprecated or removed.
They continue to function on standard pages.
Component templates cannot be used on content pages.
Consequently, migrating from standard pages to content pages also involves migrating from component templates to the component service.
Component templates and the component service can be used together on standard pages, however.
Therefore, migrating from component templates to the component service can be done before migrating from standard pages to content pages.