Hi Dragon,You can go through User Interface customization for AEM 6  .  For your use case refer the samples at  https://docs.adobe.com/docs/en/aem/6-0/develop/extending/customizing-page-authoring-touch.htmlThanks,

Hi bdk13​, You can use Apache Sling - Managing users and groups (jackrabbit.usermanager)  with an advantage of code developed from actual develpment team.Thanks,

Hi Swathi,Refer FAQ: How to configure replication agent to specific site content Thanks,

Hi ofuangka,    JCR resolver & mapping con't resolve at run time and configuration should exist prior. For your use case one of the option is to use apache rewrite rule.  Thanks,

Hi Sandeep,You need tune based on you application, Most commonly used for small/medium apps at CQ-OPS - JVM init Arguments for a Reliable CQ Instance Thanks,

Hi Bob, You can ignore the error. It needs product code change to turn off validation Or have implement EntityResolver due to changes in XML parsing at platform level.  The functionality will continue to work but log is annoying.  You can ask official support request to fix the same but you can safe...

Hi Tom,  Explain query tool provide the information you are looking Operations Dashboard  ,   enable debug log on [A] will let you see in log file but will have more additional  info.[A]org.apache.jackrabbit.oak.plugins.indexorg.apache.jackrabbit.oak.queryThanks,

Hi Lakshmi,Typically component changed from standard to factory   OR maintaining the config in both filesystem/repository causes such issue. If you followed best practise mentioned in article edubey mentioned earlier,still issue exist then report to official support team.Thanks,

Hi Girish,  There is no limitation. Typically from security point  20 to 30 minutes is sufficient for most of application.  Change based on your requirements. Create a package of Configuring OSGi in repository & place the package in <cq_home>/crx-quickstart/install/Thanks,

Hi Jacob,Sidekick not appearing indicates issue with init.jsp & should be error in the log files OR your initial installation failed due to resourse constraint.   Sanity check using http://www.aemstuff.com/osgi/aem62.html  Thanks,