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 which enables organizations to create websites, manage content and digital assets of the website through several medium like mobiles, web browsers, tabs, desktops and more. AEM also helps businesses to target right customer with right opportunity at 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
Started by a Swiss company Day Software
CGI Scripts for Netscape Enterprise Server
Day CQ 2.0
Early 2000
Standalone application (single binary)
C Programming Language
HTTP Server embedded
File system based page (content) storage
Day CQ 3.0
Early 2000
Communique 2 rewritten as a Web Application in Java
HTTP Server separated out (birth of CQSE)
Content Bus storage (connectors for various file formats, databases, etc
Day CQ 3.5
2002
Lot of bug Fixes
Day CQ 4.0
2005
Content Bus storage over JCR (CRX 1.0)
Two Web Applications: CRX and CQ
Day CQ 4.1
2006
Lot of bug Fixes
Day CQ 4.2
2008
Lot of bug Fixes
Day CQ 5.0
2008
Complete Rewrite of (almost) everything
Day CQ 5.2
2009
Lot of bug Fixes
Day CQ 5.3
2010
Lot of bug Fixes
Adobe Day CQ 5.4
2011
Day Software Acquired by Adobe and first version of CQ released under Adobe.
Managing Websites for Mobile Devices
Managing the CQ Workflow Inbox on the iPhone/iPad
Authoring with the iPad
Campaigns
Reporting
CRX Clustering
Annotations
Video Component
Carousel Component
Working with Workflows
Forums
Community Console
Profiles
Adobe Day CQ 5.5
2012
New architecture- OSGI based architecture.
New undo/redo functionality while editing content.
New Analytics Framework based on an integration with Adobe SiteCatalyst.
New integration with Adobe Search&Promote.
Improved integration with Adobe Test&Target.
Improved Campaign Manager UI.
Integration with Adobe Scene7.
XMP metadata write-back for selected file formats.
CQ DAM Proxy and Proxy Workers.
Using a Proxy to Integrate with InDesign Server.
Remote server monitoring and management via Java Management Extensions (JMX).
Page Exporter
Adobe Experience Manager (AEM) 5.6
2013
Adobe renamed CQ5 with new Name Adobe Experience Manager.
Introduction to Touch UI .
Offloading Jobs.
Adobe Experience Manager (AEM) 6.0
2014
Replaced CQSE with Jetty
New HTML Template language (HTL)- formerly known as Sightly
Jackrabbit Oak (aka Jackrabbit 3)
Upgrade CRX repository from CRX 2.0 to CRX 3.0
Deprecated the concept of reverse replication and introduced UGC (User Generated Content) or social communities.
Touch UI became functional.
New implementation for Social Component Framework (using handlebar JS template Language ).
Adobe Experience Manager (AEM) 6.1
2015
Improved Touch UI Authoring interface(usable)
Introduced Cold standby Topology for disaster recovery.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Leave a Reply