This website was initially meant to replicate the functionality of a custom application built for Physics but expanded to multiple departments. Each primary investigator needed to be able to designate other individuals as 'proxies' - allowed to create and edit content associated with that particular faculty member. Like AFAR, departments needed to be able to view only 'their' facult
Recently, I was asked to create a mobile version of an existing Drupal website. Ideally, the two sites would run off the same database so that the same content could be used.
About a year ago, I implemented a theme that determined color scheme based on taxonomy term: http://fraggles.artsci.wustl.edu/node/129 That site used a content type for sub-site landing pages, and blocks/menus were set based on URL path. This year, I took this concept a little farther using taxonomy combined with panels and a little more custom template code.
For the AFAR project, we had a set of requirements regarding permissions that were very specific and did not fit well into the typical Drupal permissions scheme.
In our department sites, we use some creative theming to overwrite the URL paths for events and news within views to link to an external source instead of the node being referenced. Unfortunately since the core search module is not a view, when search results are returned, those links DO go to the site's internal nodes.