Blogs / Ivo Lukac / Social flavours - reloaded

Social flavours - reloaded

Thursday 04 August 2011 12:58:37 pm

  • Currently 5 out of 5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

By : Ivo Lukac

This topic was actually my presentation on eZ Conference in London but due to very short time available and very broad subject I was not able to present everything I wanted. So lets try again, but with a blog post :)

Engage

 My claim was, and still is, that a modern CMS, besides being capable of usual content management, needs to:

  • be able to distribute content across more channels for more people to engage,
  • support content optimization via analytics and testing to increase the chance for engagement,
  • persuade users to engage with better usability.

So social flavoured is not just about tweeting about an article, it is about the process of engagement: how to help editors to setup the engagement, how to help users to engage and how to help editors again to measure the engagement.
In short, a modern CMS should support WEM (web engagement management) as much as possible.

Why, you ask?

A CMS is the logical platform to implement WEM tools as the content creation and consumption are done there. Lets imagine following scenario:

  1. An editor adds some content to a CMS
  2. At the same time editor decides to publish the content on several channels (with several variations per channel for A/B testing)
  3. Readers consume the content and react upon: could be just a “like”, or commenting, subscribing, buying, etc.
  4. CMS collects all the engagement data on all channels and all variations
  5. With that stats it can suggest better variations or even things like keywords to the editor while creating new content

Now that would be a killer CMS :) I would like too see this in eZ soon.

In the past web sites had some control over the stats, everyone can remember CGI visit counters :). In the meanwhile, engagement “left the house”:

  • visit data usually resides in Google Analytics or similar services
  • sharing data resides in Twitter, Facebook, Reedit, etc.
  • commenting data resides in Facebook, Disqus, Google+, etc.
  • subscribing data resides in Mailchimp, Feedburner, etc.

Surely, there are even more examples to show the trend, useful data is scattered all over Internet.

So to reach even better engagement we need that data in the CMS to process it and make some usable suggestions for the editor.  

Usability

Corner stone of any engagement is usability. Super powerful features with a complex UI will be less accepted with users than less-featured simple systems. We can see it every day: from Google search to iPhone and beyond. So when making new features developers should take special care of usability, for editors and end users.

We at Netgen try to do it with every extension we share:

  1. eztags - easier content creation
  2. ngpush - easier distribution, integration with twitter and facebook, ready to evolve to other platforms
  3. ngopengraph - closer integration with facebook
  4. ngconnect - easier engagement with simpler login
  5. ngcomments - easier engagement with AJAX based eZ Comments

There is a lot of effort in the eZ community which goes in the right direction.

I will list here several projects that I find interesting and worth checking out. They are not sorted in any particular order. Also, I did not use them all, some of them I just checked briefly. There could be more interesting extension too, so take this list just as a starting point.

Here we go, some of the social flavored eZ extensions:

So to conclude, for eZ Publish to become a CMS for the future we need features that are “engagement ready”, developed with usability in mind so the editors and end-users get most out of it.

LETSGO!

Blog Post Discussion

Social flavours - reloaded

eZ debug

Timing: Jan 17 2025 22:50:31
Script start
Timing: Jan 17 2025 22:50:31
Module start 'content'
Timing: Jan 17 2025 22:50:31
Module end 'content'
Timing: Jan 17 2025 22:50:31
Script end

Main resources:

Total runtime0.1295 sec
Peak memory usage2,048.0000 KB
Database Queries141

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0057 587.7109180.8438
Module start 'content' 0.00570.0047 768.5547103.5078
Module end 'content' 0.01040.1190 872.0625539.9219
Script end 0.1294  1,411.9844 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00332.5226200.0002
Check MTime0.00130.9943200.0001
Mysql Total
Database connection0.00060.493310.0006
Mysqli_queries0.088668.43871410.0006
Looping result0.00120.92621390.0000
Template Total0.118691.610.1186
Template load0.00080.647710.0008
Template processing0.117890.946610.1178
Override
Cache load0.00060.455410.0006
Sytem overhead
Fetch class attribute can translate value0.00050.419310.0005
XML
Image XML parsing0.00020.183010.0002
General
dbfile0.00312.4269200.0002
String conversion0.00000.004630.0000
Note: percentages do not add up to 100% because some accumulators overlap

CSS/JS files loaded with "ezjscPacker" during request:

CacheTypePacklevelSourceFiles
CSS0extension/community/design/community/stylesheets/ext/jquery.autocomplete.css
extension/community_design/design/suncana/stylesheets/scrollbars.css
extension/community_design/design/suncana/stylesheets/tabs.css
extension/community_design/design/suncana/stylesheets/roadmap.css
extension/community_design/design/suncana/stylesheets/content.css
extension/community_design/design/suncana/stylesheets/star-rating.css
extension/community_design/design/suncana/stylesheets/syntax_and_custom_tags.css
extension/community_design/design/suncana/stylesheets/buttons.css
extension/community_design/design/suncana/stylesheets/tweetbox.css
extension/community_design/design/suncana/stylesheets/jquery.fancybox-1.3.4.css
extension/bcsmoothgallery/design/standard/stylesheets/magnific-popup.css
extension/sevenx/design/simple/stylesheets/star_rating.css
extension/sevenx/design/simple/stylesheets/libs/fontawesome/css/all.min.css
extension/sevenx/design/simple/stylesheets/main.v02.css
extension/sevenx/design/simple/stylesheets/main.v02.res.css
JS0extension/ezjscore/design/standard/lib/yui/3.17.2/build/yui/yui-min.js
extension/ezjscore/design/standard/javascript/jquery-3.7.0.min.js
extension/community_design/design/suncana/javascript/jquery.ui.core.min.js
extension/community_design/design/suncana/javascript/jquery.ui.widget.min.js
extension/community_design/design/suncana/javascript/jquery.easing.1.3.js
extension/community_design/design/suncana/javascript/jquery.ui.tabs.js
extension/community_design/design/suncana/javascript/jquery.hoverIntent.min.js
extension/community_design/design/suncana/javascript/jquery.popmenu.js
extension/community_design/design/suncana/javascript/jScrollPane.js
extension/community_design/design/suncana/javascript/jquery.mousewheel.js
extension/community_design/design/suncana/javascript/jquery.cycle.all.js
extension/sevenx/design/simple/javascript/jquery.scrollTo.js
extension/community_design/design/suncana/javascript/jquery.cookie.js
extension/community_design/design/suncana/javascript/ezstarrating_jquery.js
extension/community_design/design/suncana/javascript/jquery.initboxes.js
extension/community_design/design/suncana/javascript/app.js
extension/community_design/design/suncana/javascript/twitterwidget.js
extension/community_design/design/suncana/javascript/community.js
extension/community_design/design/suncana/javascript/roadmap.js
extension/community_design/design/suncana/javascript/ez.js
extension/community_design/design/suncana/javascript/ezshareevents.js
extension/sevenx/design/simple/javascript/main.js

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs