Archive for February, 2013

h1

Adobe CQ Meetup about migration from one CMS to another on March-20

February 24, 2013

Gaston Gonzales will present on different approaches to migrate content from a cms to CQ 5. If you are in the Orange County Area it should be worth while stopping by.

You can sign up for the meetup and see more information at http://www.meetup.com/OC-CQ-Sling-JCR-User-Group/events/106181442/

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.

h1

Adobe CQ5.6 First Impression

February 22, 2013

Adobe released it’s new version of the Communique suite (5.6) on Feb-8-2013. The release can be download from daycare or licensing.adobe.com for current customers. So what’s new in this release that will make you want to upgrade your project?

New in CQ5.6

1: It’s called AEM (Adobe Experience Manager) now

While I guess not that important, it’s going to be interesting if the name is going to stick – there were other occasions where Adobe tried to rename this product and at the end, we all keep calling it Adobe CQ (yes, we finally don’t call it Day CQ anymore).

2: Responsive Design Support

If you download the latest release and navigate to the geometrixx-media example webpage and switch over to preview mode, you’ll see a dropdown allowing you to easily and quickly change the device that you are using to view the site. Also, the geometrixx-media example is now a nice example of a responsive design website and a good starting point for your own projects since more and more people are going the route of designing tablet-first websites.

3: Adaptive Images Support

The inclusion (in the geometrixx-media code base) of an adaptive-image component is a great addition to the component libraries available from the get-go in CQ. The adaptive image component helps you minimize the size of a page if browsing with a smaller device (mobile phone) by downloading a version of the image that matches the screen size of the device instead of using the browser to scale the image. Also, those pesky retina displays will get a different version of the image served to them leaving  a better impression with your customer.

4: Launches

One of my favorite new features in CQ (sorry ADEP (oh now, it’s called AEM now)). You can now essentially branch your site structure and work on a future version of the site while still altering the current version of the site. The branch and the current version are kept in sync over the LiveCopy functionality. You can then launch your new content – the current copy of the content is updated at that time. There feature also makes use of the workflow package concept to allow you to publish all the pages you changed in one bulk transaction.

The sidekick allows you to switch between the current content or a branch and also has the ability to promote your branch.

Note: there are some issues with the out of the box components not working right in the branched mode. An example of this is if you go to the gemoetrixx example site and branch for example the ‘products’ section off you’ll see that the navigation is not working anymore. I heard some rumors that Adobe is addressing these issues.

5: Manuscripts/Articles

There is a new concept in 5.6 of content that does not live in the regular site hierarchy – you can author the manuscripts/articles with a wiki style editor and then include them anywhere on your site (great examples in the geometrixx-media site), select how many columns you want to use for the display of these articles and also add other content/images between every paragraph. It’s a great demonstration of authoring some sort of content outside of the regular site structure and reuse of that information in multiple places.

6: Publications

5.6 now allows you to create magazines and publish them through an Adobe service to your mobile or tablet devices and the App Store. Seems to be a great new feature and I’ll defiantly will spend more time on this one to learn how it actually works. It may be a nice feature to publish an internal or external magazine for a company.

7: New Code Editor in CRXDE|lite

CRXDE|lite got a new code editor – gone are the times of grayed out code, shadows, etc. Great to  see that this issue has been addressed.

Many more Features

The official release notes can be found here. It also includes a list of the new features:

http://dev.day.com/docs/en/cq/current/release_notes/overview.html