halifax adobe user group - adobe experience manager (cq)

22
Adobe CQ/AEM & the dal.ca experience James Covey [email protected]

Upload: todd-yeadon

Post on 18-May-2015

315 views

Category:

Technology


4 download

DESCRIPTION

Presentation by James Covey to the Group on March 19, 2014

TRANSCRIPT

Page 1: Halifax Adobe User Group - Adobe Experience Manager (CQ)

Adobe CQ/AEM& the dal.ca experience

James [email protected]

Page 2: Halifax Adobe User Group - Adobe Experience Manager (CQ)

2009

• Dalhousie dal.ca web revitalization project kicks off.

• October: from among 7 vendors over a period of 2 months, selected Day CQ to publish dal.ca.

• so did Adobe—for adobe.com.

Page 3: Halifax Adobe User Group - Adobe Experience Manager (CQ)

where we were (2009)

• 150 websites hosted on legacy CMS (Serena Collage, EOL announcement 2008)

• 150 additional websites deemed “core” to Dal’s brand hosted on a mix of systems

• dated (2004) design

• web governance needed to be updated

Page 4: Halifax Adobe User Group - Adobe Experience Manager (CQ)

where we wanted to go

• new performance & governance framework

• new CMS for all* dal.ca sites (migrate 300 sites)

• new design / IA / UX

• new publications (program pages for prospective students)

Page 5: Halifax Adobe User Group - Adobe Experience Manager (CQ)

2010

• October: dal.ca main site relaunched on CQ with first 7 sub-sites, in new design.

• also in October…

Page 6: Halifax Adobe User Group - Adobe Experience Manager (CQ)

…this happened.

Page 7: Halifax Adobe User Group - Adobe Experience Manager (CQ)

fast-forward 2 years…

Page 8: Halifax Adobe User Group - Adobe Experience Manager (CQ)

formerly known as…

• Experience Manager = CQ + Scene7

• Analytics = Omniture SiteCatalyst

• Target = Test&Target

• Campaign = Neolane

• Social and Media Optimizer are essentially new

Page 9: Halifax Adobe User Group - Adobe Experience Manager (CQ)

the CMS solution space

Page 10: Halifax Adobe User Group - Adobe Experience Manager (CQ)

“Digital Marketing Titans”

• IBM

• Oracle

• Salesforce

• Adobe

Page 11: Halifax Adobe User Group - Adobe Experience Manager (CQ)

what is CQ/AEM for?

• “Organize, manage, and deliver creative assets and other content across digital marketing channels”

Page 12: Halifax Adobe User Group - Adobe Experience Manager (CQ)

product modules

• Digital asset management

• Web content management

• Social communities

Page 13: Halifax Adobe User Group - Adobe Experience Manager (CQ)

why we chose CQ

• Needed enterprise-class system (100s of websites, 10s of 1000s of pages)

• Concern that higher-ed niche systems weren’t as powerful and wouldn’t stay current

• Lack of Microsoft/.NET expertise at Dal (2009)

• Authors wanted a much-improved experience

Page 14: Halifax Adobe User Group - Adobe Experience Manager (CQ)

CQ: technology stack

Page 15: Halifax Adobe User Group - Adobe Experience Manager (CQ)

CQ: servers

Page 16: Halifax Adobe User Group - Adobe Experience Manager (CQ)

CQ: development

Page 17: Halifax Adobe User Group - Adobe Experience Manager (CQ)

CQ: authoring

Page 18: Halifax Adobe User Group - Adobe Experience Manager (CQ)

CQ: administering

Page 19: Halifax Adobe User Group - Adobe Experience Manager (CQ)

CQ: organizational fit• Organizations that have large amounts of

structured content to deliver online

• Local: Dalhousie, New Brunswick

• Media: Newsweek, Vanity Fair

• Organizations that have multi-channel/international publishing needs

• Hyatt, McDonalds

Page 20: Halifax Adobe User Group - Adobe Experience Manager (CQ)

“Why Not Adobe WEM?”

• Adobe the company is hopelessly disorganized

• CQ is a developer's playground

• Adobe's suites are mostly mythical

Page 21: Halifax Adobe User Group - Adobe Experience Manager (CQ)

where we are now

• 301 sites on CQ (234 mobile-compatible)

• 106 sites being migrated to CQ

• 72 sites being built with CQ

• wait-and-see on DAM and SoCo modules