The battle to "engage" site visitors is on. Gone is the day where a CMS just helps you create pages that you hope visitors read & consume. Today your site must provide extraordinary visitor experiences that cause them to take the action you want - from buying to reading to playing - and measure the effectiveness of the experience so you can improve it as needed.
Improving site engagement must be simple. Making it simple in Drupal requires a variety of Drupal component parts to be assembled - and a few gaps filled.
This is a Drupal Group devoted to assembling those components. Many of the relevant Drupal components have their own individual projects on drupal.org or groups here on g.d.o. But this group is an umbrella where we combine those activities with our own in one place to get a singular view of the problem, and the Drupal solution.
Here's a copy of the deck Jay used at his BADcamp presentation on Web Engagement Management. It's a general overview of the driving factors, the features needed, the Drupal work underway, and a request for participation by community members.
In order to get this to upload, I had to split it into 2 halves - each under the 2MB limit.
Building mobile solutions encompasses a large problem space: native apps, HTML5 web apps, responsive design, device capability detection, mobile/desktop switching, front-end performance, etc.
I'm seeing lots of really interesting contrib modules and themes tackling mobile problems in Drupal 7.
Since Dries has already indicated that mobile will be an important aspect of Drupal 8, my question is:
what do you think Drupal 8 core (not contrib) should provide for mobile solutions out of the box?
Last updated by jasonsavino on Sun, 2012-04-08 22:56
As the Curriculum and training group has identified while outlining the various skill sets involved in site creation & use, there's an under-represented skillset in the site creation process: that of the "Advanced content creator". This person has unique requirements, and to describe the requirements, it's first helpful to describe the person / persona. I hope this will be useful not only to the Curriculum & training group, but to other Drupal initiatives related to the Drupal needs of this type of user that is (already, if not increasingly) frequently present at sites deploying Drupal. (Thus the cross-posting to multiple groups.)Read more
Ektron CMS400.NET (version 8.5 as of this writing) is targeted at Microsoft-oriented IT shops & developers building marketing-oriented sites. The company makes a determined effort to have some type of widget for everything under the sun, from document management to group spaces to calendar widgets to e-commerce & order processing, and on and on (with varying levels of depth & sophistication).Read more
Adobe Customer Experience Solutions ("ACES" herein) is a bundle of products including:
- Web Experience Management, which is essentially CQ5 and the other products acquired from Day Software (plus some enhancements since the acquisition)
- Digital Enterprise Platform, which is the new name for the formerly-named LiveCycle and CRX platforms.
The remainder of the information on this page focuses on the WEM/CQ5 product only. However, Adobe had now budled the products, so that new customers must (apparently) purchase the LiveCycle/CRX products in conjunction with their CQ5 purchase.Read more
Last updated by kattekrab on Mon, 2012-02-06 01:58
Squiz CMS is "a revolutionary open source content management system with a highly usable interface which makes it easy to create, publish and maintain engaging websites."
Here is a demo video:
Below follows a detailed breakdown of the main features, as well as what Drupal equivalents exist for replicating functionality.Read more
Last updated by silverwing on Sat, 2013-04-13 18:34
I posed the following question on Twitter, and thought the answers might be helpful to others (as well as a place to archive further discussion that's actually searchable :P).
Here were some of the more detailed responses. This is a wiki, so feel free to add additional ones, either in the post or comments!Read more
Drupal’s site building user experience currently consists of moving between a lot of different tools and interfaces. Within Drupal 8 we want to unify these experiences (blocks, menus, views, panels…) more.
The experience that we are focusing on, is that of creating the front-end of your website - where content, blocks, views, menus are placed on pages and how these can be configured.Read more
We're exploring user interface design solutions for these two site builder workflows:
Todo: review itangalo's sketches
1. If we have a path of node/$nid, a node type of Student, a Language of German, a browser type of Safari Mobile, and it's Thursday, use response controller X and layout Y.
2. We have this thing here called layout Y. I want to put blocks in it that will render stuff based on context and configuration.
& As merlinofchaos outlines it:Read more