I started a post about the Adobe CQ5 Context/Clickstream Cloud last week, but before I get that out I feel inclined to mention the total ease with which we are able to collaborate with our client and our hosting & integration partner. After my team went to training last fall, we got a bit swamped with end of the year client “omigod I’ve got budget left that I need to spend in the next two weeks or I lose it forever” madness. That was followed by a super busy January and February, which I found was leading to some serious rustification of the skills we picked up in training. We managed to schedule some time with our CQ5 vendor partners who walked us through setting up access to their development repositories. They WebExed the process for us and I screen recorded. Today, one of my Lead Developers and I followed along with the video to document the process and to screencap the steps along the way. At the end of it, I was amazed at how simple it is to get up and running.
The beauty of this whole set up for us is that we can now own the look and feel of the UI from here in Chicago, our client manages all the content and product assets from Denver and our friends in Boston handle all the heavy lifting on infrastructure, form processing, Salesforce routing, etc. For the three parties involved, CQ5 is a platform that is going to enable us to collaboratively pursue our individual workstreams simultaneously. At any given time, we have landing pages, microsites, enterprise site updates going on. Over the years, this has been a mix of small static sites, landing pages and a huge CMS-driven product site all working through a cumbersome translation process to support upwards of 60 localized sites.
After working for decades in a world of code freezes and deployment windows, the fact that we’re now set up to maintain all these things inside a single platform with pretty much zero bottlenecks is pretty damn cool.