@Kautuk_shani and @om_vineet, I am not able to understand that how does this resolve the given use case?? If we keep the XF component locked on the template then the same XF will be used on all the brands and if we keep it unlocked then we have to author the XF path on all the pages. How can we solve this?

Hi Scott,regardingWe need to modify JSON output from ContentServices. Were can we find documentation on how to override, decorate and transform JSON output? It is extremely difficult to find any technical documentation on content services at all.BRHenrik Heiestad

Here is another very good article: Common critical AEM issues

Thanks, it turned out my issue was tied to the version of something I had installed that was hiding the Page Design option. I was able to get it figured out.

I would recommend:1. Writing template specific client libraries.2. Consolidating all your client libraries basis component inclusion using custom code (that would be executed once in application lifetime) in to a single library and loading them at the end of the page.3. Use caching if size of the client lib increases.4. Above would not be applied for the third party libraries. And those would be loaded before solution libraries.

IMO no such hooks available. Configure your service to have both day & night settings. In service factory have the instances pick right configuration based on a time pattern.

Thanks Sham. I will give this a try. Do we know by when can we expect these? Also do we have both in pipeline i.e. logback as well as MDC?