Integrations

Flickr Rippr reads flickr.com for users latest public photos, and turns these into content (nodes) on your drupal website.

You need only publish to flickr.com, and they will automagically appear on your drupal website after each cron run. Join this up with the Views module and make photo galleries, blocks, and other awesomes.

Example available on author's blog: http://coffee.geek.nz/photos

requires the Flickr API module.

Features

• Import latest (or all) photos for a flickr user
• Multiple flickr accounts per drupal user
• syncs tags from flickr.com as terms in a drupal taxonomy vocab.
• syncs comments from flickr, saved as drupal comments
• Can be configured to only import photos with a chosen tag or tags
• Views Integration - photos, metadata, comments, tags, geo data, flickr accounts
• Import latest photos from flickr group (new, beta, nodes will be owned by anoymous)
• Configurable size of jpegs on teaser or full page view
• Option to save jpeg photo file locally on your sever instead of serving from flickr.com
• Import latest photos on hook_cron and/or manual update of individual accounts.
• Integration with Shadow Box module

Icecast YP directory.

Simplenews Template is a Drupal module that extends the Simplenews module by providing a themable template with configurable header, footer and style. Template, header, footer and style are configurable for each newsletter independently.

Simplenews Template can with advantage be used in conjunction with RelatedContent.

Simplenews Template is developed by Thomas Barregren of NodeOne. The initial release was sponsored by Spoon Media.

DEPRECATED in favor of Embedded Media Field, which includes Embedded Video Field (previously Video CCK) as part of it's contributed modules, alo

Ekudos is a Dutch Diggalike democratic news system. This module adds an ekudos link to you posts
See ekudos.nl for the site.

I have never had the time to develop this module as planned. I believe that other modules now available may do what it aimed to do. Please contact me if you can confirm this (or want to take this over).

RESTfulness lets you build and manage a REST API to a Drupal site via administrative pages on your Drupal site itself.

In the simplest use of RESTfulness, any functionality that is currently available via a menu hook can be exposed as a REST function. Using the full complement of the standard HTTP verbs (GET, POST, PUT and DELETE), you can provide, for example, a blog API that looks like this:

• GET /blog/entry/add (get "new blog entry" form)
• POST /blog/entry/add (post new blog entry)
• PUT /blog/entry/[nid] (edit blog entry)
• DELETE /blog/entry/[nid] (delete blog entry)

You use the Accept: header of the HTTP request to specify what kind of content you want to get back. This content type is mapped to a theme. So you might specify text/html or application/xhtml+xml to request a response in (X)HTML. Or you might ask for text/xml or application/xml to get an XML version of the same content. The content type - to - theme mapping you specify determines which theme gets used.

All of this configuration happens via administrative pages, and the REST functions and content type mappings you define are stored as Drupal nodes. Hence, your API itself becomes content that you can manage using the full gamut of Drupal capabilities. You have the ability to insert code as "glue" to connect your REST API to Drupal core functionality and modules, but RESTfulness aims to provide as much GUI-based configurability, and management of the API using Drupal's own and other APIs (such as Views), as possible.