- Andrew Kos
- Bill Burlein
- Bryan Williams
- Celina Buczkowska
- Daniel Ryerson
- Jeff Brown
- John Kraus
- Joseph Mak
- Josh Durbin
- Mark Daugherty
- Matt Van Bergen
- Matthew Young
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
September 3, 2013 5:03 PM
Through the last 3 blog posts in this series we have learned what the CQ Component Maven Plugin is, some basic usage of the plugin, and some more advanced use cases. Now it is time to learn how to extend the plugin's functionality so that you can add your own transformers and widgets.
August 28, 2013 8:46 PM
One of the best parts about using Java and annotations to configure your dialogs is the ability to use objects to build nested dialog elements and to reuse pieces of a dialog. Throughout this blog we will use the example of a link object that contains a title and a path. The code follows:
August 27, 2013 9:39 PM
Introduced in the prior post in this series, the CQ Component Maven Plugin offers an idiomatic, annotation-based approach to the development of CQ Components. This post should help you get started using the plugin in your CQ project.
August 26, 2013 3:03 PM
Components, the building blocks of pages in the Adobe CQ Content Management System, are comprised of a number of parts. During development, one often finds oneself creating components by copying and pasting existing components and tweaking those aspects which makes them unique. This is typically easier than writing the parts from scratch as many of the parts, such as the dialog, the component node definition (.content.xml file), and the edit configuration, are XML serializations of JCR nodes and as such are cumbersome to construct. Further, when developing components with more robust authorability requirements, one finds oneself referring constantly to the CQ Widgets API documentation along with engagement in a healthy amount of trial and error in the development of Widget Dialogs. This is largely due to the fact that dialog.xml files are without schema- which means tooling is hard pressed to assist in their structural creation and validation- placing the burden of memorizing, or looking up, the properties germane to a Widget xtype on the developer.
August 20, 2013 1:16 PM
It’s time to break down the fundamental differences between using an Apache Sling selector and using an HTTP request parameter. They are often confused or used interchangeably, and I want to end the madness!
July 30, 2013 1:40 PM
Workflows are a really handy tool for distributing “work to be done” to your content team working in AEM. However, aside from the system administrators, no AEM users have the ability to see the holistic view of all “work to be done”. By holistic view, I mean visibility into the active instances of the various workflows you have running. In other words, only the administrator can supervise all active workflow tasks.
July 29, 2013 8:33 PM
Adobe Edge Inspect, formerly Adobe Shadow, was developed as a way of quickly previewing a web design on mobile platforms without publishing the associated files to a server. It allows IOS and Android Devices Mobiles to be paired to a computer and each device will display the same site using its native render and presentation modes. Rather than previewing a site optimized for mobile viewing on a desktop machine, Edge Inspect sends the file to paired devices, where it is rendered and displayed.
July 25, 2013 3:50 PM
This may sound familiar if you've spent any time at all developing with Adobe CQ5: your Maven build completes successfully and the resulting CQ package is installed, but you open your browser to view a page on your site and... stack trace.
June 24, 2013 7:29 PM
Adobe Experience Manager (formerly CQ5) is designed for building websites, and websites need to be found. Search engine optimization (SEO) is often overlooked during the implementation process, because it isn't defined up-front as a requirement. I’d like to share four actionable SEO best practices, specifically applied to building and using AEM components:
May 21, 2013 7:40 PM
Over the past year, I've been involved on an AEM (CQ) project that's unique in that a great amount of content/user interaction is driven by integrations with external systems. This particular implementation combines authored content with feeds from many REST/SOAP end points, JDBC calls, and a Spring/Hibernate/Spring-Dynamic Modules stack.
- Forecast for Adobe Summit: Sunny and Bright
- More AEM/CQ5 SEO Best Practices: Redirects, Vanity URLs, and XML Sitemaps
- Get Ready for CIRCUIT This Summer - Our Developer Conference
- Resetting the Value of Select Boxes in Safari for iOS onChange
- The Importance of Regression Testing
- Integrating Adobe Experience Manager with Google Tag Manager
- Say Hello to the New Application Support Team
- Strategies For Fixing Misplaced AEM/CQ5 Edit Bars
- CVE-2013-4810: a(nother) Hack that Needn’t Happen
- Responsive Image Rundown