Extending/Overlaying a Content Fragment Component into your custom component in AEM 6.4

Avatar

Avatar

berni7473

Avatar

berni7473

berni7473

26-03-2019

Hello Everyone,

Is it possible to extend or overlay the content fragment component in AEM 6.4, inside a custom project? I have tried both extending and overlaying the content fragment component from core but the dialogs in touch-ui do not seem to work.

I noticed that the structure of the cq:dialog for the content fragment component in core is also a bit different too.

1719203_pastedImage_10.png

There is granite:data node inside the structure which has the above properties. To my understanding I guess these are related to Coral UI 3, but still i'm not very sure.

Can you please provide your insights on this.

Thanks and Regards,

Bernadine Soman

Jörg HohFeike VisserVeena_07smacdonald2008

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831
Arun_Patidar
MVP

27-03-2019

Yes, you can extend the cf for your own project, you can take example of we-retail cf component.

you may need to create a dialog structure, it can be either of type coral2 or coral3.

Answers (3)

Answers (3)

Avatar

Avatar

berni7473

Avatar

berni7473

berni7473

31-03-2019

Thank you Arun for your response. I checked and created my custom cf component.

Avatar

Avatar

berni7473

Avatar

berni7473

berni7473

27-03-2019

So is it possible to extend the Content Fragment component inside my custom project? Since the dialog structure creates data attributes rather in separate nodes?

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831
Arun_Patidar
MVP

26-03-2019

yes, these are related to coral3, data:granite node is used to create data attribute in DOM.

e.g.

data-field-path

in coral2 this properties are added directly to elementNames node.