Contributed Modules Used by Whitehouse.gov
I and many others have asked for a list of the contributed modules used to build Whitehouse.gov. After it was pointed out to me that David Cole had displayed the list in one of his slides at DrupalCon—San Francisco, I found the archived presentation video, viewed it, and paused on that frame until I had my best guess of what each fuzzy entry said. Then I confirmed names by crosschecking that list against the list on Drupal.org of all modules available for Drupal 6. For all who are interested, this post not only lists these modules but also links to the respective project page for each module.
If you are looking into creating a "Government" distribution profile, this should give you a good start.
Where plans for Drupal 7 are to move all or part of a module into core, I have noted that next to the respective entry. Generally when only part of a module will be moved into core the remaining components will continue to be available for Drupal 7 on the same project page as before.
- Acquia Network Connector
- Admin
- Akamai (contributed by whitehouse.gov)
- Apache Solr Search Integration
- CAPTCHA
- CCK (largely moving to core in Drupal 7; remainder will be available at this url)
- Coder
- Context
- Context HTTP Headers (contributed by whitehouse.gov)
- Core searches
- Custom Page
- Date
- Devel
- FCK Editor — WYSIWYG HTML Editor (next version will be called CK Editor
- FileField (will be in core in Drupal 7)
- Fivestar
Google Analytics - GovDelivery Integration (contributed by whitehouse.gov)
- ImageAPI (Requires PHP 5. Largely moving to core in Drupal 7; remainder will be available at this url.)
- ImageCache (will be in core in Drupal 7)
- ImageField (will be in core in Drupal 7)
- IMCE
- iTunes
- jQuery UI
- Libraries API
- Link
- Login Security
- Memcache API and Integration
- Menu Trails
- Modal Frame API (Current plans are to include this module in core in Drupal 7, although it is the source of a significant barrier to accessibility. Stay tuned.)
- Nagios monitoring
- Node Blocks
- Node Embed (contributed by whitehouse.gov)
- Nodequeue
- Node Relationships
- Organic Groups
- Organic Groups Mandatory Group
- Pathauto
- reCAPTCHA
- Rules
- Scheduler
- Schema
- SimpleTest (will be in core in Drupal 7)
- SWF Tools
- Token (basic components will be in core in Drupal 7; other components will be at this url)
- Table Wizard
- Views
- Views Bulk Operations (VBO)
- Views Node Taxonomy Filter
- Voting API
- Webform
A good list
It is almost the same list I have composed for the Israeli Government Drupal project.
If I may add two more:
Excellent
This isn't a government install profile, but it sure is a great starting point.
@Szodok, I'm assuming you used i18n and a bunch of related modules as well.
Is login security the only security module?
--
OpenConcept | Twitter @mgifford
Thanks for your effort.
Thanks for your effort.
Thank you so much for this list!!!
Hi Cliff
I am searching for a guide/tutorial where I get technical architecture diagram (hosting scalability), step by step guide for drupal and akamai integration, operation flow, content type required from vendor (right now vendor is creating HTML pages and delivering us then we are uploading it on akamai).
I need to integrate drupal and akamai within 2-3 months for a high traffic corporate website.
Please help and give me your suggestions, feedback and links.
Regards
Ram
LinkedIn thread
There was a recent thread on this (http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&gid=35920&d...). It didn't address akamai specifically but it had lots of great content on scaling Drupal, such as below.
Note that these tips are NOT from me, but from other posters (e.g. Patrick Janser, Chris Bryant, etc.).
A few tips :
- Files are copied from the redaction server to the 4 front-end servers with rsync.
- To reduce access to MySQL, the cache is stored in some memcache deamons, which are running on the MySQL servers and the redaction server. memcache uses RAM but almost no CPU neither disk access. That is the reason why I haven't used the front-end servers for that.
- I've activated page caching, CSS and JS aggregation + compress them with GZip. When possible, I create CSS sprites, to try and reduce multiple hits to the servers.
- Don't forget to set correct HTTP headers to let your visitors cache the static files in their browsers.
What I haven't done, but could be :
- Use lighthttpd instead of Apache to serve the static files. This would reduce the memory footprint and let you run more simultaneous processes, so more users per server.
- Use a reverse proxy like Squid or Varnish. Drupal 6 isn't really compatible with a reverse proxy, but you could use Pressflow (which is also faster and offers the new database layer of Drupal 7).
If you don't want to get a LinkedIn account, but still want the content, I can PDF the thread fer ya and email it to you.
gary
Galleria
Galleria