Web Experience Management module / tech list

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Posted by batsonjay on November 4, 2011 at 4:56pm
Last updated by batsonjay on Mon, 2012-03-26 19:09

Relevant features, and modules, are as follows.

For creating content with reduced (or eliminated) developer involvement

Layout Manager from Seabourne. Design is driven by end-user UX concerns first, and builds (exclusively) on Blocks (vs. Panels).
Panels with spin-offs for handling IPE:
- in-place editor
- Panelizer
- Panopoly (Chapter 3's latest addition to the Panels UX family)
Drupal 8 initiatives to push our envelope: Core context UX

Media management (making it easy for content creators to add image & video to pages):
- Media module. This is actually in pretty good shape; but can always get better. Anybody have some really useful advancements they're working on for it that they want to bring attention to?
- Rich media. There are a bunch of things here; what's our goal?
Multilingual sites (to present a localized user experience for site visitors):

Best done using a third-party service, with module support. Available modules / services include Eloqua, Manticore, Loopfuse.

Mobile support. This is a big topic; there's lots of approaches to this. Plus, making Drupal be staggeringly-great for Mobile is one of Drupal 8's core initiatives. While all that's going on, there is a whole list of mobile resources for Drupal.
Email marketing. Another big topic, and the relevant stuff here depends on how much you want Drupal to do - vs. (wisely) using external services that focus on this problem. (Services are good because they handle blacklisting, previewing in various email clients, throttled delivery, and all kinds of good things.) Examples:

Email campaigns are also a feature of the visitor tracking & scoring systems above.
Email marketing framework
Mailchimp
Constant Contact

Online community, user generated content. Drupal can do a lot, or smaller stuff, depending on what you want:
- A complete, fully packaged community (a/k/a Social Business Software) site can be deployed using Commons
- Commons is a pre-bundling of a bunch of individual components that you can use if you don't want everything in one bag. Examples are many; a few key ones include Organic Groups, Fivestar, Facebook-style Statuses (called Statuses in the D7 namespace), User Relationships, and MANY, MANY more items. And of course, Drupal has Commenting built-in.
Multisite / microsites:

Drupal has a variety of different ways to handle multiple sites, depending on what you're actually looking to do. Methods include:

Shared code, separate sites. When sites have disparate, unrelated content (and users, etc.), simply use a shared code repository for multiple sites (and pushing from code repository to dev/staging/production sites).
Shared users, separate sites. When sites need to share common user databases, but have disparate content, (a'la Single Signon across sites) many site builders use Bakery.
Lots of shared stuff. When sites need to run a group of affiliated sites from one Drupal installation and a single shared database, the Domain Access module fits the bill.