WhiteHouse.gov Goes Drupal [Updated]

WhiteHouse.gov has gone Drupal. After months of planning, says an Obama Administration source, the White House has ditched the proprietary content management system that had been in place since the days of the Bush Administration in favor of the latest version of the open-source Drupal software, as the AP alluded to in its reporting several minutes ago.

The great Drupal switch came about after the Obama new media team, with a few months of executive branch service (and tweaking of WhiteHouse.gov) under their belts, decided they needed a more malleable development environment for the White House web presence. They wanted to be able to more quickly, easily, and gracefully build out their vision of interactive government. General Dynamics Information Technology (GDIT), the Virginia-based government contractor who had executed the Bush-era White House CMS contract, was tasked by the Obama Administration with finding a more flexible alternative. The ideal new platform would be one where dynamic features like question-and-answer forums, live video streaming, and collaborative tools could work more fluidly together with the site's infrastructure. The solution, says the White House, turned out to be Drupal. That's something of a victory for the Drupal (not to mention open-source) community.

Drupal proponents have long tried to make the case that open-source software could be just as safe, just as stable, and and just as reliable as pre-boxed software, even if hundreds, thousands, or even millions of volunteer developers had their fingers in the mix at some point along the way. The White House's seal of approval doesn't hurt.

According to White House new media director Macon Phillips, working with GDIT on the competitively bid contract are both open-source software practitioners and experts in keeping systems up and running. Notably, the Drupal specialist firm Acquia is also working with the White House on the project as a subcontractor. Why that's worth noting: Acquia founder Dries Buytaert is also happens to be credited as the programmer who created Drupal in the first place, and he currently serves as the Drupal community's project lead in the software's development. Acquia, writes Buytaert, "is to Drupal what Ubuntu or RedHat are to Linux." (Translation for the rest of us: the source for a polished, established, and supported version of a free and open-source software system.) Drupal specialists Phase2, based in Virginia, is also serving as a subcontractors on the GDIT-managed WhiteHouse.gov contract, as are the IT infrastructure firm Terremark Federal Group and Akamai, the distributed computing company already tasked with keeping the White House website up and running.

Let's really try to extract the last drop of possible meaning from a choice over a CMS. Squint a bit, and it's possible to see the White House's move to open-source software as a move towards the idea that collaborative programming can inspire -- or at least, support -- a more distributed politics. That idea bubbled up in 2004, when young programmers experimented with using Drupal itself to turn the Howard Dean campaign into the Howard Dean network. This idea, that a politics crafted by the people could be a powerful thing indeed, emerged in a slightly mutated way during the Obama presidential campaign, but has arguably receded below the surface during the first nine months of the Obama Administration. First the WhiteHouse.gov CMS gets more open, then the White House OS? Perhaps.

For the lay user, the White House website looks much the same as it has since inauguration day (though search should work noticeably better). But by being open source, the White House is opening itself up to all the bright ideas, powerful plug-ins, and innovative tools that the considerable community of Drupal aficionados come up with. It's a community that the White House says it is eager to tap into. "Open source is a great form of civic participation," the White House's Phillips told me this afternoon. "We're looking forward to getting the benefit of their energy and innovation."

Related: Drupal project lead Dries Buytaert reflects upon the White House's switch to Drupal. Tim O'Reilly's Three Insights into the Drupaling of the White House.

From the Archives: Why the White House's Embrace of Drupal Matters

[Updated with details on the contractor and subcontractors involved in the WhiteHouse.gov contract.]

Comments

Another big win for Drupal

Another big win for Drupal. The point here is that Drupal is an extensible platform and fit for the future. While they may not be using the full power of Drupal yet, they will. And the good news about Drupal is, the Whitehouse can try something "new" in social media without wasting hundred of thousands of your tax dollars on systems integration consultants for proprietary content management system tweaks.

Jordan
http://www.sumolabs.com

thats great.. wonder how they

thats great.. wonder how they will be able to combat spam???

- James from http://www.4insure.net

Nice move

To endorse OpenSouce is really a welcoming move...

-Abhishek from http://indiblogger.net

Hey

Hey Nancy thank you for the post. Its very helpeful for me.

Gregor S.
Free SMS

Compliance with Open Standards Should be Goal

I wish that the White House web site would conform with the open standards that are recognized for web documents. It is not enough to include the doctype declaration in the HTML that claims that the page is XHTML + RDFa, but there must be follow through to actually realized the goal. Any tools that are used, whether free or not, should be good enough to put out good code. I've personally used Plone which is also costs nothing and has open code that can be examined and changed. But Plone, understanding it is not perfect, at least by default produces code that conforms with the open standards it claims to.

