Blog
.
Ross Raphael
Adobe CQ5.5: A Preview of the Wicked Functionality
November 17th, 2011
Earlier this week Adobe hosted the DC Area CQ5 Users Group. The keynote of the evening was from Day Software founder and current CQ5 brand manager Cedric Heusler, previewing some upcoming functionality in CQ5.5.
On the sexy front, CQ5’s authoring interface moves closer and closer to a Windows application like user experience. They’ve added CTRL-Z functionality to the Authoring interface and in the demo, this functionality looks like it’s done and ready for prime time. You can undo any set of changes made during the current authoring session, regardless of the change. Properties, new components on the page, component property edits, etc. They can all be undone.
In the last year, Adobe acquired Omniture and you can expect to see significant Omniture functionality in CQ5’s Campaign tab and marketing functionality. It’s still up in the air if we’ll see any Site Catalyst functionality or some of Adobe’s other eRetail focused capability, although I did see some eRetail focused components in Cedric’s Sidekick when he was showing functionality in their new Geomatrixx site.
Adobe is also adding Bridge functionality to connect the Adobe Creative Suite of applications to a CQ5 DAM.
Cedric also demonstrated some Amazon Cloud functionality, by standing up a new VM with CQ5 already running in a matter of a couple of minutes. Cloud functionality was a big focus last month at Adobe Max where Adobe announced their Creative Cloud. So it looks like plenty of sizzle and steak for the coming year in CQ5.
.
Tags: adobe cq5, cloud computing, Marketing
2 Responses 
Hi, i am working on Facebook integration with Adobe CQ5.
Please help me for these 2 points
1. can we integrate CQ5 using fconnect so that the logged in users in Facebook can access the website without logging again ?
2. Facebook app integration – means how can we integration Facebook with CQ5 website so that only a component from website will appear on Facebook.
Komal, I haven’t worked with fconnect or developing Facebook apps, but I don’t see why you couldn’t write some kind of custom connector. However, keep in mind that CQ5 is RESTful so you’ll need to use a cookie or some other way of logging into the application you’re developing with CQ.
You might be best served, delivering content to your Facebook app via webservice from the CQ OSGi container that pulls content from the nodes you’re trying to deliver.