---
url: 'https://dri.es/us-house-of-representatives-using-drupal'
title: 'U.S. House of Representatives using Drupal'
author:
  name: 'Dries Buytaert'
  url: 'https://dri.es/about'
date: '2011-01-10T14:10:54-05:00'
license: 'https://creativecommons.org/licenses/by/4.0/'
type: blog
tags:
  - Drupal
  - 'Drupal sites'
  - Acquia
  - Government
published: true
featured: false
id: 2106
---

# U.S. House of Representatives using Drupal

The [United States House of Representatives](http://house.gov) has become the latest large government organization to transition their web presence to [Drupal](https://www.drupal.org), and in a really big way. Currently the House hosts approximately 520 unique websites on a mix of over a dozen proprietary and open source content management platforms, and soon they'll all be powered by Drupal. When the House went looking for [a platform to standardize their web presence on](https://dri.es/one-drupal-to-rule-them-all), they chose Drupal because it met their requirements to:

1. Accommodate hundreds of independent websites, each with different sets of features.
2. Provide the ability to deploy new sites quickly and efficiently.
3. Enable House Members to use the web designer or developer of their choice by leveraging the Drupal community.

The House worked with a number of Drupal experts for this project, including [Acquia](https://www.acquia.com), [Phase2 Technology](https://www.phase2technology.com/) and [Ingalls Information Security](https://iinfosec.com/). The team developed, validated, and delivered the Drupal 7 platform that will be used by both individual House Member sites and Committee sites. Here are some examples of recently deployed sites (a complete list can be found at https://www.house.gov/house/news.shtml): <http://sewell.house.gov>, <https://hanabusa.house.gov/>, <https://womack.house.gov/>.

With the deployment of the House Drupal platform, the Chief Administrative Office (CAO) of the House of Representatives is soliciting Drupal development firms who wish to be vetted for an Approved Vendors List. These approved vendors may then be called on by various Representative offices and Committees (the End Customers). During the next phase of the project, End Customers will look to engage vendors to create custom websites on the House Drupal platform. These vendors can range from small to large firms and may provide services such as visual design, Drupal theming, custom module development, or other related services that the House may need. Each End Customer will have the authority to independently hire approved vendors to develop on top of the House's new Drupal platform.

The CAO will be accepting submissions to qualify vendors on an ongoing basis and is requesting an initial group of submissions by January 28th. If you are interested in being on the qualified vendor list, then please [download this document](https://www.house.gov/cao-opp/PDFSolicitations/DrupalSourcesSought.pdf) for more information.

The intent of creating the list of qualified vendors is to make it easy for elected officials and other offices within the House to connect with vendors when they are in need of services. With the new House Drupal platform in production, and the freshmen class of the 112th Congress arriving in Washington this past week, there will be plenty of opportunities for qualified vendors.