As I went through and used the W3C validator Tool on pages (for example: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.whitehouse.... ), I found invalid XHTML + RDFa. It would also then more easily reach the accessibility guidelines (WAI and Section 508). Also the data contained in the web pages could be machine processable as well as being human readable (the more truthful the doctype declaration, the easier for the data to be consumed by standards compliant software).

I applaud the White House trying to make positive steps forward in terms of transparency. I just hope that they can also put in steps to ensure that the data and documents published conform with the standards they claim to want to abide by.

For more information:
http://www.w3.org/TR/gov-data/
http://validator.w3.org/
http://www.validsites.org/

Daniel Bennett

Daniel Bennett
http://advocatehope.org
daniel@citizencontact.com

Big Win for Drupal and Acquia

This is a great move on the part of the Obama administration side - I am impressed with the fact that they practice what they preach. Open Source for open government - great!

I would be further interested in a more technical security coverage of the implementation. If it is truly done on the site side then it will really silence the critics of Drupal who have been pointing out the security flaws of Drupal for a long time. If the site stands up to the test of time it will be a huge win for Acquia as well.

Andy

www.prometsource.com
www.promethost.com
www.isupportdigital.com

Not Open Government, But Consultants' Cash Cow

"the idea that collaborative programming can inspire -- or at least, support -- a more distributed politics"

Bingo! It's not really about "software flexibility" or "features" or "freeness" but using tools that have collectivist ideologies baked into them. Thanks for spelling that out again, it's helpful.

It's also helpful that we have transparency from you on the names of all the contractors in the Digital Beltway. Now what would also be useful is a news ticker showing the cost of their consulting fees put up on whitehouse.gov and updated daily. Then the American taxpayer will likely see what some really chagrined and angry managers in the private sector have seen, which is the huge sink of money that "free opensource Drupal" costs them and what a mess that can make of their CMS.

Drupal also has non-user-friendly features and then there's the other big piece of this you aren't telling us, Nancy, which we have to get from O'Reilly, which is that the mods that the whitehouse.gov goverati geeks are putting on to this particular Drupal project will be hidden and unavailable to the public. We're told "that's ok" under the concept of the licensing associated with this, because they are not reselling or reissuing the software commercially.

But...why *is* it ok for these soi-disant opensource projects, that sell themselves with the almighty shill of being open and "for the people" and with millions of eyes available to crush bugs blah blah able to create these cul-de-sacs where the mods aren't revealed? And frankly, this isn't just some script kiddie's garage, this is *the White House*. It would be one thing if this were *really* about security -- issues that the IT sector has been embarrassed before (remember when Iran got the blueprints to the president's helicopter off that contractor's laptop?).

But it's another thing if what it really does is cover up the collectivized actions by self-appointed people running the government outside the system of democratic institutions, without public oversight.

Remember, the whole Howard Dean thing isn't about "the people" because "the people" didn't elect Howard Dean -- there weren't enough of "the people" who wanted him -- and you can't chalk that up to chad problems. It's about "some people" who want to get into power by going around the system, and thinking that the whole Facebook Twitter wired thing is their express lane to that power.

Opensource, even of this sort you are giddily boosting with the leftism baked into it (Drupal devs solemnly tell you about that ideology they hope they have welded into their tool) cannot, in and of itself, guarantee civic *anything*.

You can't speak of "participation," for example, on Beth Noveck's Office of Science and Technology site when she and her cadres get to set up all the issues, and run the debates on their terms, and close the comments when and as they feel like it. Open government=closed comments.

"But by being open source, the White House is opening itself up to all the bright ideas, powerful plug-ins, and innovative tools that the considerable community of Drupal aficionados come up with."

Of course, there are bright ideas in proprietary software, too, Nancy, by people who show up for work on time, aren't anonymous, and have contractual obligations and one-time licensing fees and maintenance contracts that don't turn into the balloon payments of opensource contracting.

But...just what are these powerful bright ideas? Do they involve things like flag@whitehouse.gov, informing on your neighbour's bad and dangerous ideas about health care? Or welding into iphone apps various flash-mobs on various lefty issues like net neutrality?

And where are the innovative tools? Drupal always looks about as exciting as watching the paint dry.

Great Comment

I really appreciate the vision of the White House to become more transparent and open to new technologies, but I feel they unfairly overlooked many excellent open source Content Management Systems.

I have alot of experience in Drupal, and there are alot of great uses for it, it can be a very powerful CMS, but the headache of modifying, patching, and bending code in Drupal for just basic functions, is too much. I've moved on to better open source CMS.

