Check the articles [1] [2], which nicely explain the difference b/w the two.   [1] http://www.aemcq5tutorials.com/tutorials/aem-core-components/#core-components-advantages [2] https://aemcq5pedia.wordpress.com/2018/01/05/core-components/

@vinuu123 Use HTL Number format [1], documentation says: The formatting pattern supports both a positive and negative pattern, separated by semicolon. Each sub-pattern can have a prefix, a numeric part and a suffix. The negative sub-pattern can only change the prefix or/and suffix. The following cha...

You can use either option. The only difference is, Core components are part of AEMaaCS, while in on-prem setup, you need to install it (either via POM dependency or manually).

Inplace editing/dialog configuration open in different contexts and do not consider css/js included in your template. Though, you can use externalStyleSheets [1] in RTE configuration to specify project-specific styles to be used in edit mode. Navigate to the root node of your text component, for ex...

Check your apache rewrite logs and try to debug which rule is converting request to /?cache

I feel its because of the rule of adding .html extn    What may be happening is: 1. Request for root domain reach to apache as URI "/" 2. the add .html extn update URI to "/.html"   Now this URI does not map to any further rule, so throw 404.   Try moving this rule towards the end # Add .html extens...

Users and groups are stored under /home node. Please see [1] for details.   [1] https://experienceleague.adobe.com/docs/experience-manager-64/administering/security/security.html?lang=en

@akhilraj So the resourcePath is pointing to your component when you place it on content/jcr:content?

Just cross-check if content nodes in your experience fragment is having any self-call,  eg. Experience fragment -> component A -> Experience fragment  or Experience fragment -> component A -> Component B -> Component A