Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Integrates jQuery oEmbed All, which allows you to automatically embed Tweets, Facebook posts, and other oEmbed content anywhere on a site simply by posting a link.
Configuration consists of one step- setting the selector to which to apply jQuery oEmbed All. This allows you to whitelist or blacklist certain types of content (for instance, only applying jQuery oEmbed All to links in articles that do not have a 'no-embed' class).
This module is intended to allow entering all desired translations of a given content inside of a unique node, instead of having to create a separate node (with Multilingual Content) or a distinct field version (with Entity Translation) for each translation.
This module provides a field to integrate with Skype buttons and Skype URI's. The module contains 2 formatters, both configurable. When a stable drupal 8 version is released, this module will be ported
This module enables you to have an clear overview per domain what the menu
entries are. In Drupal all of these links are on the same page and thus
it is not clear in which domain it is and the menus will grow
very big in time as well.
Another option is to create separate menus per domain. This could be handy or could be total overkill and very clumsy since you will have to change a lot of code probably.
This module builds on the Personalize module suite. It allows you to swap out the rendered view mode of any fieldable entity on the site(provided it has multiple view modes). This module is functional, however, it is currently in heavy development and you should exercise caution before using it in a production environment.
This module extends the CiviCRM Entity module by adding a contact's address, phone, and email details to tokens. You can specify the "location type" in the token for the address, phone, and email properties of a contact.
Notice the use of "main" in the token below: [current-user:civicrm-contact:addresses:main:street-address]
Vocabulary Queue creates a nodequeue for a defined set of vocabularies and creates subqueues for each taxonomy term from the selected vocabularies have their own unique subqueue. You can place nodes into any of these subqueues.
Vocabulary Queue is build using Nodequeue modules Smartqueue API and the implementation based on smartqueue.module (part of Nodequeue module).
Vocabulary Queue is similar in functionality to smartqueue.module and the code based on code from smartqueue.module.