Since you have enabled -DoptionIncludeFrontendModule=y which will have a node module for front end development. If this module is needed, please follow the steps at [1]. If not required, start using -DoptionIncludeFrontendModule=n[1]- https://docs.adobe.com/content/help/en/experience-manager-core-co...

I don't think we have one. But, you can refer to adobe published bot integration for web chatbots at [1]. If its a JS based bot, you can simply manage via clientlibs or script calls. [1] - https://github.com/adobe/aec-bot-integrations/tree/master/aem-chatbot-demo 

You can create a granite:rendercondition where you can check for the template type and set the default value.  Search rendercondition in crx/de search to see some OOTB samples. eg. /libs/cq/gui/components/renderconditions

The package is a compiled version of your code where the java code is compiled to a jar files and is included in the /apps/<sitename>/install folder along with ui.apps content. Rest of the configurations under /apps, etc can be imported into eclipse, but not the java code. If you want to develop aga...

As per the screenshot the number of tabs are fixed, so you can have another tab - order selector - where you can configure the order. Btw, I would prefer this to be done as a container and subcomponent structure instead of a blobbed up dialog.

good to know, thanks

Do you use ACL as a seperate package and any chance admin user is missing permissions to /system/sling/monitoring/mbeans

everything seems to be in place. Are you using admin user itself ?

Hi, Are you able to find the preupgrade component at /system/console/configMgr/com.adobe.aem.upgrade.prechecks.mbean.impl.PreUpgradeTasksMBeanImpl Once you have that one, we can get the PreUpgrade tasks at /system/console/jmx/com.adobe.aem.upgrade.prechecks%3Atype%3DPreUpgradeTasks

Hi, You can go into developer mode in editor view of a page to get a view of which node is taking time to load. Most of the times, clientlibs and how JS is used is the culprit for bad performance on the page. Another excellent way of debugging is to use Google light house audit on the webpage using ...