Posts Tagged “Development”

The 5 Hardest AEM Concepts for New Developers

Even experienced developers struggle when trying to transition to the Adobe Experience Manager (AEM) platform (formerly Day CQ5). Once you fully grok AEM, it can be a joy to develop against; the APIs are generally straightforward and it makes presenting content easier than any other platform I have encountered. So why do so many developers have trouble ramping up on AEM?AEM turns traditional WCMS products on their head. No other CMS really works in a...

Request cq:Components with AJAX

It's quite evident CQ utilizes AJAX frequently.If you've ever opened your network tab while using CQ you'll see asynchronous request going off here and there. When authoring new components, navigating content, developing in CRXDE lite and much more. If you're unsure what it is, AJAX let's us make asynchronous server request to content without having to do a full page reload.As a CQ developers we create may cq:Component's that are rendered with a page request but...

Custom PredicateEvaluators or: How I Learned to Stop Worrying and Love QueryBuilder

One client's AssetShare page contains a checkbox: Needs Meta-data. Checking this box is supposed to return all assets coming from the DAM that do not have metadata. Specifically in this case we check for a particular attribute (@dc:title) that's a child of the jcr:content/metadata node.Our story begins with the following problem: checking the box wouldn't return certain assets. Upon investigation, I discovered that the one asset not returning in the query HAD an @dc:title attribute,...

Three Commonly Missed CQ Best Practices

Recently, I saw this thread on the Day Communique Google Group.  In the thread, a developer asks why he cannot use CRXDE in their production environment.  As it turns out, his employer followed the best practices for hardening CQ instances as recommended by Adobe which disables the WebDav servlet CRXDE uses.  This thread demonstrates three common problems I've seen on CQ installations.  Especially, when the implementers of the CQ installation are not familiar with CQ and...

Creating Detailed Packages with the CQ Deploy Plugin

Sometimes you may want to create a package with more descriptive information than the CQ Deploy Plugin provides out of the box.  You may want to customize the group or add a description or even add dependencies.   This article shows you how to include Package Metadata into your package and how to deploy the package with the CQ deploy plugin.Updating the PackageIn order to do this, first install the package into CQ and update...

My CQ5 Bookmarks

I'm pretty sparing with bookmarks, however there are a few pages I use just about every day for my job developing for Adobe CQ5.  I have these daily use bookmarks in my bookmarks toolbar.  They are:CQ ToggleActually, this is a bookmarklet, but it allows me to easily switch between editing more and a more 'real' preview mode.CQ Widgets APIA must have for dialog development.  Documents the available dialog widgets as well as the CQ JavaScript...

Overriding the default damadmin or siteadmin pages in CQ5

Overriding foundation content in CQ5 was made fairly easy by our friends on the Adobe CQ team.  In the vast majority of cases, we can just replicate the path of the original code under libs to our apps folder.  In the case of siteadmin and damadmin, this would mean we need to copy the root node from the original path: /libs/wcm/core/content/damadmin or /libs/wcm/core/content/siteadmin to /apps/wcm/core/content/damadmin.  However, since these particular nodes are accessed through a vanityURL...