As explained by Arun, it is ok to have read access to /conf. Permission to /conf is required because you are probably adding client library through page design hence read permission to /conf(i.e. templates) is required. In cases where component level client libraries are used, permission to /conf is...

I was wishing to rewrite their names so that I'll be able to make package of policies related to certain templates.

All of my template policies are stored like "policy_1522132149527" even after giving readable policy Title and policy description. Whenever I am sharing package(containing editable templates) with anyone, it is difficult to identify policy of template so I have to create package without policies and...

Though adding component level client library should be a perfect solution for your case, the only problem I am seeing is that the time required to load JS and CSS of that component.People prefer to load CSS at the head and JS just before end of body because they want to show static stylized content ...

Hi dgordon86​,As of now, I have tried the same as you have stated(as mentioned in the question's description)I have used % units in edit mode and vh units otherwise.As you are saying, the editing v publishing experience isn't same.

I need vh units for displaying images with height equal to view port. As per AEM 6.3 touch ui limitations, vh units aren't supported. Hence I have overwritten vh units with % unit for wcmmode = edit. But still vh and % units behave very differently on different devices and screen sizes. Hence I need...