Actively maintained

Module provides some improvements for Views combine filter.

A scrollshow is like a slideshow, except it takes over the entire page and the user scrolls down to advance to the next slide.

This module allows you to turn a list of nodes into a full page scrollshow. You can optionally add configurable effects:

• Background video: Show a video behind the slides that advances as you scroll.
• Lightbox: Open internal links to other pages on the site in a lightbox, so you're users aren't force to leave the scrollshow (for when your scrollshow is your front page).
• Parallax layers: Show up to 5 animated parallax layers, configurable per slide.
• Curtain: Show an initial image at the top of the scrollshow that will go away when the user begins to scroll. (Like the curtain raising before a performance at the theatre.)

See a simple demo here!

Setup

The main module only provides the underlying scrollshow functionality. In order to actually configure a slide show you need to enable one of the display module:

• Menu scrollshow: Can turn any Drupal menu into a scrollshow. You can configure the scrollshow by going to the menu edit page. This is the best option when you want to use a scrollshow as your front page and have a good fallback for users with primitive browsers or slow connections.

Module to monitor changes on forms and content.

This text filter rewrites the src attribute on img tags that only specify a filename to point at the current location of an attached image with the same filename should one exist.

That is, if you put this:

<img src="zebra.jpg"/>

And you've uploaded a file called zebra.jpg to an image field on the same entity, the module will replace it with something like:

<img src="/sites/foo.com/zebra.jpg"/>

I find this works quite well with Markdown. I can usually remember the filenames or know what I'll call them when I get around to uploading. From there, ![alt text](zebra.jpg) is pretty handy.

Why?

My hope is to improve on other methods of placing images in-line which, so far as I can tell, fall into two categories:

• Bypassing Drupal entirely and using a JS file manager of some sort to upload images directly and then referring to them in img tags with /sites/brittle_path/files/image.jpg
• Using a magic token that refers to the field id and often encodes some position, style, etc.

I like my images being available to Drupal. Not just pointed at in code but rendered as a field, with different Image Styles, that can be included in Views, change with Context, etc. Rules out the first one.

Fast Admin creates automatic administration Views for each content type, one view per content type.
There are plans to implement: