Ensuring Successful Maven Builds When Installing OSGi Bundles

    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.

    posted by Mark Daugherty

    4 SEO Best Practices for Adobe Experience Manager/CQ5

    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:

    posted by Ryan Lunka

    Descriptive JMX Beans in AEM/CQ

    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.

    posted by Josh Durbin

    Invisible requirements within Business requirements

    May 15, 2013 8:17 PM

    Testing in an author environment can have its own challenges. Component's configurations need to be tested at this level to achieve correct content authoring.  So, when faced with fields upon fields of data for each component needing to be validated, more often than not we are left with little to no requirements to validate these fields.

    posted by Nadia Maciulis

    Building a better Options Predicate

    May 8, 2013 9:00 PM

    There is often a need to search through Digital Assets (pictures, documents, etc.) in any content management system. CQ5 provides several ways to search within the DAM. You may use the Query Builder API with Java or REST as described here:

    posted by Joseph Mak

    Javascript, This, and You.

    April 25, 2013 7:38 PM

    The this keyword in Javascript is often a very confusing hurdle for programmers new to the language. This behaves a little differently than what people are often used to. The object that this refers to changes depending on the context in which the keyword is used. 

    posted by Matthew Young

    Extensionless URLs with Adobe Experience Manager

    April 8, 2013 12:41 PM

    Many SEO experts argue that as a best practice, your website’s pages should have extensionless URLs. For example, www.mysite.com/page-about-dogs/ would be more SEO optimized than www.mysite.com/page-about-dogs.html. Discussing the merits of this rule is another post for another day (look for one later), but sometimes this requirement just comes up. It may seem a little daunting at first, given the importance of extensions in Apache Sling, but I’ve put together a fairly simple solution that will allow you to use extensionless URLs in Adobe Experience Manager. This solution also gives you more flexibility than the "out of the box" way to handle this in CQ5.5: The Link Checker Transformer.

    posted by Ryan Lunka

    The Life of a Tester in Adobe CQ World!

    April 4, 2013 3:03 PM

    Every time I see a component dropped in my testing bucket, my brain starts the process of how to think like a user.  There are two main types of users in CQ, which are author and visitor. As an author, I need to think about the authoring experience, so as I am testing, I think about the following:

    posted by Nadia Maciulis

    Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System

    February 25, 2013 3:50 PM

    On my latest project, we had a requirement for creating two layout control components: columns and tabs. In the implementation of these components, we quickly found out CQ is built with the rigid assumption that paragraph systems will never be nested. We wanted the visual layout power and control of allowed components offered by paragraph systems in our layout components, so we had to include nested paragraph systems in our column and tab implementations.

    posted by Andrew Kos

    Google Analytics and AEM: No JavaScript? No Problem.

    February 20, 2013 4:05 PM

    Many organizations use Google Analytics as either their sole web analytics platform or as a supplement to another product like Adobe SiteCatalyst. Google Analytics is a great tool, but its standard use requires that site visitors have JavaScript enabled. If your organization’s growth strategy includes business in developing nations, you are likely finding that a significant portion of Web traffic is via mobile phones that do not support JavaScript. To increase the integrity of your analytics data, you should implement a solution that counts these otherwise uncounted visitors.

    posted by Ryan Lunka

Recent Posts

Blog Archive