This won't work out of the box on 12c, because of the migration from folders_g to Framework Folders.
The content comes from a WebCenter Content backend in the same domain.
The content is put into an auto-advancing carousel.
The carousel has an index that on hover changes the feature, and a parallax hover-scroller, which is awesome but probably not tablet-friendly.
is the value of an HTML component on the target page. Uses the collection id to pull the items and use metadata to generate a carousel.
pulls data using cs.js and generates HTML (that matches carousel.css) for a dynamic carousel.
uses media query for responsive and styles the following structure:
.carousel
a
.carousel-feature
figure
:before
img
figcaption
figure.feature
is the interface for the RIDC (idcplg) server for WebCenter Content. It works roughly with this syntax:
// function call for service and parameter
cs(type, id)
// returns something that could be confused for a Promise/A but instead a ‘wish’
.then(function(response){
// result is very SOAPy, so there is an onion to peel
var items =
// Designed to handle the returns from many services, but only one implemented here
cs[type](response)
// convert to HTML
.map(function(item){
// etc. (see file)
- dID
- dDocTitle
- xSupplementalMarkings
- xComments
- dWebURL
Woot! Good to see your code again sir!