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 [2019/08/27 10:15] – [Key Features] 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 1: | Line 1: | ||
| - | ====== WCMS - Key concepts and features ====== | + | ====== WCMS and SmartEdit |
| 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. | ||
| - | ---- | ||
| - | ===== Key Concepts ===== | + | <WRAP center round important 100%> |
| + | SmartEdit fully replaced the WCMS Cockpit((deprecated since hybris 6.7)) since SAP hybris 1905. [[https:// | ||
| + | </ | ||
| + | |||
| + | |||
| + | ===== Key CMS Concepts ===== | ||
| - | * **CMS Component: | + | * **CMS Component: |
| * **Slot:** Area in the page to render a group of components | * **Slot:** Area in the page to render a group of components | ||
| * **Restrictions: | * **Restrictions: | ||
| - | * **Page Template:** Defines the number and name of slots of a page. It may contain slots with prefilled | + | * **Page Template:** Defines the number and name of slots of a page. It may contain slots with pre-filled |
| * While it defines the slots, **it doesn' | * While it defines the slots, **it doesn' | ||
| * In other words, there isn't any JSP associated to the page template. Each page has a JSP and all the JSPs of the pages belonging to a template **could have the same layout.** | * In other words, there isn't any JSP associated to the page template. Each page has a JSP and all the JSPs of the pages belonging to a template **could have the same layout.** | ||
| * **The final positioning of the slots on the page is done in the JSP of the page.** | * **The final positioning of the slots on the page is done in the JSP of the page.** | ||
| - | * By default there are two content | + | * By default there are two content |
| - | * **Content | + | * **Content |
| - | * **Synchronization: | + | * **Synchronization: |
| - | * **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 | ||
| - | * **Roles** | ||
| - | * **CMS Designer:** creates pages and manages content | ||
| - | * **CMS Content Manager:** approves the content created by the CMS designers and writes the translations | ||
| - | * **CMS Publisher: | ||
| - | * Each role has a list of tasks | ||
| - | * **Customization levels** | ||
| - | * **Easy**: Use XML configuration and user groups to change the appearance of the cockpit | ||
| - | * **Medium**: Based on the existing CMS cockpit. Add an editor, custom section or column in the editors, add a perspective or customize the storing mechanism | ||
| - | * **Expert**: Uses the cockpit independently of the CMS cockpit. Customize the type service, implement a new perspective which customizes all the areas, new wizard type, new cockpit application, | ||
| - | ===== Key Features ===== | + | ==== 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 ===== | ||
| * Supports different types of content | * Supports different types of content | ||
| * **dynamic**: | * **dynamic**: | ||
| Line 34: | Line 34: | ||
| * **structured**: | * **structured**: | ||
| * **unstructured**: | * **unstructured**: | ||
| - | |||
| - | |||
| - | <WRAP center round important 100%> | ||
| - | The following section refers to the WCMS Cockpit. This extension will be replaced by SmartEdit and is deprecated since SAP Hybris 6.7. SmartEdit will support the old features and new ones. | ||
| - | </ | ||
| - | * **Cockpit** | ||
| - | * **Perspectives**: | ||
| - | * **Live Edit**: Enables to browse the website, preview the last changes and edit the content on the fly | ||
| - | * A preview context with a user, usergroup, fake time, a language 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. | ||
| - | * The cms:body and cms:element JSP tags contain javascript code to enable the live edit. | ||
| - | * **WCMS Page View (Catalog Perspective)**: | ||
| - | * A website may be cloned by using the personalization tool. | ||
| - | * **Navigation**: | ||
| - | * **Customer Segments:** Part of the [[sap_hybris_commerce: | ||
| - | * **Synchronization of a single page or component** | ||
| - | * Pages and slots can be **locked for editing** | ||
| - | * **Blacklist**: | ||
| - | * **Query box** | ||
| - | * Quick Collection: It is a set of elements which is stored in the session of the current user. It is like a clipboard for collections. | ||
| - | * Named Collections | ||
| - | * **Wizards** for the creation or selection of items. They may have decision, mandatory, reference and type selector pages. | ||
| * **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: 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. |
| - | * **cmscockpit**((Deprecated since SAP Hybris 6.7)) | + | * cmsbackoffice: |
| - | * **Content | + | |
| + | | ||
| + | * cmswebservices: | ||
| + | | ||
| ===== CMS Restrictions ===== | ===== CMS Restrictions ===== | ||
| * They control the **visibility** from components and pages. | * They control the **visibility** from components and pages. | ||
| - | * Hybris comes out-of-box with the following restrictions: | + | * Hybris comes out-of-box with the following restrictions: |
| * To add a restriction to a component, you have to go to the **visibility context section** of the editor area and add a new instance of any of the above restrictions. | * To add a restriction to a component, you have to go to the **visibility context section** of the editor area and add a new instance of any of the above restrictions. | ||
| - | * The accelerator includes an additonal | + | * The accelerator includes an additional |
| * The BTG extension defines a **Customer Segment Restriction** | * The BTG extension defines a **Customer Segment Restriction** | ||
| * Each pageType have a list of restrictions types which are applicable to it. | * Each pageType have a list of restrictions types which are applicable to it. | ||
| ==== Evaluation of Restrictions ==== | ==== Evaluation of Restrictions ==== | ||
| - | The restriction are evaluatedduring | + | The restriction are evaluated during |
| DefaultCMSPageSlotComponentService.getCMSComponentsForContentSlot(..) and | DefaultCMSPageSlotComponentService.getCMSComponentsForContentSlot(..) and | ||
| flattenComponentContainerHierarchy(..) which only return visible components. | flattenComponentContainerHierarchy(..) which only return visible components. | ||
| - | ==== Data Model ==== | + | |
| - | * [[https:// | + | ===== Key features of smartEdit |
| - | * 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 | + | * [[https:// |
| - | ===== Futher | + | * **Pages and Storefront** |
| - | [[https:// | + | * In-place WYSIWYG editing of pages and components |
| + | * Versioning 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 | ||
| + | * This information | ||
| + | * The frontend must implement the [[https:// | ||
| + | * **Navigation**: | ||
| + | * Use of workflows to guide the edition and approval of those changes | ||
| + | |||
| + | |||
| + | |||
| + | ===== Further | ||
| + | [[https:// | ||
| + | [[sap_hybris_commerce: | ||
| + | [[https:// | ||
| + | [[https:// | ||
| ===== Pitfalls ===== | ===== Pitfalls ===== | ||
| - | | + | * Page templates |
| - | | + | |
| * 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. | ||
| + | |||
| + | ==== SmartEdit ===== | ||
| + | * There currently no way to synchronize the navigation nodes inside SmartEdit (with SAP hybris 1905) | ||
| + | * 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 | ||
| --Based on SAP Hybris 1905 | --Based on SAP Hybris 1905 | ||