We were looking into the same and ended up creating a ticket with Adobe Support. Here’s their feedback:The ability to Create Live Copy has been added to AEMaaCS (via internal improvement request CQ-4268610). This was not backported to AEM 6.5 versions with the following feedback: If the improvement ...

Hey!  I think what you're looking for is the Sling Model Exporter. With it, you can define a Sling Model with the properties you want to expose, that is then available by browsing to your-page.model.json.

Hey! The AEM project archetype creates a page component for you when initialising your project. That page is including the contexthub code in your page. If you’re not using contexthub (and you’re not planning to use it either) you’re safe to remove it from your code. You should find something back u...

Unfortunately, as we're using a JCR Query (via Session), we need a JCR_OAK AemContext.

I’m trying to write a unit test for one of my services that does a query as part of the service. As such, I need a JCR_OAK AemContext to be able to test these changes. My unit test roughly looks like below:    @ExtendWith(AemContextExtension.class) class MyUnitTest { private static final String ...

Nice, that's amazing. I'll check it out for myself too. Thanks!

As pointed out by @Jörg_Hoh , there's an even better way of doing it!  Create a map with the properties you want to pass to your serviceMap<String,Object> parameters = new HashMap<>(); parameters.put("my_property","my property");You can then pass this to your context with the registerInjectActivateS...

Hey! In order to be able to use a custom device group on your page, you need to add it to the cq:deviceGroups property on the root of your website. So say you have a website "my-site" under /content/my-site and a custom device group "my-site-devices" under /etc/mobile/groups/my-site-devices, then yo...

Hey Created a support case with Adobe customer care, and they pointed out that the way you're referencing the uber jar has changed. As outlined on the SP6 release notes, the new way to include the uber-jar is:  <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>...

From what I've noticed, it looks like the wrapper div is not being generated when including a component. Because of this, the style system cannot add any classes to it. Adding @decoration=true to the data-sly-resource will include the wrapper div (which is important, because otherwise your cq:htmlTa...