You might remember that a while ago, Drupal was promoted to the 'Visionaries' category in Gartner's Magic Quadrant for Social Software in the Workplace. For someone unfamiliar with all the social software vendors and projects, the choice can be overwhelming and Gartner's reports can carry a lot of weight in the decision making process. Drupal's promotion to the 'Visionaries' category was a big win for all of us.

The social software market is evolving fast, and in response Gartner is working on a presentation that compares all of the different social software players in the enterprise market, including open-source projects like Drupal. As part of that process, Acquia was invited to review the presentation and provide comments about the social software landscape and Drupal's success stories. These success stories are important to help Gartner position Drupal against its many competitors. We will also be having a followup meeting with Gartner for further discussion.

Gartner considers three different use cases for social software: (i) team collaboration software, (ii) community software and (iii) networking software. Each of these scenarios have different requirements and emphasize different features of social software. User profiles and group support seems to carry a lot of weight in their evaluations. In addition, for each of these use cases, Gartner considers two different deployment scenarios: (a) sites inside the workplace and (b) externally facing websites. This effectively creates a 3x2 matrix or grid.

To help prepare for our meeting with Gartner, and to help further Drupal's competitive positioning in the enterprise we're looking for good examples in each of those categories. Good suggestions? Post them in the comments of this blog post. Remember that Gartner is focused on the enterprise, so we're looking for examples in the enterprise that carry a lot of weight. Thanks for your help!


Damien McKenna (not verified):

Team collaboration, public-facing websites: A large portion of the websites are migrating to Drupal with many successes already under our belt. A key benefit for us is that we can have people in different departments all working together, each assigned user roles suitable for their requirements and greatly lessen the potential for snafu's, e.g. the SEO group can manage the metadata without fear that they may also break content, architecture, yadda, yadda.

We are also (time permitting) investigating replacing our custom-made Coldfusion-based intranet with Open_Atrium.

Jeff McCoy (not verified):

I work at the World Bank and we have a couple sites that could fit in with your examples for Gartner.

We have an internal-facing Open-Atrium based site that could fit in with "team collaboration software"; for more information, see Development Seed's write up:…

We also have an external-facing multisite blog platform, presently hosting about 16 blogs, that might fit in the "community software" example: see

Mike Jennings (not verified):

My organization is in the throws of implementing Drupal in an enterprise setting where numerous sites must be managed. I would have to say our efforts cross the boundaries of the grid suggested here.

I'm the project manager as well as the most outspoken proponent for Drupal. With regard to the enterprise, we are looking at a multi-site approach to reduce code patching. We currently do not share MYSQL tables. Unfortunately, we are finding some obstacles with regard to integrating Drupal into our traditional static web development lifecycle.

(i) OSTIPEDIA is a Drupal site we have been working several years to implement inside our local area computer network. We have explored a broad range of Drupal modules supporting six primary areas of online functionality; ie. monitoring, search, in-depth study, personal organization, writing original documentation, peer networking.

(ii) We have also supported grants to study and enable peer-to-peer communication about the content in our public digital library. The Drupal community is something we are observing. And, we are considering how Drupal functionality might help expand peer communication toward full online community interaction.

(iii) We have conducted much analysis of our digital library to discover and map networks of authors and subjects. We have also funded published research about accelerating the spread of ideas throughout the complex networks of scientific research. (read our blog posts by Wojick, Warnick, and Watson)

Dimitris (not verified):

Hi Dries,

We use Drupal for OrganiK, an applied research project funded by the European Commission.

The aim of OrganiK is to develop a next-generation Knowledge Management system that fits to work practices of small corporations.

For that purpose we have extended Drupal with intelligent information processing capabilities and in the next months the system will be deployed inside five companies.

You can check a brief video of OrganiK and our project web site.


Branden Faulls (not verified):

The National Strategies website ( is a UK government education portal powered by Drupal and delivered by Capita, a UK service outsourcing company. The NS website uses a taxonomy driven navigation system that harnesses Apache Solr search to deliver a broad range of guidance materials to educators and consultants across the UK. The site leverages Drupal's community features to drive engagement using organic groups, wikis, discussion forums and user generated content.

Drupal is a pivotal part of the National Strategies project strategy in delivering value to the education sector now, and in future projects that require content management with a social emphasis.

Jens Hansen (not verified):

Hi there,

our business ready Wiki might be good example of how powerful Drupal can be used for Enterprise 2.0 solutions. It is fully based on Drupal technologies and we have productive installations running at a couple of customers.

The decision to create a Wiki based on Drupal was the result of more than eight years of Wiki consulting with open source wikis like MediaWiki, TWiki and Foswiki. After making a lot of experiences with those systems we reached the boundaries of traditional wikis and spent too much time coding features that customers appreciate but the systems did not offer. This was such a pain! :-)

After having a deep look at other solutions we decided Drupal would be best fit to build a next generation Wiki. It took a lot of effort to integrate most of the feature that we loved about Wikis, like extensible permission management, LDAP integration, faceted search and so forth. Now users can create new pages by using WYSIWYG, integrate pictures, tables etc., do and undo revisions, have flexible linking of pages that goes far beyond existing mechanisms. They can create pages by links, use tags and categories for marking pages and integrate them into a facetted search function, or export every page as PDF. Later on we integrated workflows and content moderation, which are especially needed in enterprise environments .

Currently we are developing a lot of modules which should make the user experience in Drupal much more beginner friendly. We also released a couple of them allready, e.g. like tagging, wysiwyg_imageupload, content_lock or content_moderation.
In the near future we will integrate typical enterprise widgets like ToDo-Lists, configurateable dashboards, spaces for departments and much more.

Some of the new features including the complete reworked theme and usability are presented in the fair CeBIT 2010 in Hannover.

We hope that this can support your case and are looking forward to answer any further questions you might have or even demo the system. We would be happy to help you and the community positioning Drupal as a great tool for Enterprise 2.0.

For more information please have a look at our website:

Rafael Salazar (not verified):

I've been working with Dokuwiki in the past. I have always desired some kind of Drupal + Dokuwiki were available. Currently I am trying to implement a Wiki on Drupal, using some of the modules publicly available. I entered wikinovation for some kind of information about if your wiki was available for non-commercial purposes, or some very basic version available as open source, but I didn't find anything about that.

My question is, as I am really convinced this is the best way to go, Drupal Wiki, what is the availability of your extended version of Drupal? Is it a commercial version only for paying customers? Please redirect me as necessary to find information about these questions.

I submitted a link to a web site I developed using DokuWiki as the framework.

:Rafael Salazar