Content editing experience

Node Reference Highlight (NRHI) is a module that provides the ability to highlight text in a node body and associate another type of node to it by reference. It provides permission and workflow style logic to allow for the following types of interactivity:

• Allow role X Y and Z to highlight for reference
• Allow role X to highlight content created by role Y
• Allow role Y to highlight all content

7.x

Actively in development though early testing of alpha1 is stable and more robust then original 6.x. 7.x no longer needs to demonstrate how to implement the API as two example uses of the API come packaged as add on features. NRHI Glossary is now included in this package and replicates the functionality originally provided in the ELMS Terms module.

It now requires the following contributed modules:

• Entity Reference
• Entity Reference Prepopulate
• Prepopulate (7.x-2.x-dev)

The API has also been expanded to allow for non node reference calls. An example implementation of this can be seen out of the box if you enable the Typo Module.

6.x

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 is an API for creating book content outlines. It's similar to the Skeleton module in that it seeks to make outlines reusable but differs in that it's completely for developers. For examples on how to implement this see the ELMS distribution (see elms_id_best_practices and elms_content for complex examples in particular). Right now this is used for course outlines but is generalized to allow for the rapid creation of any outline. Below you will see the API.txt file for how you can implement and modify outlines defined by other projects.

Here is the basic structure:

$outline['YOUR_TEMPLATE_MACHINE_NAME'] = array(
     'title' => 'YOUR TEMPLATE NAME',
      array(
       'type' => '',
       'title' => '',
       'content => '', //optional body content
	'format' => '', //optional text input format
	'duplicate' => TRUE //or number of times to replicate,
	'children' => array(
	 //SAME STRUCTURE AS ABOVE NOW
	)
     ));

--Acceptable values for type, any kind of content type
--@i can be used in the title of something that's going to be duplicated as to where the incemental value should be placed. This is not required.
--duplicate: number of times to duplicate, the loop value can be altered based on criteria, see hook_book_outline_builder_loop_alter.

Poll Extras provides additional flexibility to the core poll module. Here's the specifics:

This module makes it easy for content editors to create webforms to go along with other posts, as part of a single workflow.

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