Where CQ5 fits in the Adobe Digital Enterprise Platform

If you are a follower, user, or customer of Day Software’s Communique (CQ) web content management software, by now you know that Adobe Systems acquired Day in late 2010.  Since then, Adobe and the talented folks that came over from Day Software have been focused on integrating the various components of the CQ stack into the future direction of Adobe’s Digital Enterprise Platform.

With the official announcement of the Adobe Digital Enterprise Platform for Customer Experience Management in June, you may be confused with updated product terminology and wonder how and where the Day CQ products you may currently use fit in the new platform.  To better understand this, let’s take a step back and review how Adobe is evolving the platform.

In a world of always connected, multi-channel, multi-touchpoint consumers, the ability to deliver rich, immersive digital interactions across the many devices they may use to connect to that content has been paramount to any organizations success.  Day Software’s web content management system (WCMS), CQ5 has always been known as a leader in delivering this type of flexibility and functionality.  The integration with the broader Adobe enterprise product set took the CQ5 JCR content repository and made it the core of the new Adobe Digital Enterprise Platform (ADEP), replacing the existing LiveCycle repository.  ADEP also uses the existing Day web applications (now called Web Experience Management) and collaboration tools and extends the functionality significantly by integrating the Adobe Flash, Flex Framework and the powerful Online Marketing Suite powered by Omniture.

So the good news is that as an existing Day CQ5 customer, you will be very familiar with the core tool set as very little has changed for you.  The biggest change comes in how Adobe will package and license the capabilities going forward.

For additional information, you can read:

• Adobe Web Experience Management Solution Brief
• Adobe Digital Enterprise Platform Solution Brief
• Blog post by Tim Anderson, ITWriting.com