@anilchennapragada ,   I understand the problem here, at this moment, I have a few solutions for you. 1. As Adobe always recommends of using modularity while authoring a page, if the image components are used instead of any custom component where the image is part of the custom component html, this ...

Hi @Sanjana12,   Path browser is basically a cq:dialog widget. example: <pagepath jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/form/pathbrowser" fieldLabel="Page" name="./pagePath" required="{Boolean}true" root...

Adding a point here,reverse distribution is also possible through SCD, the action attribute would be "PULL" on your trigger.example :  $ curl -v -u admin:admin http://localhost:8081/libs/sling/distribution/services/agents/publish -d 'action=PULL' -d 'path=/content/sample1' This is more important a...

Hi @Tessa_learner1 ,To address your error, I might need your code snippet to check. In simple words, a Resource Resolver is a basically an interface between the objects in the repository (Sling considers them as resources) and the code you write. Since the interface api helps to access the resources...

Hi @user07108 ,   Width of the image inside the text component?   click on the source edit button and you can paste your html there and hence you can edit your height and width attributes.   There's one problem here though, the image path might not get shortened on dispatcher/production. I would su...

No need to extend any file @goonmanian-gooner , have a styling in your project's client-lib  targeting the container selectors. You can inspect the element and check the css classes, example:   

Yes possible, you can write overriding css for your parsys/container. Do not do any changes to the files under libs though, you can write your own css in your project specific folder, targeting the containers/parsys through selectors.Thank you.

Not necessarily. Clearing the cache could be a little safer if there is any update to your forms/components.

Hi @sesmic Follow the steps for building a package: go to http://localhost:4502/crx/packmgr/index.jsp  and click on create a package on the top navigation, just beside the search bar.   give a proper package name and other details and click on OK.   a package will be created as show in the picture....

Hi @webdev91,   Recently Adobe has come up with a core component for the sitemap feature, leaving the ACS commons or Osgi config approach deprecated. And since you mentioned that this is a recent migration, I would strongly recommend you to use the latest version of core components.More on new sitem...