Content display

User displays is part of the Display Suite and is an implementation of its API.

Use a drag-and-drop interface to customize layouts of nodes, views, comments, user data, etc. By defining custom view modes, one piece of content can be displayed differently in different places.

Sequential presentation of any of your site nodes, utilizing user chosen effects based on ajax asynchronous calls.

Why?
Indeed there are plenty of slideshow modules out there. So why creating one more?
We had to provide a good answer for the following requirements:

• Show a series of content items as slides using transition effect.
• Allow the user to navigate across slides using tabs and/or navigational buttons.
• Allow the content manager (non admin role) to fully control the contents & layout of each slide using node-based or views-based mode.
• Allow the content manager to easily publish / unpublish the slides and set their order of appearance.
• Allow the content manager to set the slides intervals, transition intervals and other slideshow relevant settings.
• Ensure the performance is content-agnostic i.e. allow the slideshow content to grow (number of slides and their weight) without impacting the slideshow page load time.

We could not find a module which fully suffice the above requirements (see comparison). Hence Ajax Slideshow was born.

This feature and many other checkout improvements are available for 6.x in the Ubercart Checkout Tweaks module.

_{Features • Additional module}

A catalogue shows items in a category, along with subcategories. With this module, this is a view of nodes that embeds a view of terms, with a taxonomy term argument which affects both: the main view shows nodes for the given term, and the embedded view shows the child terms of the given term.

Examples

This module is a generalization of the code from the image gallery system in Image module. In that module, the gallery view shows the nodes for the current term, and the child terms; or in other words, the nodes in the current gallery and the subgalleries.

For a shop site, suppose vocabulary is product type. For a particular term, say 'bicycles', path at 'catalogue/bicycles' takes this term as its argument, and for that term the output is:

1. the embedded term view showing child terms of 'bicycle', such as:
   • children's bicycles
   • mountain bikes
2. the main node view showing bikes which belong to the term 'bicycle'. These are general bicycle nodes that have not been further categorized.

Further examples and setup instructions are in the README file.

Features

• Embeds the view of child terms above the view of nodes