Expand my Community achievements bar.

SOLVED

custom, OOTB component

Avatar

Level 9

Hi All,

Suppose we have an OOTB component which is customized. How will we ensure that we are using the custom component and not the OOTB component.

1 Accepted Solution

Avatar

Correct answer by
Level 7

if you simply want to identify which all components are dragged on page, i.e. either the custom one or OOTB one, then you can use either of the below 2 options:

  1. append query parameter to the page ?debug=layout in author and reload the page, this will let you identify which all components are dragged on the page along with their repository path.
  2. else you can directly go to crxde lite and see which all components are present on the page.

If you simply want to make sure you are dragging the right component on the page then as Scott mentioned, simply keep its component group different so author know where are are custom component present because OOTB components are generally under component group General.

- Runal

View solution in original post

2 Replies

Avatar

Level 10

When you create a custom component - you specify where it is in the Sidekick (or side rail in Touch UI). You also give it a different name -- like HeroComponent.

When an AEM author sets up a CQ page - the author needs to know the name of the custom component and in which CQ group it's located. (for example -- General)

Read this article that will discuss how to create an AEM Touch UI component. You will see the difference between an OOTB component and  custom one:

https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html

In this example - an author will know the difference between a text component or the HeroText component. 

Avatar

Correct answer by
Level 7

if you simply want to identify which all components are dragged on page, i.e. either the custom one or OOTB one, then you can use either of the below 2 options:

  1. append query parameter to the page ?debug=layout in author and reload the page, this will let you identify which all components are dragged on the page along with their repository path.
  2. else you can directly go to crxde lite and see which all components are present on the page.

If you simply want to make sure you are dragging the right component on the page then as Scott mentioned, simply keep its component group different so author know where are are custom component present because OOTB components are generally under component group General.

- Runal