Great comment, I'd like to see how much the digital contractors are earning from taxpayer money.

Best,

Josh M.
Miami Web Design
Chamber of Commerce

http://www.brightshore.net

Need a hand?

I'm sorry to hear you find it hard to accomplish basic functions in Drupal. I have found Drupal to be extremely flexible and extensible. If you are interested in getting involved in the Drupal community I would encourage you to check out the online documentation at http://drupal.org/handbooks and http://api.drupal.org (the hook system allows you to programmatically modify most anything) or check out one of the dozens of Drupal books (I'm a fan of Pro Drupal Development from Apress).

Working with open source CMS is a great way to save clients money as you do not need to spend time reinventing the wheel developing something like a comment system, friend requests, email notification frameworks, etc. What open source CMS are you currently working with?

Go drupal.

Great, I'm scouting for the best SMV on the net, and to Drupal being the base for the government's website, says a lot of good things about it.

salvia

better open source CMS

Would you mind sharing what you moved on to?

Also, anyone have any idea which CMS the WhiteHouse.gov site was using before the move to Drupal?

Thanks

Thanks for this informative

Thanks for this informative update! Well, in these times of crisis, everyone has difficult times – whether it's an emergency expense like getting your car towed, or a medical emergency, and that's when some people could really use a low rate personal loan. A low rate personal loan for a few hundred dollars can be a real help in tough times, and bank overdraft fees are something you want to avoid. A short term personal loan, like other financial tools, is something you don't want to rely on long term – it's a short term solution for a short term problem, and long term solutions are best dealt with professional advice. So whether you want to call it a low rate personal loan, or payday loans, it's a tool for heading off emergencies.

WH.gov CMS history

I was the White House Internet director from 2005-2007. There was an internal Perl based CMS that was bulit homegrown by a handful of brilliant career government employees. The "Tool" was used all eight years during President Bush's two terms. However, months before the election, and in preparation for the new administration (either Obama or McCain), a brand new CMS was put in place (GDIT) at 12:01 PM on Inauguration Day.

Drupal is growing so fast.

Drupal is growing so fast. There are so many drupal sites and all of them have completely different purposes. Even a movie site.

Fail Fast and Publicly

I'm not sure if you were replying to me, but the other commenter here put it well, "the headache of modifying, patching, and bending code in Drupal for just basic functions, is too much."

People experiencing this are both programmers and users. And merely mouthing the propaganda again with a sense of superiority, and making it seem as if somebody hasn't read enough documentation or Bible passages to believe, and if one hasn't read enough of the books with the inspirational messages, then it's their fault.

You don't save clients money with open source. Because...they have to constantly pay *your consulting fee* to make that lovely free but buggy and balky stuff work. And, there are varieties of options, and the White House will end up falling very flat with this, so one can only hope that the failure will be fast and public so they and we can learn from it, and that they don't lie about it and cover it up out of ideological zealotry about opensource, which is merely a cover for baking leftwing ideology into social media tools.

@prokofy: Did you know this

@prokofy: Did you know this very site is a Drupal site?

I'm a Drupal developer that's been working with the platform for the past two years and I have a startup design company called NET Burger that also uses Drupal.

Your inflammatory comments are loaded with appeals to fear, uncertainty and doubt. It is very hard to take you seriously with the tone you use.

I want to point out that the advantage of using a freely-available and open-source CMS of any kind is that it's a virtual certainty that if you are unsatisfied with one firm, you can hire another firm to do the job. Because 95% of the codebase is familiar and understood, the difference in complexity of adapting a project on such a system compared to adapting work on a proprietary or home-grown CMS is vast.

Further advantage comes from the 'Drupal Way,' shorthand speak between drupal developers referring to the strict standards and practices that make sure that all Drupal code is structured and documented carefully for security, cleanliness, and understandability. This is likely what is referred to when detractors shout angrily about 'drupal knows best.'

Most Drupal sites currently employ some form of 'glue' module that modifies functions and adds extra bits where necessary. Usually less than 1% of the code in a site is in this sort of module, I would say.

I think you can agree with me that the most optimal solution would be for the government to commit wholly to open and public source code on not only its website, but also all software it employs in daily functioning.

I'd also think it's safe to assume you're not familiar with Drupal. It is not an out-of-the-box solution with beautiful themes and plugins that make a perfect Web site in a matter of hours. It is, however, a toolkit that allows web programmers to leverage the freely-available work of thousands of other professional and hobbyist programmers and create feature-rich and solid implmentations in less time. Rather than developing features one by one, there are often modules that can provide the features when configured and used elegantly with one another.