See http://drupalcontribstatus.com/ for a demo.
A module to help power a dashboard sort of like this, leveraging as much as possible off of the fabulous http://drupal.org/project/upgrade_status module!
This project adds UUID support for the User Revision module.
Query hundreds of millions of social web profiles by email, Twitter username or Facebook ID.
Supports results from over 125 social networks.
This module integrates with the Qwerly API to enrich Drupal user profiles with social media profiles so that enterprise owners can learn more about customers and leads.
Contributed and maintained by Livelink New Media
With this module you can easily create a lot of nodes with same webform fields. It can be applicable in case of job vacancies with reply form, kind of quality feedback control or whatever your mind suggests you.
Because you can create more than one webform-enabled content types, you respectively can attach different default fields for each of them.
This module totally depends on Webform module
Form flow provides a simple way for you to create multi-step forms.
Site-wide forms can be joined together into a single flow. When a user reaches the final stage of a form flow, all the forms are submitted.
These flows can be created programmatically via hook_default_flows(), or an admin UI is provided to build flows.
You can customise the flow settings:
DrukePHP is a bridge between Drupal and CakePHP, allowing module developers to implement core application functionality using MVC patterns (CakePHP) and leveraging the power of Drupal & contributed modules for CMS functionality.
Facebook Counter module will check for numbers of Facebook shares for each node.
Roadmap:
Field API dependency (to be useable with Views)
Checking for shares number using the Batch API
Checking for shares number when saving the updated node (useful for update susing Views batch Operation)
As the data will be stored within the core Fields, it will be possible tu use Views to create some nice statistics.
The Taxonomy Domain Access Control (TDAC) module manages the creation, editing, archiving, settings, and display of Subscriptions which allow/restrict access to Fields within certain Node Types to registered Users from certain Domains, based on their email address.
e.g. If you want all Users registered with an email from the Domain "example.com" to be able to access the "cloud computing" Taxonomy from January 1st, 2011 to December 31st, 2011... TDAC is the module you want.
Built-in support and extensions for:
Allows administrators to configure title fields for nodes from the Field UI. This also allows users to edit the description and field size of title fields, as well as easily disable or enable title fields for a node type.
Title - actually makes titles a proper Field API field compared to this module which only 'fakes' titles being a proper field to allow it to be managed in the Field UI rather than on the edit content type screen.
The basic idea is that when one defines the token they add an addition param of function which is a callback to be used.
