Posts Tagged ‘AEM 6.5’

Adobe Experience Manager (AEM) is a sophisticated and versatile content management tool. Components are the elements that help structure the page, for example, the header, body, and footer, through authoring. AEM’s core components, have always allowed authors to create pages that are both efficient and simple to use, whereas developers can create components that are […]

Recently, a client approached us with a requirement to update content fragment elements data, Assets metadata, and Folder metadata via an Azure-based API. Our initial solution was to implement a JMX script, which could be started by an admin user group with valid parameters. However, this was a rather limiting solution, as normal AEM authors […]

DynamoDB, offered by Amazon Web Services, is a NoSQL database that provides both key-value and document data models. It supports tables of any size with horizontal scaling (Expanding your infrastructure by incorporating extra nodes or machines to accommodate increased demands.). It empowers developers to create serverless applications that have the flexibility to begin on a […]

AEM has a vast infrastructure, and it requires time to hold expertise on it. Every expert was once a beginner, so you are never too late to start and have fun on AEM. In this blog, we will focus on the developers’ perspective of AEM and how one can start as an AEM developer. We […]

After the introduction of AEM Core Components, custom component development has been drastically changed. In some use cases, there is zero customization and core components can be directly used for authoring. Even in those situations, the custom component is needed. It can be quickly built by extending the existing core components. Thus, the development cost […]

One of the strong features of Adobe Experience Manager (AEM) is creating UI content using the content authoring capability with Core Components.  As contents are created, they are stored in a Jackrabbit Oak repository as resources, which is then fetched and rendered as HTML content.  When out-of-the-box content authoring components do not suit the needs […]

I love writing code. What I love more is writing less. Less code means fewer unit tests because you have much less coverage to hit. Well organized, modularized, short, and concise. How do you achieve this? Good software engineering practices, code generators, and leveraging existing frameworks and APIs. Leveraging Frameworks and APIs As an AEM […]

Recently, I published a blog post regarding AEM Customization: Show Unpublished Reference Alert for Content Path where I showed how to customize the Pathfield and Xffield resourceType. In doing this, I was able to showcase how to create a notification for the content author as to whether the selected content path is published or not. […]

Have you ever noticed that while authoring an AEM component, the component dialog box does not provide any hints or alerts for if the selected content path is published or not? This is a confusing scenario for AEM authors, especially when setting or choosing the content path in the component dialog for pathfield and xffield […]

Recently, one of our clients looked to add a custom field in the Adobe Experience Manager (AEM) Content Fragment Model Editor. If you’re wondering what AEM Content Fragments are, check out Dan Klco’s post, as he does a great job explaining. Content Fragment Models are built with elements from various out-of-the-box data types, including single-line […]

If you are on AEM 6.5 and have upgraded to Service Pack 5 (AEM version 6.5.5) you might have noticed that you can no longer login to AEM via CRX/DE This change was implemented in the SP5 update and according to the CSE that our team worked with: “The login and logout buttons have been […]

Before AEM 6.5, we really only had one UI to manage user permissions.  That’s not to say we couldn’t go to the JCR directly and set ACLs, but the user admin screen was just simpler. For instance, take this example from the classic user admin console. Typically, this meant that we would check the root […]