meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sap_hybris_commerce:cms_cockpit_wcms:wcms-key-concepts-and-features [2020/02/05 16:43] – Removal of roles and customizations levels Antonio Robirosa | sap_hybris_commerce:cms_cockpit_wcms:wcms-key-concepts-and-features [2020/02/11 20:25] (current) – [Key features of smartEdit] Antonio Robirosa | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| It enables the customer to manage pages and content of multichannel-websites like banners, text, images, product carousels and other components. Marketing campaigns may be integrated in the website by setting the conditions for the visibility of components and pages. | It enables the customer to manage pages and content of multichannel-websites like banners, text, images, product carousels and other components. Marketing campaigns may be integrated in the website by setting the conditions for the visibility of components and pages. | ||
| - | ---- | + | |
| + | <WRAP center round important 100%> | ||
| + | SmartEdit fully replaced the WCMS Cockpit((deprecated since hybris 6.7)) since SAP hybris 1905. [[https:// | ||
| + | </ | ||
| ===== Key CMS Concepts ===== | ===== Key CMS Concepts ===== | ||
| Line 18: | Line 22: | ||
| * **Navigation Node:** It is a page, url or media which could be directly accessed by the visitors of your website. | * **Navigation Node:** It is a page, url or media which could be directly accessed by the visitors of your website. | ||
| * **Component Type Group:** Set of components types allowed in a content slot | * **Component Type Group:** Set of components types allowed in a content slot | ||
| + | |||
| + | ==== Data Model ==== | ||
| + | * [[https:// | ||
| + | * All the CMS Types extend from **CMSItem or CMSRelation**. Both superclasses are content catalog aware. | ||
| + | * A page, component, slot or template can be used in many CMS Sites. They would be assigned to the same content catalogue and this catalogue is shared among many CMS Sites. | ||
| ===== Key CMS Features ===== | ===== Key CMS Features ===== | ||
| Line 27: | Line 36: | ||
| * **Deep linking** of products, pages, categories, etc. using custom URLs. | * **Deep linking** of products, pages, categories, etc. using custom URLs. | ||
| * Based on the following extensions: | * Based on the following extensions: | ||
| - | * cms2 | + | * cms2: Core hybris types of the WCMS |
| * cms2lib: Reusable components. Out-of-the box comes with the banner, product detail, product list and rotating image components. | * cms2lib: Reusable components. Out-of-the box comes with the banner, product detail, product list and rotating image components. | ||
| * cmsbackoffice: | * cmsbackoffice: | ||
| - | * cmsfacades: | + | * cmsfacades: |
| - | * cmsoccaddon | + | * cmsoccaddon: Provides a REST API to query page and component information. It should be used by the frontend. |
| - | * cmswebservices | + | * cmswebservices: Provides a REST API to query and manipulate content catalogue versions, CMS components, CMS medias, navigation nodes, languages of the websites, page, page types, content slots, CMS restrictions and synchronize CMS items. This REST API must be used to access the CMS data from other systems. |
| - | * previewwebservices | + | * previewwebservices: Used by the Live Preview to send the preview parameters to the frontend |
| ===== CMS Restrictions ===== | ===== CMS Restrictions ===== | ||
| * They control the **visibility** from components and pages. | * They control the **visibility** from components and pages. | ||
| Line 45: | Line 54: | ||
| DefaultCMSPageSlotComponentService.getCMSComponentsForContentSlot(..) and | DefaultCMSPageSlotComponentService.getCMSComponentsForContentSlot(..) and | ||
| flattenComponentContainerHierarchy(..) which only return visible components. | flattenComponentContainerHierarchy(..) which only return visible components. | ||
| - | ==== Data Model ==== | ||
| - | * [[https:// | ||
| - | * All the CMS Types extend from **CMSItem or CMSRelation**. Both superclasses are content catalog aware. | ||
| - | * A page, component, slot or template can be used in many CMS Sites. They would be assigned to the same content catalog and this catalog is shared among many CMS Sites. | ||
| ===== Key features of smartEdit ==== | ===== Key features of smartEdit ==== | ||
| + | {{ : | ||
| + | * [[https:// | ||
| * **Pages and Storefront** | * **Pages and Storefront** | ||
| * In-place WYSIWYG editing of pages and components | * In-place WYSIWYG editing of pages and components | ||
| * Versioning of pages | * Versioning of pages | ||
| * Synchronization of pages and management of the edit status of pages | * Synchronization of pages and management of the edit status of pages | ||
| - | + | * A preview context with a content catalogue version, a language, an arbitrary time and product catalogue may be used to preview the site and test restrictions | |
| - | {{ : | + | |
| - | + | ||
| - | * A preview context with a content catalogue version, a language, an arbitrary time and product catalogue may be used to preview the site and test restrictions | + | |
| * This information is passed in the url to the frontend. The CMSSiteFilter gets the id of the previewTicket and loads the data. | * This information is passed in the url to the frontend. The CMSSiteFilter gets the id of the previewTicket and loads the data. | ||
| - | * The cms:body and cms:element JSP tags contain javascript code to enable | + | * The frontend must implement |
| * **Navigation**: | * **Navigation**: | ||
| - | FIXME Can nodes be synched inside SmartEdit? | + | |
| - | FIXME Check if the wizards can be customized | + | |
| ===== Further Reading ===== | ===== Further Reading ===== | ||
| - | [[https:// | + | [[https:// |
| + | [[sap_hybris_commerce: | ||
| + | [[https:// | ||
| + | [[https:// | ||
| ===== Pitfalls ===== | ===== Pitfalls ===== | ||
| * Page templates must be created in the backoffice cockpit or using Impex | * Page templates must be created in the backoffice cockpit or using Impex | ||
| * To change the usage of the attributes name and uid is a difficult and long task because of the way the wizards use them. | * To change the usage of the attributes name and uid is a difficult and long task because of the way the wizards use them. | ||
| - | ==== CMS Cockpit((deprecated on SAP hybris | + | ==== SmartEdit ===== |
| - | * **The popup editor can't open another popup.** This means that you if you have a complex tree of components, the editors in the WCMS cockpit support four levels of components (slot, component container in the component editor, child component in the component editor, another component in popup editor). | + | * There currently no way to synchronize the navigation nodes inside SmartEdit |
| + | * Wizards for for the creation or selection of items with decision, mandatory, reference and type selector pages can't be created. This was a feature of the deprecated WCMS cockpit. | ||
| + | |||
| + | |||
| + | ==== Deprecated WCMS cockpit | ||
| + | * **The popup editor can't open another popup.** This means that you if you have a complex tree of components, the editors in the WCMS cockpit support four levels of components (slot, component container in the component editor, child component in the component editor, another component in popup editor). | ||
| FIXME Test this case on SmartEdit | FIXME Test this case on SmartEdit | ||