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 customizable and expandable. In this blog, we will look at the mysterious world of AEM components and how they impact the platform’s overall functionality and user experience.  Fig. Core Components Library Classification o ..read more

As all AEM Developers know, AEM, and more-so the underlying JCR, has limitations on how many children a single parent can have before we start to see performance issues.  First in the UI, and then more critically in the ability to look-up and manage content nodes themselves.  When designing for a net-new AEM website, this can be planned around, however, many times when dealing with a migration, there may be requirements to both keep existing links in-tact, which may put us in a situation where a large flat list, at least as exposed to the end-user, is unavoidable. In this post, I w ..read more

I enjoy building websites using the Adobe Experience Manager (AEM) content management system. I also enjoy using JavaScript frameworks like Vue, React, and Angular to create rich web applications. Occasionally I get to do both. AEM provides a SPA Editor to facilitate building components for single-page applications. The SPA Editor enables front-end developers to produce components in React or Angular. These components are used by the author to create rich, native-like experiences. Some time ago, I was engaged with a customer who needed a single-page application written in Vue and not React o ..read more

About the OpenAI Assistants API The OpenAI Assistants API allows you to build AI assistants within your own applications. An Assistant has instructions and can leverage models, tools, and knowledge to respond to user queries. The Assistants API is designed to help developers build powerful AI assistants capable of performing a variety of tasks. Different from OpenAI’s Chat Completions API, Assistants API is an agent framework. Your instruction is similar to a system prompt but is just one part of the message that includes other messaging and internal functions that are out of your contro ..read more

Workflow Model A Workflow Model represents a definition (model) of a workflow. It is made of Workflow Nodes and Workflow Transitions. Workflow models in Adobe Experience Manager (AEM) are used to define the series of steps executed when a user starts a workflow, and it is used for the automatic processing of content as well as facilitating governance and processes requiring human decision-making. Workflows enable you to automate processes for managing resources and publishing content in your AEM environment. AEM Workflow provides a way to collaborate, manage, and proc ..read more

There’s a new type of environment known as a Rapid Development Environment (RDE) with Adobe’s Cloud Service. This environment was specifically made with developers in mind to accelerate code deployments and other development activities in Cloud Service. We’ve had a chance to use the RDE to better understand its capabilities, strengths, and gaps. Pipelines in an AEMaaCS program are often executing and busy during high development activity, which is one of the main reasons for using an RDE. If a developer isn’t using an RDE and needs to validate that their code will work in Cloud Service, they ..read more

Deploying multiple tenants to AEM through Adobe Cloud Manager can be challenging. Cloud Manager does not provide the ability to configure multiple deployment pipelines to AEM. More specifically, Cloud Manager cannot deploy from more than one Git repository. In a multi-tenant ecosystem, each tenant dev team needs to store their code in separate repositories and deploy them when needed. Ideally, this should be done automatically for lower environments like DEV whenever there is a code commit. To achieve this with Cloud Manager, someone must manually update the deployment pipelines to point to ..read more

With the introduction of Adobe Experience Manager as a Cloud Service (AEMaaCS), customers who currently run AEM on premise or through Adobe Managed Services (AMS) and want to migrate to the cloud need to plan for changes made to the AEM repository. One tool to assist in the process is the Repository Modernizer. This tool comes after you’ve already used the Best Practices Analyzer and is a part of the code refactoring process. The Repository Modernizer is needed to update the code repository structure from a 6.X structure to one that is compatible with AEMaaCS. Transforming your code base so ..read more

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 did not have the necessary permissions to perform these operations. To solve this problem, the client requested us to provide a custom action button in the AEM Assets Menu. This button would enable AEM authors who have permission to modify the AEM Asset ..read more

Faster asset upload and download speeds are crucial for businesses and content creators who frequently deal with large files. Whether it’s uploading files to a cloud storage platform, sharing files with colleagues, or publishing content online, faster upload and download speeds enable individuals and teams to work more efficiently, saving time and increasing productivity.  In this blog, I will look at these several factors compared across the architecture differences of AEM with Adobe Managed Services (AMS) compared to the newer AEM as a Cloud Service (AEMaaCS) architecture.  DAM u ..read more