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

Adobe Edge Delivery Services (previously Next-Gen Composability or Project Franklin) is a relatively new offering from Adobe that accelerates content velocity, delivers high-impact experiences at a high performance, and greatly reduces time-to-market. The idea behind the technology is relatively straightforward: empower users where they are, and they don’t need to worry about the usual concerns with publishing their content via additional tools. By allowing them quick edit and publishing tools in Microsoft Word or Google Docs, they can skip the process of having to learn the interfaces and p ..read more

What if you could host a development AEM instance on a single-board, low-cost, high-performance computer that consumes very little power with hardware that you pay for once? That’s the question I set out to answer with my minimalist AEM experiment. Leading a team of AEM developers who support an on-prem implementation, I’m tasked with trying to make local environment setups as painless as possible. This is often complicated by variations in hardware and resources among the team members. Hosting AEM on the same machine as your IDE (Integrated Development Environment) is not always optimal due ..read more

Welcome to the continuation of our multi-part series on using Content Automation in AEM as a Cloud Service to accelerate your creative operations. To gain a more comprehensive understanding, make sure to check out Part 1 of this series which gives an overview of the feature by Adobe, along with helpful use cases and Part 2 for a walkthrough of applying Lightroom filters to Assets. In this third segment, we will take a closer look at the creative operations within Adobe Photoshop, and how this process is replicated in AEM as a Cloud Service. Creative Operations Process in Adobe Photoshop In t ..read more

Content Management Systems and Templating In the past, I have worked with various Content Management Systems, including Drupal, which utilized the Twig templating engine to generate the HTML for web pages. Twig shares many features with HTL, the templating language used in Adobe Experience Manager (AEM). While working with Twig templates in conjunction with the Pattern Lab design system tool, I appreciated the ability to see changes, mock different authored properties, and thoroughly test templates before integrating them into the CMS. We tested component functionality, visual design, respons ..read more

The AEM Style System allows the template creator to define style classes in the component’s content policy as well as page policy so that the content author can select them while modifying the component on the page. These styles can be visual variations of components, making them more versatile. Use Case: The Style System offers a consistent solution to both templates and content author requirements: a) Style classes can be defined by template authors in component content policies. b) When editing the component on a page, content authors can then select these classes from a drop-down menu to ..read more