Content editing experience

The twitter_blackbird module allows you to create an HTML representation of actual tweets in your posts, just by pasting in a tweet URL.

Twitter API:

http://media.twitter.com/blackbird-pie/

Demo:

http://www.universalpantograph.com/content/test-blackbird-pie-tweet-embe...

In addition, each HTML representation includes web intent links:

http://dev.twitter.com/pages/intents

that allow you to reply, retweet, or favorite the tweet.

Although every tweet is archived after first use, I haven't considered any more sophisticated forms of handling rate limits yet, because in my own use cases I'm not likely to encounter those limits. Soon. (I have not joined forces with the twitter module because this module has no dependencies on it. When I address rate limiting with OAuth, or for other functionality, that will happen.)

NOTE Because Drupal stores only data that is entered in posts, only the URL (and not the full tweet HTML representation) is stored in content. This may change in a future release. However, the twitter ID and twitter details are stored, so that the site only hits twitter once per posted tweeet.

Provides support for the iVysilani by Ceska telvize for Embedded Media Field.

A very simple module which would allow you to show all/any comments attached to all node translations. Just a great way to communicate in truly multi-lingual environments.

For example I have node in English and Spanish. Drupal natural way would be to show comments for en/es translation separately (attached to en/es content). But i18n_comments will aggregate all English and Spanish comments for any translations. It doesn't matter if user will leave a comment to any node translation.

How to use:

- Works with Drupal core comment module (not nodecomment).
- Works with Drupal core localization/translation modules, doesn't require i18n to be present (but works fine with it too).
- Just enable the module. There are no settings.

Need help:

- Tested on a few very different D7 setups, but not perfect yet most probably, please do test it and submit any bugs.
- Might not make sense with Drupal forums, pleas submit your experiences.

Alternative approach

Comment QA stands by Comments, Questions and Answers.

Comment QA extends the default Drupal commenting system by adding questions and answers (Q&A) capabilities to the Drupal commenting system.

Drupal comments, by default, will produce a sequence (or thread) of comments entered by users. This works for most sites featuring blogs, forums, etc. But it is not enough for sites where users need to ask questions and get answers from other users or from the owner of a node; a situation very common on B2B sites and communities of practice.

With Comment QA the administrator can designate roles that can create questions and the roles that can create answers. This designation is done from the permissions page where all other Drupal permissions are managed.

This module adds also new check boxes to the comment section of the content type configuration form so that administrators can enable or disable the (Q&A) capabilities for specific content types.

Installation:

Installation is like with all normal Drupal modules. Drop the Comment QA folder where all the other contributed modules are (typically in sites/all/modules).

Dependencies:

The core Comment module must be enabled.

Permissions:

This project aims to provide simplenote integration and syncing to Drupal content types. http://simplenoteapp.com/

This module provides a copy/paste based integration with Google Translation Tools http://translate.google.com/translate_tools