No WEM without Multichannel WCM

Thursday 23 September 2010 8:06:56 am - 3 replies

Introduction

As every 2 years, new words and fancy abbreviations pop up in our market. If you read reports, blog posts of specialists, it is all about Web Engagement (WEM) or Customer Engagement (CEM) which seem to become an additional layer on top of WCM or for some people even a substitute.
While it makes absolutely sense, it makes me wonder how a WCM vendor should think when it comes to strategically look ahead in terms of positioning and roadmap. Almost all WCM vendors today address that in a way already but what is next?

» Read full blog post

3 replies

Author	Message
Mutunga Mutua	Sunday 16 January 2011 3:31:36 am Well you have a good point. Giving a consumer more than one way to buy something is the way forwards and is here to stay. I also think that web engagement (WEM) is is essential for business to boost their sales besides having better understanding of their consumers. Technology is changing and device driven content will shape the future of WCM and WEM. Mutunga Mutua www.area254.com
Doug Brethower	Sunday 16 January 2011 4:48:45 pm "positioning and roadmap" "device driven content will shape the future of WCM and WEM" Mobile shifts human interfaces to information-entertainment-communication technology into real time. Real time/time shifting simplifies everything about communication and data. It requires a re-thinking of the possibilities. Standardizing interfaces across screen display sizes, three screen capable layout technology is IMHO at the forefront of the thinking. All media, data, and information from all channels merge into pure digital network to the extent that screen size is the prime consideration. Users need one layout that makes sense for their ever bigger office desktop, another layout tailored to netbook/tablet size mobile work screens, another layout for the device that slips in their pocket. Uniformity of the experience across all display sizes, familiarity by retaining the essence with only logical simplifications as the display size gets smaller makes sense to me. Three screen user engagement-content management. It awaits a catchy acronym ;~} Doug Brethower Apple Certified Technical Consultant, Southwest, MO USA http://share.ez.no/directory/companies/lakedata.net
Nicolas Pastorino	Monday 17 January 2011 2:41:11 am " Three screen user engagement-content management. It awaits a catchy acronym ;~} " GDUE : Gracefully Downsizeable User Experience ? -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye

Author

Message

Mutunga Mutua

Sunday 16 January 2011 3:31:36 am

Well you have a good point. Giving a consumer more than one way to buy something is the way forwards and is here to stay. I also think that web engagement (WEM) is is essential for business to boost their sales besides having better understanding of their consumers. Technology is changing and device driven content will shape the future of WCM and WEM.

Mutunga Mutua

www.area254.com

Doug Brethower

Sunday 16 January 2011 4:48:45 pm

"positioning and roadmap"

"device driven content will shape the future of WCM and WEM"

Mobile shifts human interfaces to information-entertainment-communication technology into real time. Real time/time shifting simplifies everything about communication and data. It requires a re-thinking of the possibilities.

Standardizing interfaces across screen display sizes, three screen capable layout technology is IMHO at the forefront of the thinking. All media, data, and information from all channels merge into pure digital network to the extent that screen size is the prime consideration.

Users need one layout that makes sense for their ever bigger office desktop, another layout tailored to netbook/tablet size mobile work screens, another layout for the device that slips in their pocket.

Uniformity of the experience across all display sizes, familiarity by retaining the essence with only logical simplifications as the display size gets smaller makes sense to me.

Three screen user engagement-content management. It awaits a catchy acronym ;~}

Doug Brethower
Apple Certified Technical Consultant, Southwest, MO USA
http://share.ez.no/directory/companies/lakedata.net

Nicolas Pastorino

Monday 17 January 2011 2:41:11 am

Three screen user engagement-content management. It awaits a catchy acronym ;~}

GDUE : Gracefully Downsizeable User Experience ?

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

You must be logged in to post messages in this topic!

eZ debug

Timing:	Jan 17 2025 23:45:41
Script start
Timing:	Jan 17 2025 23:45:41
Module start 'layout'
Timing:	Jan 17 2025 23:45:41
Module start 'content'
Timing:	Jan 17 2025 23:45:41
Module end 'content'
Timing:	Jan 17 2025 23:45:41
Script end

Main resources:

Total runtime	0.1413 sec
Peak memory usage	4,096.0000 KB
Database Queries	72

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	587.9141	152.6250
Module start 'layout'	0.0051	0.0024	740.5391	39.4609
Module start 'content'	0.0074	0.1324	780.0000	720.4922
Module end 'content'	0.1398	0.0014	1,500.4922	18.3984
Script end	0.1413		1,518.8906

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	2.0013	16	0.0002
Check MTime	0.0013	0.8859	16	0.0001
Mysql Total
Database connection	0.0008	0.5914	1	0.0008
Mysqli_queries	0.0722	51.0878	72	0.0010
Looping result	0.0008	0.5388	70	0.0000
Template Total	0.1174	83.0	2	0.0587
Template load	0.0023	1.6273	2	0.0012
Template processing	0.1151	81.4024	2	0.0575
Template load and register function	0.0002	0.1075	1	0.0002
states
state_id_array	0.0014	0.9971	2	0.0007
state_identifier_array	0.0011	0.7533	3	0.0004
Override
Cache load	0.0019	1.3314	28	0.0001
Sytem overhead
Fetch class attribute name	0.0017	1.1816	7	0.0002
Fetch class attribute can translate value	0.0010	0.7252	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0113	7	0.0000
XML
Image XML parsing	0.0019	1.3215	3	0.0006
General
dbfile	0.0018	1.2682	29	0.0001
String conversion	0.0000	0.0042	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	forum_topic/full.tpl	extension/community_design/design/suncana/override/templates/forum_topic/full.tpl
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/separator.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltags/separator.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	content/datatype/view/ezxmltags/quote.tpl	datatype/ezxmltext/quote.tpl	extension/ezwebin/design/ezwebin/override/templates/datatype/ezxmltext/quote.tpl
1	content/datatype/view/ezxmltags/strong.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/strong.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 20 Number of unique templates used: 10

Time used to render debug report: 0.0001 secs