Adobe Experience Manager (AEM)/ Adobe CQ5 History

AEM history or Adobe Experience Manager (formerly known as CQ5) history, if you break the work history it contains a story, let’s see the story behind most successful content management system AEM(Adobe Experience Manager), how it was started and what important features are added to each stage.

(Day Communiqué) CQ5 was originally started by a Swiss company Day Software in early 2000 with the name “Communique”. CQ is the short form of “Communique”.

Day Software was acquired by Adobe Systems on 28 July 2010 for US$240 million after Day CQ 5.3 release.

Product History:-

Adobe Communique (Adobe CQ5) currently known as Adobe Experience Manager (AEM), is a web-based content management system that enables organizations to create websites, manage content and digital assets of the website through several mediums like mobiles, web browsers, tabs, desktops, and more. AEM also helps businesses to target the right customer with the right opportunity at the right time through personalization (Campaigns).

Below is the detailed list of AEM history:-

Product Name	Release Date	High Lights
Day CQ 1.0	Early 2000	1.    Started by a Swiss company Day Software 2.    CGI Scripts for Netscape Enterprise Server
Day CQ 2.0	Early 2000	1.    A standalone application (single binary) 2.    C Programming Language 3.    HTTP Server embedded 4.    File system based page (content) storage
Day CQ 3.0	Early 2000	1.    Communique 2 rewritten as a Web Application in Java 2.    HTTP Server separated out (birth of CQSE) 3.    Content Bus storage (connectors for various file formats, databases, etc
Day CQ 3.5	2002	1.    A lot of bug Fixes
Day CQ 4.0	2005	1.    Content Bus storage over JCR (CRX 1.0) 2.    Two Web Applications: CRX and CQ
Day CQ 4.1	2006	1.    A lot of bug Fixes
Day CQ 4.2	2008	1.    A lot of bug Fixes
Day CQ 5.0	2008	1.    Complete Rewrite of (almost) everything
Day CQ 5.2	2009	1.    A lot of bug Fixes
Day CQ 5.3	2010	1.    A lot of bug Fixes
Adobe Day CQ 5.4	2011	1.    Day Software Acquired by Adobe and the first version of CQ released under Adobe. 2.    Managing Websites for Mobile Devices 3.    Managing the CQ Workflow Inbox on the iPhone/iPad 4.    Authoring with the iPad 5.    Campaigns 6.    Reporting 7.    CRX Clustering 8.    Annotations 9.    Video Component 10.Carousel Component 11.Working with Workflows 12.Forums 13.Community Console 14.Profiles
Adobe Day CQ 5.5	2012	1.     New architecture- OSGI based architecture. 2.    New undo/redo functionality while editing content. 3.    New Analytics Framework based on an integration with Adobe SiteCatalyst. 4.    New integration with Adobe Search&Promote. 5.    Improved integration with Adobe Test&Target. 6.    Improved Campaign Manager UI. 7.    Integration with Adobe Scene7. 8.    XMP metadata write-back for selected file formats. 9.    CQ DAM Proxy and Proxy Workers. 10.Using a Proxy to Integrate with InDesign Server. 11.Remote server monitoring and management via Java Management Extensions (JMX). 12.Page Exporter
Adobe Experience Manager (AEM) 5.6	2013	1.    Adobe renamed CQ5 with a new Name Adobe Experience Manager. 2.    Introduction to Touch UI. 3.    Offloading Jobs.
Adobe Experience Manager (AEM) 6.0	2014	1.    Replaced CQSE with Jetty 2.    New HTML Template Language (HTL)- formerly known as Sightly 3.    Jackrabbit Oak (aka Jackrabbit 3) 4.    Upgrade CRX repository from CRX 2.0 to CRX 3.0 5.    Deprecated the concept of reverse replication and introduced UGC (User Generated Content) or social communities. 6.    Touch UI became functional. 7.    New implementation for Social Component Framework (using handlebar JS template Language ).
Adobe Experience Manager (AEM) 6.1	2015	1.    Improved Touch UI Authoring interface(usable) 2.    Introduced Cold standby Topology for disaster recovery. 3.    Introduced transient workflows. 4.    A lot of improvements for the Touch UI Interface. 5.    For Complete List Click Here.
Adobe Experience Manager (AEM) 6.2	2016	1.    A lot of User Interface Improvements. 2.     Dashboard for Monitoring Queues. 3.    Introduction of content fragments. 4.    Introduced editable templates using the template editor. 5.    For Complete List Click Here
Adobe Experience Manager (AEM) 6.3	2017	1.    Introduction to Production-ready components (Core Components) 2.    Experience fragments 3.    Stable online revision Clean up(online tar compaction) 4.    Bulk workflow 5.    Performance and scale enhancements 6.    Community ideation 7.    Source user-generated content 8.    3D assets 9.    Asset templates 10.  High-quality file format and color management
Adobe Experience Manager (AEM) 6.4	2018	1.    Style System 2.    Short Codes 3.    Experience Fragments Building Blocks and Experience Fragments integration with Adobe Target 4.    Structured Content Fragments and Summarization 5.    TouchUI Workflow Editor 6.    Metadata Export and Import 7.    Cascading Metadata Rules 8.    Asset Reports 9.    AEM Smart Tags and Smart Translation Search

Technologies involved in CQ/AEM

Technology	Features
Apache Jackrabbit	open-source repository (following JCR specifications) CRX repository
Apache Felix	OSGi container
Apache PDF box	indexing of the pdf files
Apache shining	only for hosting gadgets
Apache Aries	JMS functionality
Apache tika	Indexing of all items/binding content except pdf
EXTJS	to implement user interface components
JQuery	JS framework
Less.js	javascript framework
CQSE-(not open source)	internal WAP