What is the Adobe Exchange?

by Peter Nash

Mar 06 , 2019
What is the Adobe Exchange?

Joey and I had the opportunity to sit down with Tyler Briggs, Technology Partner Marketing Manager, and David Humphries, Senior Manager of Adobe Exchange, to talk about the Adobe Exchange. We started off asking, what the Adobe Exchange is, because both Joey and I had not ever dealt with it and we assumed most people hadn’t. The Adobe Exchange is an application marketplace with tools that enhance Adobe product users experience for all three of Adobe’s clouds (Document, Creative, and Experience).

What’s the Point of Using a Template Type?

by Dylan Reniers

Feb 12 , 2019
What’s the Point of Using a Template Type?

A while back, a common AEM question came up on a slack channel I am part of: “When looking into editable templates, what is the purpose of using a template type? I’ve read it’s the ‘template of a template’, but still it is not quite clear to me. Does editing a template type impose the same effects as editing a template?” It is true that a template type is basically the ‘template’ of a template.

Catching up with David Gonzalez

Adobe Summit 2018

by Joey Smith

Jan 10 , 2019
Catching up with David Gonzalez

This year at Summit I didn’t have booth duty, which allowed me more freedom to browse the Community Pavilion and attend sessions and labs. One of the labs I was excited to attend was David Gonzalez’s (https://www.linkedin.com/in/davidjgonzalez/). David is a Technical Marketing Engineer at Adobe and co-project lead of ACS AEM Commons/Tools/Samples, and his lab was called “Accelerate Your Development with Experience Manager Core Components” (https://adobesummit.lanyonevents.com/2018/connect/sessionDetail.ww?SESSION_ID=6149). After his lab, David took some time to talk with me about what’s new with ACS AEM Commons.

Extending the ACS AEM Commons Generic List to Support Multiple Fields

by Matthew Sullivan

Nov 27 , 2018
Extending the ACS AEM Commons Generic List to Support Multiple Fields

The Adobe Experience Manager ACS Commons Generic List facilitates authorable Title / Value pairs that can be used to populate drop downs from a centrally authored location. The functionality of the Generic List is limited to the Title and Value pairs, but there could be other use cases for centrally managed metadata that can be easily chosen from a dropdown. This example will extend the Generic List to manage metadata for organizational units / departments.

Important Security Updates for AEM 6.x

by Joey Smith

Oct 16 , 2018
Important Security Updates for AEM 6.x

If you are not subscribed to Adobe’s Security Bulletins, you might not have heard about the recent security update issued by Adobe for all supported versions of AEM (6.0 - 6.4). Quoting their press release: Adobe has released security updates for Adobe Experience Manager. These updates resolve two reflected cross-site scripting vulnerabilities rated Moderate, and three stored cross-site scripting vulnerabilities rated Important that could result in sensitive information disclosure.

AEM Encryption 101: How to Encrypt a Shared Secret

by Curtis Mortensen

Oct 02 , 2018
AEM Encryption 101: How to Encrypt a Shared Secret

I recently had a request from a client who wanted to use a third party service that didn’t provide an authentication key. Instead I need to use a simple username and password combo that the client didn’t want exposed in our code repository where we generally keep our configuration values. Having heard about encrypted configuration values, I set out to learn how to use them. I found a variety of resources out there, but none of them really walked me through from Point A to Point B.

Oh by the way… The Content Tree is Back!

A return to normalcy

by Peter Nash

Sep 05 , 2018
Oh by the way… The Content Tree is Back!

In the rush of everyone talking about the newest features of AEM 6.4, something was overlooked. Those of us that were familiar with the Classic UI in Adobe Experience Manager, and how everything worked in it, were thrown for a bit of a loop when the Touch UI was first introduced in AEM 5.6. Not only was everything in a new spot or organized in a different way, but the method to get to those places also changed.

CQDOC-12969 UPDATE: Embedding Resources in Proxied Client Libraries

Ambiguous AEM Documentation Clarified

by Joey Smith

Aug 29 , 2018
CQDOC-12969 UPDATE: Embedding Resources in Proxied Client Libraries

In a previous article, Tyler Maynard of Hoodoo Digital, pointed out that the Adobe Experience Manager documentation for Using Client-Side Libraries did not expressly state that static resources needed to be within a folder path named “resources”. This prompted me to submit a ticket to the AEM documentation team to correct this error. They have now changed their documentation to reflect this requirement. No word yet on the feature enhancement request to make this a configurable item so that you can specify your own path.

Experience the New Experience League

Adobe Community Manager Interview from Adobe Summit 2018

by Peter Nash

Aug 14 , 2018
Experience the New Experience League

Some of you may already be aware of the Experience League. It’s been around since early 2018, but it was a big push at Adobe Summit 2018. That’s where I ran into Cary Burgess and Scott MacDonald. They took some time to talk to me about the Experience League. The goal of the League is to help connect people that are users of Adobe Experience Manager, and help make them successful.

Embedding Resources in Proxied Client Libraries

Clarifying Ambiguous AEM Documentation

by Tyler Maynard

Aug 06 , 2018
Embedding Resources in Proxied Client Libraries

If you’re planning on moving towards Adobe Experience Managers recommended pattern for clientlibs in AEM 6.3+, by storing all clientlibs in ‘/apps’ and setting ‘allowProxy=“{Boolean}true”’ so that they will be proxied by the new ‘/etc.clientlibs/’ servlet, you must store referenced assets (like images) under a folder named ‘resources’. Although this is not explicitly stated in the documentation, using any other folder name will not work. As you can see in the image above, the Using Client-Side Libraries documentation examples DO use this pattern, but they don’t make any explicit statements regarding the folder naming requirements.