Web Experience Management

Op 12 mei 2016 vindt de volgende editie van DrupalJam plaats, opnieuw in De Fabrique in Utrecht. Het sfeervolle industriële staat opnieuw decor voor hét Drupal congres van de lage landen. Met een geweldig programma op een fantastische locatie is DrupalJam dé gelegenheid om te netwerken, kennis te delen en als bedrijf te verbinden met het populaire CMS Drupal.

Hi folks,

I just started a blog about digital experience management with Drupal, and am writing a series comparing CRM Core and Redhen features. A lot of people seem to have questions about the similarities and differences between the two modules. Since I am researching just that for a project now, I figured I would share my findings.

The first post is here:

http://thedrupalexperience.com/article/crm-core-vs-redhen-pt-1-differenc...

Apologies for posting this same conversation to two groups, I couldn't determine the best place for this conversation to take place as it is relevant to both groups.

I wanted to start a discussion on best practices for optimizing content stored within Drupal for click-throughs and conversions. I am familiar with external tools like Optimizely and Google Analytics Content Experiments, and use them regularly for A/B and multivariate testing. They have not proven great, though, when wanting to automate testing of content within the CMS.

Here is a general use case:

Hi,
I have came across this one http://prediction.io/
It is an open source server for personalization, reccommendation and content discovery.
Actually this one does everything for web experience management!
Your thoughts?Is anyone interested in developing a module for this?
thanks

Drupal is now become one of the most popular PHP based content management system. Drupal is gaining more interest now a day because it will adopt some of the Symfony Components for upcoming version 8. By adopting HttpKernel, Drupal and Symfony projects will become more inter-operable. It means that you will be able to easily integrate your custom Symfony applications with Drupal and vice-versa.
Today Drupal is used by celebrities, non-profit institutions, schools, Fortune 500 companies and Government websites.

Mumbai Druplers,

Would like to thank everyone who attended regional meet. The best part of this meetup was the initiative to involve students, who interacted with peoples from Industry, working on Drupal.Students were really curious to know about Drupal.I am really exited to get student community on-board.

In this meetup, we talked on Drupal 8 initiatives, we explained to Druplers the key new initiatives being taken by core development team on configuration management, twig, views in core, responsive web.Thanks to Bharat for taking the session.

One of the requirements for the LSD initiative is that layouts themselves be editorial controlled. This means providing revisions to layouts with the ability to move the layout through an approval workflow.

I'm not proposing we put this functionality directly in core, but we provide a way for contrib to "easily" add the functionality.

We want to give you a quick run through our ideas and current state of research for the Blocks & Layout initiative. I am working together with Useradvocate and EclipseGc to form a broad understanding.

One of the first things I want to tackle is describing how we use "context", because this is one of the most common questions. A really quick way of describing it is that context(s) are the data objects that blocks depend upon, to determine when display (yes/no) and how to display.

I want to get serious about redoing the information architecture of Drupal. To be frank, it's a problem. Users don't know what's structure and whats content. Neither do we. I see developers all the time asking where their modules belong.

Introduction

Drupal 8 wants to provide a much-improved workflow for content creators. One of the most critical screens in this is the content creation page. This issue outlines a plan for implementing a new design for this page.

The main issues that this design wants to solve are:

One of the key ideas behind the new D8 architecture is that of resources being identified by unique URLs. It sounds simple enough but, behind it, I think there are some exciting potentials for transforming Drupal’s UX strategy. I want to share some ideas about that kind of transformation here and I’ll tackle it from a few angles: ‘what is a page’; the principle of definition-usage pairs; and IA Space and URL semantics.

yoroy's picture Only local images are allowed.

INTRODUCTION

Looks like the web experience management session at Drupalcon Denver has been approved.

What would people like to hear at this? I can give some or all of the session I did at BADcamp, but there's much more that can be covered, and I'd like to make sure we're getting relevant things discussed.

Thoughts?

http://www.mediabistro.com/10000words/the-new-convoluted-life-cycle-of-a...

<

blockquote> Always start in a blog form — i.e., your quickest way of publishing.
If the update is significant enough that, in print, it would merit its own new headline, then create a new blog post, rather than an update to an older post.

Radioactivity 2 allows you to track any fieldable entities; users, nodes, commerce products, etc. It can be used as a simple view counter but also as a popularity or activity meter, e.g. with it you can create a 'most viewed nodes at this moment' list. There is also limited rules which allows you to create an activity meter for basically whatever you want.

I imagine this is of interest here: http://mearra.com/blogs/teemu-merikoski/radioactivity-2-basics

Drupal 8 development has been underway for some time now and we're seeing increased activity around issues that aim to improve Drupal usability.

What's been missing is an overview of where we should focus our time and energy when tackling Drupal user experience challenges. This post provides an outline of the topics we want to focus on to make Drupal 8 great.

In a nutshell, we want to:

<

ul>

The first problem we need to solve is how users get around Drupal's interface on devices with small screens and touch screens. See the D8MUX road map.

Let's do some brainstorming and prototyping over how we get this good on mobile.

What do we need?

• Simple
• Consistent
• Finger friendly
• Complementary - The navigation can't upstage the main purpose of the page or task.

Current pain points

One page many purposes

As we found out in London, Drupal's mobile admin interface faces some big obstacles to overcome. If we want to to be able to tackle some of these problems in the next release cycle we need focus, the idea being we don't move on to the next item in till we have the previous one licked. I've whipped up proposal for our road map. This is by no means complete, there is plenty of detail to fill in.

I'm hoping we can work on it together.

Words to live by

Don't let the current interface hold us back