Find out more about our consulting services. McLean. Boston. New York.
In making the case for an expensive software integration, short term vision is rarely going to bare out the costs. But midterm expenditures show, from a variety of viewpoints, the value and utility of an integration with the Adobe CQ5 platform. The coming updates (CQ5.5) on the venerable Adobe WCM/CMS will make an even more intuitive authoring environment that behaves more and more like the applications users utilize on a daily basis.
As an IT manager, the last thing you want to see is ANOTHER integration in your enterprise. CQ5 is different though: it lightens the load because it’s a self-contained system that takes full advantage of the Java technology stack. This means that you can stand up your CQ5 enterprise in a modular fashion, giving you a cohesive system without worry about being tightly coupled to the rest of your enterprise systems. It also allows you to integrate CQ5 with the rest of your backend systems at a pace that suits your enterprise.
From the point of view of the UX designer, CQ5 is a tool like many other WCM’s which can integrate any vision for your website or web application. CQ5 is flexible enough to allow the implementation to control what goes where and how authorable content appears. CQ5 provides a seamless platform for content governance. The design and implementation of the CQ5 templates, pages, and components, ensure that there is no way for unauthorized users to modify anything other than the content on designated areas, ensuring content approvers control what content is actually published. CQ5’s templating model ensures that new pages look and behave just as intended by the designer, controlling what kinds of content can be placed on different areas of the page.
As a business user or brand manager, CQ5 provides a nearly instant platform for delivering new or modified content to your users and customers. In a traditional application framework such as Struts, Spring, Java ServerFaces, PHP, ASP.NET, Cold Fusion, etc., business users need to change content, often resulting in a change order that has to be delivered to the software development department or software contractors. But with CQ5, as soon as you have your change requirements firmed up, content authors can make these changes and content approvers can publish them. Changing content on a CQ5 web page is frequently as easy as editing a Word or Power Point document.
A past customer was spending in the region of one million dollars a year maintaining about 400 hundred JSP pages with their out sourced IT partner, who on average took 3 weeks to turn around even the simplest modifications, such as changing verbiage on the page or swapping out a Flash presentation.
Now: imagine an enterprise where the manager of any given department decides that they need to update some content or revise some media. As soon as they know what content or media needs to be updated, they can begin editing page content and uploading new images, media, or files to the CQ5 Digital Assent Manager (DAM) and inserting those new files into new or existing pages. Then it’s just a matter of submitting the new or updated content to the content approver for publishing.
The publishing workflow can be as complex or as simple as needed, including content approvers from any corporate department, such as legal, IT, marketing, etc. Once the content approver(s) receive notice of a change and can approve it, the new content is published to your live site for your customers.
CQ5 is a complex platform and learning how to wield it to make real business changes is difficult. If you have any questions about CQ5 functionality, or want to know how NavigationArts is optimizing the platform, feel free to leave a comment below.