WCM tagged posts

August 30, 2017 Posted in Blogs, ECM

In 2008, I worked on a Web Content Management (WCM) project for Accenture BPO. The client of Accenture spent 1.5 M on purchasing the license and package of the WCM system called Day Communique / CQ. The core team of Day Software contributed to Apache Jackrabbit – an open source content repository, then created the commercial CQ, which includes a content hierarchical repository CRX, an IDE CRX DE and the browser-based authoring and deployment interface. The unique tight bundle of content repository, IDE and smooth web-based deployment environment gains quite a bit clients quickly, especially for those who have deep pocket. In 2009, Day released CQ 5. In 2010, Day CQ 5 was acquired by Adobe and renamed to Adobe AEM (Adobe Experience Manager).

It has been ten years! Now Adobe AEM released ver...

December 23, 2014 Posted in Blogs

Our utility client has a large site with numerous sub-sites that need to be migrated to a new million dollars WCM (Web Content Management) based system. The new site is based on Adobe CQ* which is a neat WCM system.

The problem is the migration can’t be done in one day. In a large organization, the way it works is to migrate sub-sites one by one. The procedure can take a few months or longer. So we need to bridge the legacy site and new one to help on seamless migration. When user accesses the site, user may access the bookmarks or favorite links that they stored in their browsers. Those bookmarks still point to legacy sites even there are newly migrated sites available. What we need do is to find the match in between and redirect the legacy URLs to the new one running on new WCM system.