Hi @NitroHazeDev  Please find example here https://aemsimplifiedbynikhil.wordpress.com/2023/02/27/extending-core-components-model-and-creating-its-new-implementation-aem/    you don't need this part @ConsumerType public interface AFTextInputModel extends TextInput{ boolean showCharCounter(); }   ...

Hi @dylanmccurry  You can create the component and deploy with the build and run ondeploy script to change the resource type https://github.com/valtech/aem-easy-content-upgrade 

Hi @PradeepMC1  Are you trying on local Setup or with actual domain? Seems cache-control header is being overriden by CDN , example https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/launch/byo-cdn-akamai-setup#addmodify-behavior-caching 

Hi @_Anon_ymous_  Factory Servlet will not work like this. You need to register Factory Servlet dynamically based on different config.   Please check below example https://github.com/adobe/aem-core-wcm-components/blob/main/bundles/core/src/main/java/com/adobe/cq/wcm/core/components/internal/servlets...

The core component deploy scripts as precompiled bundled scripts. This allows developers to precompile their scripts at build-time. https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/developing/archetype/precompiled-bundled-scripts      This is happening because the ...

Hi @anasustic  I am not an Adobe Campaign expert but according to document it should work OOTB   The list of available personalization fields is synchronized with your Adobe Campaign instance. The fields are managed in Adobe Campaign in the schema nms:seedMember. All fields in nms:seedMember must al...

Hi @marksarmiento  Maybe try with   @Model(resourceType = {"customs/samplecomponent", "/apps/cq/experience-fragments/editor/components/experiencefragment"}.

Hi @SurabhiAc3  EDS does support loading content from another page but it all client side, Please check fragment block https://github.com/adobe/aem-block-collection/tree/main/blocks/fragment 

Hi @abhinarvekar    With the 'prod' run mode, the configuration applies to both AEMaaCS and AEM. However, if another config with a higher-priority run mode exists, that will take precedence. For AEMaaCS, place the configuration inside the config.prod folder.For AMS, use the config.prod.ams folder fo...

Hi @abhinarvekar  You could have use the OSGI runmode/config to determine the version. Example of runmodes - AEM6.5 can have prod and ams(custom) run mode AEM6.5 - prod.ams AEMaaCS - prod