WhiteHouse.gov, Drupal & CMS: A little history

You may also like...

13 Responses

  1. Rich Hephner says:

    Thanks for giving “The Tool” its proper place in history. Those of us who worked on it never imagined it would last for the whole administration. The fact that we didn’t even bother to name the system is indicative that it was never meant to be much of an enterprise solution.

    As you’ve pointed our, Perl was a natural choice for a number of reasons. Since our development cycle for new functionality measured in days or hours rather than weeks, it would have been hard to imagine coding in anything other than a scripting language. PHP was pretty immature at the time, so that left Perl. We also had some pretty restrictive security constraints that limited what could be public facing. Off the shelf products could not meet those constraints in 2002.

    Thanks for the write up.

  2. Yes i agree that open source is not the answer for software.We can develop a website with all the techinical functionalities by using some language but it is not possible with the tool.

  3. Vito says:

    Yes, I’ve laid out some pros and contras at the http://vito.ho.ua/en/content/white-house-httpwwwwhitehousegov-site-moved-drupal , however seems I should say some words of support to the open government program because of http://www.slate.com/id/2233719/ .

    Yes, it can’t be globally effective and so, as every government program, but it’s still good if it helps someone. I’ve listed some of my thoughts here http://vito.ho.ua/en/content/white-house-team-httpwwwwhitehousegov-open-government-action

  4. Sanjeev says:

    I love the new site, just hope that WH can stick around with the platform. .

    http://www.sanjeevg.com/2009/10/open-source-president-goes-drupal.html

  5. Vito says:

    They at WhiteHouse support team are paying some attention to feedbacks!

    Listed some details here http://vito.ho.ua/en/content/white-house-httpwwwwhitehousegov-site-moved-drupal#comment-5 .

  6. pextubing says:

    New site is nice, just hope that Whitehouse can stick around with the platform

  7. Bernd says:

    Wonderful post! We are linking to this particularly great content on our site.
    Keep up the good writing.

  8. Cecil says:

    Very good blog you have here but I was wanting to know if you knew of any discussion boards that cover the same
    topics discussed in this article? I’d really love to be a part of community where I can get feedback from other experienced individuals that share the same interest. If you have any recommendations, please let me know.
    Cheers!

  1. October 29, 2009

    […] This post was mentioned on Twitter by Alan W. Silberberg, Jeff Walpole. Jeff Walpole said: almacy CapitalGig: WhiteHouse.gov, Drupal & CMS: A little history http://ow.ly/xsB0 (via @almacy – the godfather of the last WH.gov) […]

  2. October 31, 2009

    […] CapitalGig » Blog Archive » WhiteHouse.gov, Drupal & CMS: A little history […]

  3. November 1, 2009

    […] généralement impossible à mettre à jour si on changeait d’équipe1. Selon un article de l’agence de l’époque, leur outil était censé être provisoire, à tel point qu’ils n’ont jamais pris le […]

  4. November 5, 2009

    […] another website even though the website was new in January, 2009. David says at his personal blog Capital Gig: Many stories have reported that President Obama’s team inherited an “old proprietary CMS which […]

  5. November 5, 2009

    […] another website even though the website was new in January, 2009. David says at his personal blog Capital Gig: Many stories have reported that President Obama’s team inherited an “old proprietary CMS which […]

Leave a Reply

Your email address will not be published. Required fields are marked *