Content display

Drupal & Storify, two technologies, two amazing products, one Drupal module to link them.

Overview

Storify is a site which allows you to make stories using tweets, photos, videos, or other social related stuff. You can easily drag and drop these items into one place, to make a story. You can then re-order the elements to improve the stories flow, and include your own text.
Storypal is the module who links Storify and Drupal.

Features for Drupal 7

Storypal provides a new field and an input filter for including storified Stories into your beloved content.
With Storypal, you can:

• Create and edit stories within Drupal using the Storify interface
• Embed stories using different templates into your content

Features for Drupal 6

Storypal provides a new field and an input filter for including storified Stories into your beloved content.
This version doesn't use the CCK field system, I'm not planning to add this into version 6 as long as there is no explicit demand; also it may force people to upgrade to D7.

Requirements

Drupal 6

• Autoload
• Libraries 1.x

Sandbox for my new Skinr based skins module - this is where I will be migrating most of the style theme settings in my current themes, so I can reduce code duplication and make these publicly avail

Demonotice will help you show your website testers that this version of your website is in beta stage. You can also set your own notices.

This module has two (2) features:

1. better UI selection of terms. concept of the UI is similar to Hierarchical Select module.
2. creates related content block using the terms selected (that's why the name).

Better UI for selecting vocabularies

The module allows you to select multiple vocabularies in a single field entity. In Hierarchical Select, you can only choose 1 vocabulary at a time. It still synced the terms selected in the taxonomy table so you can still use this in views.

You can install this module just for this use.

Related Content Block

This module produce a block that displays related content using terms. The logic is different from other similar modules (see related modules) when generating the results. This is for specific use case where in the terms assignment are properly designed by the editors or site owner. It takes into consideration the hierarchy of the tags and the order of the group they are selected.

To better explain, here is an example. Let's assume we have Color as our only vocabulary assigned to a field entity. It has the following terms (written with hierarchy).

# Red
## Light Red
#### Light Red Combo 1
#### Light Red Combo 2
## Dark Red
### Dark Red Combo 1
### Dark Red Combo 2
## Shiny Red
# Blue

I am creating this sandox as a code exploration of Web Components as defined here: http://dvcs.w3.org/

Will allow site administrators to control which regions in a theme allow for placement of blocks via Drupal Core's block administration tools.