It’s been pointed out to me that the containing HTML is also important, particularly the containing <div id="rotator">...<div> element. I’ve been meaning to add another tab with the actual HTML with the snippet calls in place, but I’m in such a habit of doing a view source of any web page that interests me that it didn’t really occur to me that anybody looking at my little demo wouldn’t immediately do the same.
Actually, I’ve taken this directly from
http://www.raymondselda.com/create-a-tabbed-content-rotator-using-jquery/ and his demo page
http://www.raymondselda.com/demo/tabbed-rotator/ and the only reason I made up the demo was to show how Wayfinder and Ditto could be used rather than a single hard-coded page, which would not be pleasant for the average user to be editing. This way, you can use a few resources that the user can edit and have the rotator automatically use those resources for its tabs and contents.
For actual use, I would put the whole rotator div in a chunk, and use a radio button TV to offer the option of having the rotator on a page or not. Usually such a thing would only appear on the home page, so the default for the TV would be some other chunk with something more suitable for the rest of the site’s pages, or even an empty chunk. I might even use ManagerManager to hide the TV once it’s set for the home page to have the rotator. The MM rule can always be commented out if it becomes necessary to make any changes in any of the resources. Or, of course, one could use a template specifically for the home page. I find it amusing to make a single template fit the entire site using TVs and CSS.