I'm joining a large project that is in the process of updating components and templates to 6.5. Its been difficult to tell what has and hasn't been updated without reviewing the code of each file. My thoughts are to start documenting each component with a readme as its updated. Each would have whats completed, whats remaining, and any additional notes that may be important to the update process. Like listing any dependencies or bugs that need to be addressed before it can be completed. It may no...

Currently each component gets a Java interface written. It also gets an impl class that uses annotations like @ValueMapValue and @getter in place of writing the actual getter and setters. We do this for everything regardless of how basic the component is. I've seen some blog posts that suggest you only create an interface and use the annotations like @ValueMapValue in it. This removes the need to create the impl class as well as unit tests. What would be considered the recommended/best practice ...

We created our language copy by basically copying the English version and making it a Spanish version. We can't scrap what we've done because the pages and their content have already be translated. Is there a way to convert what we have into a language copy of the English version? Its over 100 pages per language and there's 4 translated non-English languages. This is on 6.5.7 hosted with Adobe.

I've enabled the data layer and verified its working. I've been asked to add additional information to whats returned in the page and custom component data. Do I need to write my own version of the getData() method because I don't see a way to use the DataLayerBuilder for this.

Using AEM 6.5 but we are not using Magento. We are products we are importing into AEM. They can have over 40-50 attributes and each attribute has 4-8 of its own attributes. Attributes are basically technical specs describing dimensions, weights, speeds, and things you would see describing an engine. What is the best way to handle these attributes? I've seen another project were each of these types of attributes were stored as part of the product. This ended up with a bunch of attributes stored w...

I'm trying to create a Sling job and not having much luck. I've followed the docs on the Apache and Adobe sites but if keeps throwing a null pointer exception. I figure I've missed an important step that wasn't in the docs I read. Also, everything I've read thats AEM related is based on a watcher seeing a change to the JCR or a scheduled task that runs at a set time. We want to trigger it without a JCR update. My goal is to have a user perform an action that ends with a job being created and imm...