@rohankalra This could be a CSS issue with your custom component. Can you provide some more detail on the issue?

@varaprasadande1 I believe- Oracle Java™ 11 is supported until September 2026 at a minimum. Support for Oracle Java™ 17 is in preparation.  ref. https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requirements.html?lang=en you could also always specify the ...

@NathanVieira you need to include the resource as below: <div data-sly-resource="${'navigation' @ resourceType='/apps/myproject/components/navigation'}"></div>

@Abhishek16 you can try the below: currentPage = request.getResourceResolver().adaptTo(PageManager.class).getContainingPage(resource);

@manasabojja7 You could delegate the model by using adapters- @Model(adaptables = SlingHttpServletRequest.class, adapters = Tabs.class, resourceType = "myproject/components/myTabs") and could use the below to include the object: @Self@Via(type = ResourceSuperType.class)@Delegate(excludes = De...

@Johnhenao10 You could use the parsys component inside your custom component: <div class="custom-component"><h2>Custom header</h2><sly data-sly-resource="${'parsys' @ resourceType='wcm/foundation/components/parsys', decorationTagName='div'}"/></div>  You could also proxy the parsys component and cus...

Thanks for the replies, we have figured out the issue- it was due to the scope defined in the maven dependency, we had to change from compile to provided in the pom file.

@Tessa_learner1 In short,  Node is like a unit of the JCR repository and resource is something that sling uses to access Nodes. JCR APIs act on the Node and Sling APIs use the resource.   The Sling API works at a higher, more abstract level than the JCR API. This allows your code to be more reusable...

@RobertHarperFS it seems by default, the ability to switch to the classic UI via the admin consoles has been disabled,  ref. https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/enable-classic-ui-admin.html?lang=en  

@maheshp  1. You could create a utility that updates the page properties in bulk. 2. You could make use of groovy scripting    you could have a look at this ref. too- https://github.com/AdobeDocs/experience-manager-65.en/blob/main/help/sites-developing/bulk-editing.md https://experienceleague.adobe....