Typically, versioning in AEM is something only thought of in the context of pages. In fact, the common way in which one works with versioning is baked into the Touch UI Sites console which further couples the two. However, versioning isn’t limited to pages. Any node in the JCR can theoretically be versioned. In this …
In Part 3 we discussed a series of questions that are meant to guide the architecting of the actual components. We broke them down based on the Authorability of the components and then those tasks that are specific to what a developer would actually do. In this final section, we will discuss an approach to …
In Part 2 of our series, we discussed 3 fundamental steps that should be taken to group or organize the needed components for the website. In Part 3 we will discuss a series of questions that are meant to guide the architecting of the actual components. Here are a set of questions and considerations that …
In Part 1 of our series, we introduced a series of documents that we use to help define what will be done for the given site. We defined a variety of components, talked about the page templates (content), and extolled the virtues of always considering the authors when you do AEM development. Part 2 will …
We faced a problem where a project we were working on wanted to use features in the cq-6.3.0-featurepack-10262-1.2. We ran into an issue where the 6.3.0-featurepack package contains configurations to Demandware. The reason this was an issue is because our project had configuration nodes for Demandware as well. One solution would have been to uninstall …