By newms on
The U.S. Whitehouse launched http://recovery.gov today - a site designed to track the implementation of the Stimulus bill that will be signed into law today by President Obama. It seems as if they are using Drupal for the site - check the page source.
Comments
Yep it's Drupal for sure
Yep it's Drupal for sure.
./is-drupal magic command agrees :D
Interesting they decided not to use Pathauto for some reason.
-- David
davidnewkerk.com | absolutecross.com
View my Drupal lessons & guides
Definitely
Here's the drupal.js: http://www.recovery.gov/misc/drupal.js
Thickbox
Using Thickbox for outgoing links as well, as in the link: http://www.recovery.gov/customcode/thickbox/site_warning.php?height=200&...
_
Would be nice to get a writeup from these guys-- particularly with regards to accessibility since it''s a govt site.
===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz
accessibility
http://www.recovery.gov/Pages/Accessibility.aspx
Looks like they've done a good job paying attention to Section 508.
=-=
No longer on drupal therefore it doesn't apply where drupal is concerned.
Love the clean design but it
Love the clean design but it seems unfinished
See this post by one of the
See this post by one of the people involved with the project:
http://drupal.org/node/376313
Yes the WH is using Drupal...
A press release was issued by the White House and MSNBC reported today that the White House has switched to Open Source and is using Drupal! This is a great victory for the Open Source Community. If it's good enough for this Administration, it's good enough for every government agency from Federal to local towns. It SAVES taxpayers money and makes government more efficient. Way to go Mr. President!
Ahh, that's no big deal...
Ahh, that's no big deal... =P
Now this is news! http://www.slayer.net/us/home is on drupal!!
w00t!
=D
=-=
Sweet. Saw them in 1986 in a bar called cedar gardens in Trenton NJ.
Tom Araya's voice is getting a little weak these days though. The blood curtling screams from the 80's were tops.
Looks like they're not using
Looks like they're not using Drupal anymore.
=-=
That's already been stated in this thread..... Therefore old news and redundant.
see: http://www.google.com/search?hl=en&source=hp&q=recovery.gov+18+million&a...
Why?
Why aren't they using drupal anymore? Can't seem to be able to find any info on that.
Is/was something wrong with drupal?
I've heard someone say that is was because of safety leaks, which would be quite disappointing.
It still wouldn't mean drupal is unsafe, though, just not safe enough for very high-profile websites.
They may have found that
They may have found that Drupal wasn't the right fit for recovery.gov for a variety of reasons, which is fine, it happens sometimes. However, they still use it for whitehouse.gov which is even "more" high profile of a site than recovery.gov. Also many huge companies, organizations, and other governments use Drupal as well. So no, there are no safety leaks; Drupal is excellent for sites of all types and sizes, and has among the best track records of any CMS for rapidly and professionally dealing with every known security issue (and a team of security experts constantly at work trying to find new issues both in core, as well as scanning through the huge number of 3rd party modules trying to find security issues in them before the wrong people do). Contributed modules or custom code added by a site's developer are the most likely source of security issues in Drupal, so extra caution and security assessment is necessary with 3rd party modules and custom code (see the book Cracking Drupal for more info). Open source in general (Drupal included) has proven to have a better security track record than closed source (case in point: Linux versus Windows).
Rosy
That's a bit to rosy IMO.
:)
Hey Heine - well of course you know best hehe, you're on the team. In any case though I can see clearly from the end results that the security team is hard at work (not just on core but in contributed modules as well, considering the many helpful notices I receive about module security updates from the mailing list). There's nothing a fraction as good as that in any other CMS I'm aware of. I guess more precisely it's not just "the security team" but much of the Drupal development community that's doing what I mentioned. Many module authors as well as other Drupal developers using or contributing to those modules, whether on the security team or not, are clearly good at spotting security issues and getting them fixed in the next releases of those modules.
Perhaps I can amend my statement to something like "Drupal coders with expertise in writing/fixing secure code, who not only help address any security issues found in core, but also respond to and assist with correcting security issues identified in 3rd party contributed modules. Members of the security team are also known to do security audits on various 3rd party modules they come across and report and/or fix the security issues they discover. Also provided is excellent documentation on writing secure code for Drupal, how to report security issues to the security team, as well as at least 1 or more books written specifically about writing secure code for Drupal. There are even modules (e.g. Coder, Security Review, and Security Scanner) which help identify common security issues. Drupal core also informs you automatically of all available security updates for every installed module."
:)
http://developmentseed.org/bl
http://developmentseed.org/blog/2009/nov/18/videos-presentations-whiteho... is a 16ish minute video of 3 of the WhiteHouse tech dev team talking about Drupal