Content editing experience

FeedAPI and related modules provide lots of ways to get feed data into Drupal, especially into nodes.

This module allows multilingual content to be imported using the migrate module. It (reasonably, I think) assumes that translations are identified in the source database with a language field and a common key that allows the language variants to be identified as a common translation.

To use this module, enable it as usual (its prerequisites, unsurprisingly, are migrate and i18n). Set up the site's i18n languages and create any migration content sets as desired. Then visit Administer > Content Management > Migrate > Internationalization to configure things. This requires two steps: first, identify the language field and the translation ID field for each content set; save these settings and then set up the language code mappings that correlate language codes in the source data with the enabled Drupal i18n languages. And then proceed to import your data as per usual.

So far this module supports migration of nodes and taxonomy terms only. And only fully multilingual taxonomy terms are handled properly. It is in very active development, as I am currently working on migrating a moderately complex trilingual (English / Hebrew / Arabic) site. As such, it is in a very idiosyncratic alpha state, but bug reports and feature requests are welcome.

Please contact us at http://openconcept.ca if you'd like to contract us to do specific work on this module.

Text Review is a bundle of modules that allows you to review texts in a variety of ways and display the results within the text.

Text sources

• Content, CCK fields and their revisions
• Comments (and their revisions using Comment Revisions)
• Everything that uses the Text Review input filter
• UI texts (using Coder and Translation template extractor)

Review methods

• Difference percentage
• Differences
• Manually configured blacklists and whitelists
• Similarity percentage
• Spell check
• Word count

Possible use cases

• View differences between content (node) and comment revisions, much like Diff.module.
• Check if a module's UI texts are written in correct US English and according to the guidelines.

Extensibility

Text sources, review methods and defusers (methods to ignore certain pieces of texts) can be added and overridden by other modules. See trevi.api.php. The central module acts as a hub for different review methods and text sources. This means that if you add a text source, it can be reviewed with all available methods directly.

Yr Weatherdata collects weather forecast from Yr.no, a free, online weather service operated by the Norwegian Meteorological Institute and Norwegian Broadcasting Corporation.

Features

• More than 7 million locations to choose from
• Configurable with different units for displaying temperature, wind speed, pressure etc.
• Many different blocks and pages available to display the forecast
• Plenty of theme hooks available for customization

#D7AX: I pledge to make this module as accessible as it can be. If you find any flaws, please submit an issue. Help me fix them if you can.

#D7CX: Yr Weatherdata 7.x-1.0 was released the same day as Drupal 7!

The Own Term module grew out of the need to create blogs that were more flexible than the standard blog that comes out of the box with Drupal, particularly:

1. We wanted blogs to have a name different than the user who wrote them.
2. We wanted to include other things than blog nodes in a blog stream, such as polls.
3. We wanted a blog that more than one person could contribute posts to.

After some thought, it occurred to us that really, all a blog is is a collection of nodes. And if you want to collect a bunch of nodes together, then taxonomy seems to be the best way to start. They've even got taxonomy out of the box.

When you enable ownterm you need to set up a vocabulary which is set up for ownterm by clicking on the 'Enable Ownterm' checkbox in the vocabulary's edit page, and this should be an empty vocabulary to start with. After that you need to give at least the 'create and edit term' permission to authenticated users.

The Content Levels module exposes a cck field type & widget by the same name.

This field allows the user to define some ordered series of content ranking (e.g. 'Gold', 'Silver', 'Bronze') and to specify the visibility and editability of each field on the content-type depending on the content level of a node.