Handling AEM Core components

[mkrzyzanowski]

Adobe maintains a set of core components: https://github.com/adobe/aem-core-wcm-components.

The scope of this task is to investigate if Bobcat can handle authoring using these components and add such capability wherever it is not possible.

Note: we're assuming the latest version of Core components

Environment:

• AEM 6.5
• All tests should be written in repository: bobcat-aem-tests

Components:

Template components

• Page
• Navigation
• Language Navigation
• Breadcrumb
• Quick Search

Page authoring components

• Text
• Title
• Image
• Download Thanks @Danon9111 for noticing that the Download Component is deprecated
• Teaser
• Button
• List
• Content Fragment
• Content Fragment List
• Separator there is no need of adding any tests. New issue in Bobcat core functionality Handling Styles Variant functionality  #392
• Sharing changes in core Bobcat functionality required Handling AEM Page Properties  #393

Container components

• Container
• Carousel
• Accordion
• Tabs

Form components

• Form container
• Form text field
• Form options field
• Form hidden field
• Form button

[kaczymuczy]

I'll join, will take care of Title first

[kaczymuczy]

Next on my list is List

[kaczymuczy]

Text is already covered by ConfigureComponentTest - checking it on the list as "done"

[kaczymuczy]

Next - Image

[jaskowskak]

Hi, I take care of Teaser component

[DeChrish]

@kaczymuczy @jaskowskak @mkrzyzanowski Good Job!!

[Danon9111]

I will take a look on Download component

EDIT:
Regarding AEM properties Download component is deprecated since 6.5 version

[barbasial]

I'm joining too. I will take care of Button component.

[kaczymuczy]

I'll put the Content Fragment now under my looking glass

[Danon9111]

I will take a look on the Separator component

[jaskowskak]

I'll take care of Carousel

[Danon9111]

Separator is a core component and available in AEM 6.5. Unfortunately it is not available (by default) under We Retail content. It is available only under component demo pages (../content/core-components-examples/library).

We can make it available by modifying default configuration of 'content-page' template under We Retail branch. (This need to be confirmed, if is it possible to automate this action)

We can also prepare tests for Separator component, which will work under path

/content/core-components-examples/library

Or we can drop this component.

@mkrzyzanowski @Shaihuludus what do you think?

P.S.
As I heard there is bigger number of components whit similar situation. Maybe it would be valuable to verify which components?

[jaskowskak]

Tests for Teaser component: wttech/bobcat-aem-tests#12

[Danon9111]

Creating tests for Separator component will be dropped. Reasons behind it are:

• Separator component does not have any configuration dialog
• In default AEM solution, for Separator component Author can change only Style Variant
• Bobcat does not support operations on Style Variants. New ticket for this is open Handling Styles Variant functionality  #392

I have also noticed that in Core Components 2.6.0 is added new component - Experience Fragment and in Core Components 2.7.0 Embed . Do we want add them to the list and create tests for them?

[Danon9111]

I will try Sharing component this time ;)

[Danon9111]

Sharing component need some special configuration of page properties. We can achieve this by "hard coding" this properties, but after that we don't have anything to automate. Other way is to create mechanism in Bobcat to set proper page properties. For this purpose I have create issue in main Bobcat repo - #393

For now, there is no sense to create any tests for Sharing component.

[Danon9111]

I will work on breadcrumb right now

[barbasial]

I will try Accordion

[kaczymuczy]

I'm going for the Content Fragment List

[kaczymuczy]

Working on Tabs now

[kaczymuczy]

Going for Form Container

[kaczymuczy]

Actually I'll take all Form Components should no one protest :)