As I reported for the O’Reilly Radar yesterday, when the House chose Drupal as the preferred web content management system for House.gov, it made the “People’s House” one of the largest government institutions to move to the open source web content management platform.
The House.gov platform is moving to Drupal but House.gov itself is not on Drupal quite yet. That will probably happen in the next several months, according to Dan Weiser, communications director of the Office of the Chief Administrative Officer in the United States House of Representatives.
In the meantime, the incoming Congressmen and Congresswomen do appear to have adopted Drupal as the platform for their official websites. For instance, Congresswoman Colleen Hanabusa‘s site, below, uses one of several templates on the Drupal platform. Notably, each of the new sites includes default modules for the leaders in the respective verticals in the social media world: Flickr, YouTube, Twitter and Facebook.
Some questions remain about the cost and choices that representatives have as they choose their online Web presences. As NextGov reported today, while House websites can move to the open source platform – they don’t have to do so.
Given the context of citizens turning to the Internet for government information, data and services in increasing numbers, however, a well-designed Congressional website with clear connections to the various digital outposts has moved from a “nice to have” to a “must have” in the eyes of the digitally connected. (For citizens on the other side of the digital divide, the House switchboards are still available via phone call at (202) 224-3121 or TTY: (202) 225-1904).
If that’s a given, then the question is then why Drupal is now the preferred web hosting environment for the House. On that count, “Drupal was chosen because it is open source and widely accepted, therefore allows Members to leverage a large community of programmers which gives them more choices and innovation,” wrote Weiser in an email. “It should also be noted that Members still will have the option to use other platforms.”
Weiser told NextGov that, because, Drupal developers are in every member’s district, “that hopefully means expanded choice and more innovation for our members.”
The current content management system limits the choice of site programmer as well as innovation, said Dan Weiser, communications director for the chief administrative officer, in an e-mail. Drupal, which uses a common framework and code that can be customized, will allow members to leverage a large community of programmers, providing more opportunities for innovation, he added.
The House expects to save some money with the transition to Drupal, since the chief administrative officer will manage the infrastructure and members pay vendors only for development time, Weiser said.
The inclusion of social media is also no longer a novelty in the beginning of 2011. “We expected there would be interest by the incoming freshmen to have social media on their sites; it just seemed natural to offer the option,” wrote Weiser.
[Disclosure: One of the vendors involved in the House’s Drupal effort is Acquia. O’Reilly AlphaTech Ventures is an investor in Acquia.]