Hi @ArchitAr2 ,    Both ways can be utilized to have effective results. When the case is utilizing AEM component and sling models, in my experience, it was better to use the Content Fragment APIs and sling apis. When utilizing headless concepts, calling via react app or component calling the AEM Gra...

Hi @HelpTech    1. Can you check this thread if its relevant? -Re: @SlingServletPaths, is there a way to specify ... - Adobe Experience League Community - 577553  It seems /bin/test should cater to /bin/test and /bin/test/abc    2. Otherwise, have you tried like below just to make sure?   @Component...

@sunnymarwaha fyi

Also check if CDN cache needs to be cleared.   Also curious since its need 24 hours plus, is the issue resolved? @FraukeSc 

@Amsalek4 yeah true, I see now item.html is not coming into picture. list.html can be explored. Looking little more into this,   We can also explore overriding teaserimpl (using delegate pattern) for this component resourcetype and in that case return the description as blank by overriding getDescri...

Hi @s1101v I hope I am not missing the context.   It seems we can use CUG applied to the folder and add a given user group to it. Assuming when user logs in via LDAP or similar mechanism their group can be identified and if the group is allowed for the folder it will allow access to contents under /...

Hello @Vignesh_K_S    We have faced similar issue when we have multified option, but when the use case was to use more multifield items, there would be loading issues while authoring.   For one component, can you consider using container based component and add another component within that which ca...

Hi @fionas76543059 Did you try with just the pdf box dependency in pom?   <dependency> <groupId>org.apache.pdfbox</groupId> <artifactId>pdfbox</artifactId> <version>2.0.20</version> </dependency>   Just with that I am not seeing similar issue for existing bundles

You can overlay list.html or  item.html and see if you update it to remove or hide description.    aem-core-wcm-components/content/src/content/jcr_root/apps/core/wcm/components/list/v4/list/item.html at main · adobe/aem-core-wcm-components · GitHub    

This might be OOTB behavior, have you tried in Vanilla instance if it is same behavior?