keeping up to date with the adobe aem 6 documentation

March 3, 2015

Adobe puts out great documentation about AEM6 on docs.adobe.com – however, to keep up to date with the latest changes and recommendations is sometimes not that easy. We’re proud to announce our adobe doc diff website: http://adobedocsdiff.headwire.com/

The site indexes the documentation on a daily basis and can send you an email with the latest changes or you can just go back to the site from time to time and see what changed since you last visited.

Also check out the side by side view of the site (for example http://adobedocsdiff.headwire.com/sitediff/sidebyside.jsp?date=2015-03-03#ui-recommendations.html) providing you with the previous version the current version and a diff view of the content from both.


AEM 6 SP2 Available

February 6, 2015

Adobe released Service Pack 2 for AEM6. The release notes indicate that jackrabbit oak was updated to version 1.0.9

The following statement in the release notes may also be of interest:

Preannouncement: Removal of CRX2 in next AEM release

AEM 6.0 ships with a compatibility option to run the server with the repository technology that is used in AEM 5.6.1. The documentation also refers to it as CRX2 or Apache Jackrabbit 2.x.

AEM 6.0 introduces the next generation Java Content Repository that the documentation refers to as Apache Jackrabbit Oak or CRX3. It comes with many significant improvements, mainly with regards to scalability, performance and optimizations for AEM capabilities. For more info, please see Introduction to Oak.

Adobe is planning to remove the compatibility option in the next release of Adobe Experience Manager. The update process of the next release will contain the option to switch to the Oak-based repository during the update, that can be used for customers that want to update from AEM 5.x or AEM 6.0 using the compatibility option.


dialog conversion tool for classic UI to CoralUI released

February 4, 2015

Adobe released their upcoming dialog conversion tool that lets you convert a classic AEM dialog to the new CoralUI dialog structure. The documentation for the tool can be found on the docs.adobe.com site at http://docs.adobe.com/docs/en/aem/6-0/develop/dev-tools/dialog-conversion.html

The package is available on package share


AEM OSGi Dependency Map

January 30, 2015

AEM contains a lot of OSGi bundles. We figured it would be nice to see how the bundles are connected.


you can find the dependency map for AEM5.6.1 and AEM 6.0.1 at http://www.cqblueprints.com/tipsandtricks/osgi-dependencies.html


dynamically created and google indexed

January 21, 2015

According to google, js generated pages should now be indexed by their crawler as well. To test this out, we created a small test site that keeps all the content for the site in a json file and then uses handlebars to output the html for the site.

The html for the site only contains a body tag and a placeholder.

click here to visit the sample site

Read the rest of this entry »


Moving to AEM6

August 20, 2014

I have not posted much on this blog for a while. First, I was waiting for AEM6 to come out, then I realized there is lots to learn on the AEM6 front – I finally decided to start a secondary blog that just focuses on learning about AEM6. Things I encounter while trying to get up to speed with the new major milestone release.

The new blog can be found here: learningaem6.wordpress.com



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.


Get every new post delivered to your Inbox.

Join 45 other followers