Starting today, Twitter's developer community lives and breathes on Drupal! Check it out at

This is a big deal for Drupal -- it's not every day that one of the hottest technology start-ups switches one of its sites to Drupal. At Acquia, we have been working with Twitter on this site but couldn't talk about it for the longest time. I'm glad we finally can because it's a great use case for Drupal.

Twitter has 750,000 developers who have created nearly a million apps, making 13 billion API calls per day. Those are some astonishing figures! A population that big requires a lot, as we in the Drupal community know.

Fortunately, Drupal handles big communities well. Developer communities have been quick to recognize that and have adopted Drupal at a remarkable rate. Among them are the Brightcove developer community, Symantec Connect's developer community, DivX's developer community, and many more. Drupal's own website,, has more than a million registered users and is one of the largest developer communities in the world. Needless to say, runs on Drupal.

Twitter is a curious case. On its face Twitter only has to do one thing -- deliver short messages in one-to-many mode. But its published APIs (and enormous popularity) have led developers to create a lot of interesting things. That's also why Drupal sites can publish to Twitter, and vice versa, via the Twitter module.

In the end, that is what good developer communities are all about. Developers are like molecules, vibrating with intensity and vigor. Their individual movements can seem random. But together in the right environment, they can form waves -- or snowflakes. Nurturing a community in which both are possible is the challenge every software project faces; I'd like to think that Twitter, through Drupal, is creating the right environment.

Dev twitter com


Kirk (not verified):

Very cool to see. I find it interesting that it appears they are using Views to power "discussions" as opposed to the core Forum module.

I'm working on a new project where I'm doing something similar. And oddly enough, I am choosing to name my section "discussions" too. It is a minor point, but when you name it "Forum" people expect a certain set of features, many of which I think are pointless. Simply changing the name lets you do something unique and unexpected.

Jonathan Lambert (not verified):

This is a big use case, and something we've done a lot of work on. Using Drupal for developer communities works extremely well, and it's also often philosophically aligned with what they're trying to do as an organization.

Drupal is a good choice to be an evaluation default option for a lot of organizations when they look at how to build a sustainable strategy for developer communities.

Congratulations Dries! Nice work.

Craig Moore (not verified):

Sounds very interesting! I may have only limited Drupal experience, but I would be very interested to hear about some of the challenges in building this site, if you are able to talk about it further! Sounds like you could produce a hundred more blog posts on this topic alone!

Clare (not verified):

Yes - I was just thinking that. Would love to get a look at how it works :)

Matt Burke (not verified):

That's fantastic news.

That really is a major feather in the cap for you guys.

It will also help every one of us Drupal developers whose had to face a client who is worried because of it's opensource nature that Drupal won't scale.

Well it will scale and this is now the number one test case.

Karl Roos (not verified):

They are probably not sending a single request to Drupal, this must have been an implementation sort of like Spotify's WordPress front-end: A script that pushes changes to static HTML files instead of pulling. That's the only smart way to create an enterprise or major integration with a memory hijacker like Drupal or WordPress.

Cris (not verified):

Now if only the Drupal community could make twitter work on Drupal 7.