Archive for the ‘web’ Category


Ready for Sightly? The new AEM Templating Language

December 7, 2013

If you have been to one of the AEM Tech Events around the world you may have noticed Adobe is starting to heavily push their new templating language that hopefully will be available in AEM starting with the 6.0 release that’s scheduled for the beginning of next year. It also sounds like the templating language may be available for AEM5.6 as well. So what is it all about?

Have a look at the presentation by Gabriel Walt

And some of the videos from the Adobe@Adobe blog by Senol Tas

It seems the templating language code-named sightly will bring quite a big change to the developers working with AEM (CQ). The work is more shifted towards the front-end developers – the backend developers will be focusing more on java based development.


Video of Cedric Huesler’s talk: Reflection on AEM 5.6 release and preview of mid-year

May 24, 2013

If you missed Cedric’s talk at the Orange County CQ User Group meeting you can now watch it on youtube at


Reflection on AEM 5.6 release and preview of mid-year Release by Cedric Huesler

May 6, 2013

Cedric Huesler (the product manager of AEM/CQ) will give a talk at the OC CQ User Group meeting (May-22, 6pm at the offices of Capital Group)

Would be great if you can make it!


Webinar: Increase Online Sales with Persuasive Content through Magnolia CMS’ Shop Module

April 16, 2013

I will be moderating a Magnolia CMS webinar for the Open Source Magnolia Shop Module developed by fastforward and maintained by fastforward and magnolia. You can see a fully JCR based shop solution in action – join us for this great event!

Thursday, April 25, 2013
5:00 PM – 6:00 PM CET (11:00 to Noon, EDT)

register here >

Creating unique online storefronts that are secure, integrated with back-office inventory and catalog management and also easy for customers to use, is a challenge for any e-commerce integrator. The Magnolia CMS Shop module is a toolkit that adds e-commerce functionality to Magnolia CMS and makes it possible to enhance shop pages with compelling content that attracts new customers and increases sales.

Some of the key benefits of this integration include:

  • Products, product categories, prices and currencies are managed in Magnolia CMS’ AdminCentral.
  • All data is stored in the Data module except shopping carts in their own workspace.
  • Developers can get started quickly by using the default website structure containing shop, product detail and shopping cart pages.

On 25 April 2013, Ulrich Scheidegger, co-founder and managing director of fastforward websolutions and one of the developers of the Magnolia CMS Shop module, will present a webinar on creating Magnolia CMS-powered e-commerce websites without needing to add or run other shop software. This webinar will demonstrate how to build unique, branded online storefronts that are tightly integrated with Magnolia CMS’ intuitive editing and administration tools.

The webinar will be moderated by Ruben Reusser, CTO at headwire and expert in KonaKart e-commerce integrations. This webinar is extremely useful for Java and CMS developers of all levels, as well as IT professionals and system integrators interested in e-commerce solutions.


Device Detection Problems in AEM5.6 on Windows 8

April 13, 2013

When exploring AEMs default website geometrixx or geometrixx-media with a Windows8 device that has a touch screen (some of the newer laptops on the market for example)  you are either forwarded to a .tablet.html page (geometrixx) or the mobile site (geometrixx-outdoors). This seems to be a problem with the device detection that is part of AEM5.6. A tool called BrowserMap is used to perform a client slide test to determine your type of device and then you are redirected based on your device and a set of settings on the site.

The documentation from Adobe on how to set up your site for device detection can be found here

To see what AEM thinks your device is, you can go to http://localhost:4502/etc/mobile/browsermap/detect.html – with a Windows 8 Laptop with touch screen and Chrome you will get something like this as the output:


As you can see, the detection thinks the browser is running on a tablet.

Looking at the /content/geometrixx/jcr:content/cq:siteVariant node and the /content/geometrixx_mobile/jcr:content/cq:siteVariant node they both have a cq:variantFamily property with the value ‘geometrixx’. For the main website the media property is set to ‘browser, oldBrowser, highResolutionDisplay’, for the _mobile site to ‘smartphone, tablet, highResolutionDisplay’ – for whatever reason, this is not a String Array property but just a comma separated list and the node type is nt:unstructured – cq:siteVariant is the actual name that the browser detection is looking for.

What’s interesting to me is that on geometrixx, a selector called tablet is added and the browser stays on the same page while the setup in geometrixx-outdoors seems to be the same but there the browser is redirected to the mobile version of the site.

You can force AEM to use a specific device and bypass the BrowserMap detection by adding the parameter device=[device group name] to the URL. The supported device groups by default are:

  • smartphone
  • tablet
  • highResolutionDisplay
  • browser
  • oldBrowser (the latest version of Firefox is considered an oldBrowser)

The BrowserMap library is available on github at The testpage that’s available within AEM is also available online at – the library in AEM seems to be a bit more up to date since it can detect IE10 on Windows 8 (although it thinks that it does not have touch capabilities) – the one on github just reports it does not know the browser.

On the bright side, geometrixx-media does not need the browser detection since it’s a responsive design based website. I highly recommend going that route.


Setting up a Clean Instance of CQ5.6 without the Samples

March 13, 2013

While installing CQ5.6 I found a log entry that sounded quite interesting:

SlingSettingsServiceImpl Active run modes: [ author, crx2, crx3mongo, samplecontent ]

apparently (not sure if this is new in CQ5.6) you can pass in a runmode during installation to trigger different features of CQ to be installed or not.

Running CQ the first time with these arguments will not install the geometrixx samples at all and to me seems to be the better approach than installing CQ first and then uninstalling the geometrixx samples as suggested in various places and the security guide for CQ.

java -jar cq.5.6.jar -r nosamplecontent

After this installation, your copy of CQ (AEM) will be almost clean of any geometrixx atrifacts (there are however some geometrixx-media users that are left over, they are probably not contained in the example geometrixx code.

Other Available Options

It seems the following options can be set for installation purposes (one from each row, if non is selected the first one is taken):

  • author | publish
  • crx2 | crx3
  • crx3mongo | crx3h2
  • samplecontent | nosamplecontent

I gave the crx3 | crx3mongo runmodes a try but did not really get a working version of AEM out of that combination – I am sure there will be some sort of documentation from Adobe about those features soon 🙂


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


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.


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.
  • 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.