Thank you all for your quick response.As many suggested the below structure, we have decided to go with it./content /brand /us/en/ /in/en/ Thank you again, everyone!@Fanindra_Surat @SantoshSai @Kiran_Vedantam @Himanshu_Jain 

We have a website with different regions (USA and India). All the content will be in English only so, no translation is needed. Also, the pages for both regions are different and they don't share the content either. Only, the look and feel are the same. In this case, what would be the best folder st...

I was building pages in my local while the DEV environment for author and publish instance was getting configured. Now we have the DEV environment configured so I created a package of conf, dam, experience fragments, and pages separately from my local and installed them in the DEV author instance. I...

Hi @Fanindra_Surat Thank you for your response.My additional question on the points below.1. It's good to know that there is an HTTP Client already available in uber-jar so I don't need to worry about adding additional dependency (at least initially). Of course, I am going to research more on this b...

Hello Everyone,I just wanted to throw a question on REST API implementation here. We have a third-party REST API that returns data needed for our website's couple of pages. I am not sure which REST Client to use or how to implement one in terms of AEM development. So, I am just seeking some guidance...

Hi @Anish-Sinha Yes, I agree that a Layout Container definitely provides more features to the author in managing the layout, adding policies, etc. But here, we define the layout and manage it through the code. The sole purpose of ParSys here is to allow the author to add the component, so thought no...

Hello Everyone,We have a simple 3-Columns Grid component where we are using "wcm/foundation/components/parsys", directly inside those columns for adding whatever component. Our concern is that, is it safe to use "parsys" as resourceType directly or should we use "wcm/foundation/components/responsive...

Hi @BrianKasingli Thank you very much for your excellent explanation.Now, it makes sense why Adobe decided to use @ScriptVariable in this particular Breadcrumb case, as they can handle multiple conditions in a one-liner.  

@Jörg_Hoh Thank you for your quick response.In which case we should use @ValueMapValue over @Inject? or should we always use @Inject annotation as a best practice?Note: I have edited my question a bit. I was talking about @ValueMapValue annotation

I was looking into aem-core-wcm-components GitHub repo and noticed the different patterns for converting string to integer or boolean. Below is the code snippet from BreadcrumpImpl.java. @ScriptVariable private ValueMap properties; private boolean showHidden; private int startLevel; @PostConstruct...