Agency training Way of working around Experience manager

November 01, 2013 _Sector Confidential 1

Agency training – Way of working around Experience manager Philips Component Library

Roel de Laat, Danielle Schmit, Stacey Salazar Digital Services, B2B

March 2015


Our Adobe EM Pages


Typical development approach

Typical EM Site

Wireframes

Designs

Build HTML

Build template

Build/extend components

Testing

Compose/assemble master

Localize

Training


they look the same


Structure the

choices

Clearer differentiation in

options

Explain benefits


Why generic components are important


Because you can create multiple experiences

Stacking them differently and using

“theming”



BP_18

GC_11

PC_02

GC_04

PC_05

GC_04

N_11



From build to re-use The

component library

Intake process

Re-use + Enhance

Build

CL

LI

HC

CO

Different projects create new

components

Components are added to the

library

Review is done using library and

input from request

Decision made on re-use of

components


Typical vs Library approach

Using library approach

Typical CQ Site

Wireframes

Designs

Build HTML

Build template

Build/extend components

Testing

Compose/assemble master

Localize

Training optional


Why are we re-using components?

• Cost: Less investment needed to design and build. Time: • Faster time to market • Faster time to measure and respond • Faster time to revenue • More time available to focus on the content

• Quality: Higher quality and stable platform


2012 2013 2014

Have a silo approach in experience,

organization setup and technical

landscape

Developing a landscape of common digital

marketing capabilities

Creating a flexible landscape with re-usable

components to drive marketing innovation and relevant content

2013 2014 2012

http://www.philips.co.uk/componentlibrary/home.html

15

Pages

Unstructured content

Static Images

Documents

Formerly known as: CQ 5.6

Content Management System Adobe Experience Manager

CQ

16

Page templates

Page types

Components

Themes

Renditions

Generic template

Homepage template

Product detail template

Product Group template

Event template

Content Management System Adobe Experience Manager (CQ)

17

Page templates

Page types

Components

Themes

Renditions

Generic template: Topic pages Innovation pages About pages Consulting pages ...


18

Page templates

Page types

Components

Themes

Renditions

Generic template Topic page


19

Generic Content Components

GC04 – Columns

GC11 – Text

GC13 – Image

Social Components

SC01 – Youtube

SC02 – Facebook feed

SC04 – Twitter feed

Other

MH01 – Masthead

N11 – List of links

U54 – Eloqua form

Visit component library ►

Components


20

Page templates

Page types

Components

Themes

Renditions





21

Page templates

Page types

Components

Themes

Renditions


XS S M L

Mobile first

22

Responsive: Breakpoints and renditions

L

M S

XS

L

M

S

XS

23

Thanks for submitting this ticket. Judging by your briefing, this is the best option,

leveraging the existing components. Shall we implement that? Or do you still see

reason for new functionality.

Triage

Help to me to achieve (enter goal) with the

existing set of components

Yes, please implement the option, leveraging existing functionality

No, these options won’t do. I truly need new/additional functionality

in order to achieve my goals

CQ5 Component Library Optionally: DS to touch base with Information Architect

DAP/Digital Services

Digital Lead Market / Digital manager BU Step 2

Enter intake process (see next slide)

(wireframes)

(x-sector examples)


24

If the new functionality is helpful to multiple businesses and/or

markets, and provides a unique ability with sustainable business

value, it has a high chance to be picked up by the central

development project.

If not, your business will need to find funding to finance the

development work within the DAP track.

25

What to deliver to the intake process?

1) Description of the ability (“what are my visitors able to do, and why?”), the functionality (“what it accomplishes”), and the desired behavior on the front-end (“how it accomplishes that in the eye of the visitor”).

2) A short list of acceptance criteria (“we’ll accept it, when it …”) 3) Write the business case: describe in 1 paragraph the level of reusability for other

markets, and other businesses. Which generic value does this bring? 4) Where lies ownership: who is asking (and consequently: who is signing off when it’s

delivered) 5) Predict volume and duration: how often will this new functionality be used, and for

how long? 6) Deliver (if available) gathered evidence of customer preference (either web

statistics, user testing results or scientific research)

You can use the example form below (with pre-set example values)


Thank you






