h1

Watch out for Pitfalls – Things to navigate around if you do a Demo of Adobe CQ5.6

February 23, 2013

As mentioned in my last post Adobe cq5.6 (or AEM 5.6) was recently released. It is a very nice and feature rich product but while browsing the documentation and looking at the new examples, I discovered a couple of pitfalls on the way, mostly in the newly added features. I figured I’ll start recording them here for others to see as well, comment, suggest workarounds, etc.

Note: I have been using a windows 8 machine with a touchscreen while exploring AEM5.6

Geometrixx-Media

The geometrixx-media site is a great example of a responsive website that works well on your phone, tabled or desktop. The preview mode allows you to directly switch between different devices for a quick review of your site.

geometrixx-media

If you are demoing the page, I’d stay away from the following things (or remember the workarounds):

  • Don’t try to search on the geometrixx-media website. The search uses a regular jcr search within the geometrixx-media/en site, however, since the articles are all stored somewhere else (in the DAM through the new manuscript feature) the search does not return a result for articles. As an example:
    • Search for ‘blues festival’ and you’ll get a ‘your search did not return any documents’ response, however, ‘blues festival’ is in the first sentence on ‘/content/geometrixx-media/en/events/the-lineup-you-ve-been-waiting-for.html’
      In order to fix this, you’ll need to switch the search component to search in ‘/content/dam/geometrixx-media/articles’ instead (of course, then it does not search the regular content anymore, so modifying the search to search multiple paths would probably be a good idea) and then you may want to alter the search results display to point to the pages that are using the article instead of just the article in the dam since that exposes a text only version of the article (note to self: since the manuscripts/articles are in the DAM and can be exposed as clear text there it may be a good idea to think about how to protect these articles)
  • Don’t navigate away from the page you’re on if you are in preview mode. You will not be able to switch the device anymore and it will show up in the wrong device. There is a workaround for this by removing the cf# in the URL. Once you do that, browsing around and changing devices works like a charm. In case you forgot to remove the cf#, then just do a reload of the page to make everything work again.
  • Don’t switch over to the ‘Nexus 7’ device – while not a big problem, the collapsed menu oddly is displayed outside of the ‘viewable’ area of the page and therefore doesn’t make for a good demo.
    geometrixx-media-nexus7
  • The footer component does not work well – if you are looking at the site with a smaller window size or a small device, the pillars in the footer stack, however, since the main titles of the pillars are not linked anywhere the footer becomes unusable.

Windows 8 with a Touch Screen

I highly recommend avoiding the new touch UI with a windows 8 computer with a touch screen (that includes windows surface). Unfortunately the touch features do not work at all on these devices and even when using AEM5.6 with a mouse and a browser the new touch UI does not work well. CQ (AEM) can still be used with the classic UI – no problems there. The only thing that seems to be odd is if you are using chrome and are browsing the geometrixx website the selector .tablet is added to the URL. This is however only happening in chrome – IE and FF seem to be fine.

An easy way to get around this problem is to install virtual box and a linux operating system (for example Ubuntu) and then use firefox in that environment (or of course don’t use Windows 8 and a touch screen at all).

Is there More?

There are for sure other things one has to steer away from with the latest release, if you know of such a thing, it would be great to see some additional comments here in order for all of us to know what to avoid, how to get around an issue.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: