Want to get Lullabot article, videocast, and podcast announcements delivered right to your in-box?
Let us know your email address (we won't share it) and we'll let you know when anything exciting happens.
Bringing Drupal to the U.S. Government
We had a great week of on-site training at the Department of Commerce in Washington, DC last week. They've already launched recovery.commerce.gov in Drupal and they're currently in the process of rebuilding Commerce.gov as a Drupal site. We spent the week with their team making sure that they understood not only how to build and present a Drupal site, but also the benefits of the Drupal community. They're a smart bunch and it's always fun to watch the synapses sparking as people realize all of the ways that they can snap together Drupal's pieces to create interesting web functionality.
There seems to be quite a buzz around Drupal in the government and as the Commerce team walked around the building with Drupal books under their arms, they got lots of comments from people in other bureaus, saying, "Oh! Drupal! We're thinking about using Drupal." Word is starting to get around about Drupal as a great platform for government websites.
There was a lot of excitement in the Drupal community when Recovery.gov originally launched using Drupal. And while the site has since upped its budget, redesigned, and moved off of Drupal, I still think that this is a win for our humble CMS. The site was built quickly on Drupal and launched within one month of Obama taking office. Shortly after launch, the site was getting 3,000 hits per second! That's a huge amount of traffic for any website, not to mention one built so quickly.
When I saw Tim O'Reilly last year, he asked how much Drupal is being used in government agencies. And other than its popularity for political campaigns and NGOs, my answer was "Not too much". But since that time we've seen quite a boom. In addition to these federal sites, we've been seeing Drupal at the state level with exemplary sites like New York State Senate which leverages email, mobile, and social networking to keep its citizens connected. (We'll have the New York Senate team presenting about this site at the Do It With Drupal Seminar in December.) We're also starting to see Drupal becoming a flexible and inexpensive platform for local city and town governments to create sites with much more interactive and rich content than they could afford in the past.
It's exciting to see Drupal bringing a new level of transparency and openness to government -- allowing for more understanding and involvement by citizens. While most of this government information and data was theoretically open in the past, the truth was that you had to find the right people to open the right file cabinets in the right storage rooms to get what you needed. Now, thanks to the web, the barrier of involvement has gotten a lot lower. Whether it's finding out the wait time at the nearest Registry of Motor Vehicles, downloading the application for a dog license, or keeping track of how your state representative is voting on the issues, the Internet is making it easier. Drupal can provide a quick flexible way to build these feature rich sites.
And for all those other government agencies looking to get up to speed quickly with Drupal, we'll be happy to help!
Comments on this post will automatically be closed three months from the original post date.



RSS Feed



Comments
positive stuff
I recently did some training related to http://pm.gov.au, and there is a similar change occurring in Australia.
I've found that the perception of many of the Australian public servants I've encountered is largely "Drupal is for Mom and Dad sites". With a different marketing dynamic in open source, the biggest single factor that dispels this myth is their involvement in a successful Drupal project.
Once the drive is there, in particular top-down pressure from the decision makers, then other barriers (eg microsoft-centricity, open-source suspicion) tend to dissolve (they're not "real" problems after all, and the Drupal word will spread quickly.
Just a note about Sharepoint and government entities. At least in Australia there seems to be the marketing-driven perception that bringing external internet sites under Sharepoint within an department/organization has productivity/security benefits. I just keep seeing this pattern. So I thought I'd drop this link:
http://www.mediacurrent.com/blogs/drupal-vs-sharepoint
Not just Australia
There's a similar change happening EVERYWHERE it seems. We've provided training for the UK NHS, various local and national government organisations (including Companies House) and we've put two government proposals in in the last two months here in the UK. All Drupal. The pressure on government departments in Britain now is to a) use smaller businesses rather than big consultancies, because they get better value and b) use open source software wherever sensible and slash licensing costs. That's official. I've seen the memos.
My understanding is the
My understanding is the first recovery.gov site cost $18M and the second an additional $9.5M.
Any idea why in the hell it cost so much money for either implementation?
$18 million
Nope. The $18 million figure floated around was the two year budget for the agency that was responsible for maintaining and expanding Recovery.gov. While high, it's not quite the same as an $18 million dollar Drupal site.
Congrats! That's a big step
Congrats! That's a big step to Drupal community too.
Recently Thai government have adopted Drupal to use in several of their projects as well including http://pm.go.th/
You rock man. I'm all for
You rock man.
I'm all for gov going web 2.0 in any way. Transarency, accountability and free access for the win.
How do we convince other Depts?
Jeff, great news re: Commerce. I work at a large non-profit in MA that has been pushing Drupal for a couple of years. We have lots of grants/contracts with the Federal Govt and recently have noticed that individual depts are getting more strict about their technology guidelines. For us, both the Dept of Ed and SAMHSA (part of HHS) have both pushed back against Drupal because they need us to conform to their tech stack (generally MS .NET and MSSQL and/or ColdFusion).
The really frustrating part is that we're hosting the site. They don't plan on ever hosting the site, but their guideline is that "the site needs to be able to be hosted on our servers if necessary at the end of the project" (usually 3-5 years out).
We're not talking about their internal sites. These are projects that are funded by the Departments, but usually externally hosted and managed. It's been a tough year to convince people in some Federal Departments that Drupal is worth the investment even though the alternatives are generally much more expensive, especially for us.
Anyway thanks for letting us know about Commerce. With the move of recovery.gov it's been tough to have a "showcase" govt site to show that we're not just blowing smoke.
If you guys at Lullabot would be interested in making a more formal arrangement to help us with some of these cases, I'd love to talk more about it off the comment thread.
More Deployments, Better Documentation, More Drupalcon Sessions
I believe the answer to this is to do (and promote) more deployments on the WIMP stack, provide better documentation for WIMPy Drupal, and improve the WIMPy Drupal knowledge-base in the community by adding more related Drupalcon Sessions. That is to say, the encouragement has to come from the Drupal community and Drupal developers (like Lullabot), in the form of increasing awareness of what's possible with Drupal for formerly exclusively .NET shops. So far, most developers have continued to simply reiterate "we know you're a .NET shop but we prefer to deploy on Apache". This will continue to be a point of limitation. Acquia's work with Microsoft here in developing the one-click Acquia WIMP stack install was an exciting start. Let's hope we see more.
As of IIS7, .NET and PhP can run quite nicely on the same server. Microsoft worked with Zend to re-do the PhP stack, create a stable url rewrite module, and now they have a native MSSQL Server driver for PhP and WinCache to improve PhP application stability and performance on IIS. Drupal works great on Apache, and Apache will continue to dominate the market. But there are some real opportunities for .NET-centric government agencies to now use Drupal in a "mainstream" .NET environment safely and with good performance.
It will be interesting to see whether Drupal comes to be seen as a viable alternative for government agencies.
Good post, and there's more...
Jeff, Thanks for this post. Great to hear updates about what's going on around the U.S. government with Drupal sites. We re-launched http://www.opic.gov on Drupal last May, and are currently under contract to design and develop two more Drupal sites for other govt. agencies. This definitely seems like a growing trend.
good decision to use drupal
Its a good decision to use drupal for govt site, i have used drupal on many of my site and found it very satisfactory.
techieask
its great to see that they
its great to see that they are rebuilding the site in Drupal.