What is Adobe CQ5?
Adobe CQ5 (now renamed as Adobe Experience Manager) is a robust web content management system (WCMS) based on Java. It enables users to design, develop, author and manage digital properties to provide sophisticated digital properties (websites, mobile sites and apps) and deliver consistent user experience across multiple channels.
How CQ5 actually works?
Mainly CQ5 servers run on two instances – Author instance and Publish instance.
- Author instance: Content authors are connected to Author instance to create, edit and optimize web pages/sites using existing components (created by CQ5 developers), website content, and more. Simple / Complex workflows can be enabled to ensure that only approved content goes live.
- Publish instance: Once the pages are built, the pages will be published to the publish instance for the site visitors to view. The authors can test in author instance, and publish to publish instance. There could be multiple author instances and multiple publish instances to accommodate load balancing.
Another key component is Dispatcher. Dispatcher is used for caching content and generating it dynamically and load-balancing to achieve HA (High Availability).
What is the technical background of CQ5?
CQ5 is based on Java and uses JCR (java content repository), Apache Sling RESTful framework, and OSGi framework.
- JCR is where all the content is stored.
- Apache Sling RESTful framework to map that content with corresponding url requests. You can expose Sling URLs for access from outside CQ5 instance as well.
- OSGi framework (Apache Felix as container) enables it to control (start and stop) each module independently. You deploy your java code into OSGi bundles and manage these bundles independently from the AEM Console.
How to manage multilingual and multinational sites?
CQ5 has a feature called Multi-Site Management (MSM). It enables you to develop, edit and optimize different websites in different languages for different regions (domestic/international). Organizations can even build websites for each of their brands and serve local needs. With multinational presence of many brands, there are times when you need to serve the content in local languages. There are third party companies like translations.com which can provide translations for your content and have built-in connectors from inside CQ without manually managing the content for translations
How to build mobile sites and apps in CQ5?
With Adobe Experience Manager 6.0, the site can be optimized automatically for responsiveness. You can preview the site in an emulator, which replicates a mobile device (phone / tablet), while authoring a page for your mobile website. You can also switch between different emulators to know how the end UI is going to be. This will tremendously reduce the testing time and allows you to launch responsive site quickly.
Adobe Experience Manager, with its OOTB (out-of-the-box) components, enables you to render mobile pages specifically for a device based on its features. It has categorized all the mobile devices into three groups including smart, touch and feature. You can create your own groups. When users access your mobile site from their device, CQ5 detects the device and offers the page layout that corresponds to the device group it belongs.
To develop mobile apps, you can use Adobe Experience Manager Apps feature. AEM allows you to create native apps and hybrid apps by accessing PhoneGap enterprise features, which integrated within AEM. You can also create apps specific to your brands and marketing campaigns specific to the region.