Hi @annaachen1214    The topic is extremely large and can have many flavors depending on the specific of your current implementation. I would recommend to start from the official documentation:https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journey/getti...

Hi @KKeerthi  From the Adobe's best practice documentation: "Use includedPaths and avoid excludedPaths property. Always set queryPaths value to the same value as includedPaths value."   https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/understand-indexing-bes...

Hi @mohanmathka    Maybe these resources on similar/same topic can help you out:- https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/last-modified-header-is-not-being-added-in-page-response-from/td-p/438565- https://experienceleague.adobe.com/en/docs/experience-manager-dispatc...

Hi @Zendarkke    Can you share you HTL code ? I believe the property is an array so you might need to iterate it. Also, I suggest using Sling models to read props and make the values available in HTL.

Hi @rajkumarha1    I believe this is what you need to do: https://lhotsetechnologies.com/blog/enable-rte-plugins-for-content-fragment/Once you have the StyledTextEditor.js file in your codebase, you can tweak it as you need. I believe for the paragraphs you need to find this section and modify it: ...

Hi @diana-raileanu    Maybe you can leverage some of the properties for the boot delegation support and play around with them in your sling.properties file:https://sling.apache.org/documentation/configuration.html#osgi-boot-delegation-support-1   Maybe org.osgi.framework.system.packages.extra=com.su...

Hi @Jitesh07  If you want to refresh the entire page, as you said, can you try this snippet ? const contentApi = $(".foundation-content").adaptTo("foundation-content"); if (contentApi) { contentApi.refresh(); }   Doc: https://developer.adobe.com/experience-manager/reference-materials/6-5/granite...

Hi @Sandeep-L    Not sure exactly what is happening specifically on your project, but it seams that third party (in your case the ACS Commons) dependency is not getting embedded upon deployment. Maybe this article can help you:- https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-depen...

You can either add the content in your codebase to be installed upon deployment, as a one time thing.Or see if you can leverage ACS Commons: https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html

Hi @dylanmccurry  Is there a reason why you cannot access the CRX in AEMaaCS ? You don't have permissions ? Because it is accessible for Author tier and in theory you can also do the manual changes that you need. Only /apps and /libs are immutable, so they cannot be changed. There are multiple ways ...