Today’s post objective is to learn how to develop a Custom Component in Sites Cloud Service that makes use of static files (in our case, a default image that can be override by the contributor) and how to reference the static files to work both in edit mode and when the site is published.
Let’s finish 2016 continuing with the series of custom components, in this case we will create a custom component to integrate Oracle Content Marketing (a.k.a Compendium) with Oracle Sites Cloud Service.
Oracle Content Marketing makes it easy for everyone in your organization (and even your customers) to create and distribute compelling content across multiple channels to the people you want to reach. You can plan, produce, and deliver engaging content across multiple personas and channels throughout the customer lifecycle. In this example, we are going to integrate in Sites Cloud Service a Compendium content generated by a marketer using all the Content Marketing Cloud capabilities.
In this post, we will see a custom component example to integrate Eloqua with Oracle Sites Cloud Service.
Oracle Eloqua is a Marketing Automation Tool to manage data and customer experiences. In this example, we are going to integrate in Sites Cloud Service an Eloqua Form generated by a marketer with all the specific processing rules defined in the Form, so we will be added to an specific campaign and some actions are going to be performed once the Eloqua component is included in a SCS page and a visitor submits the form.
In this post I will show an example of a custom carousel component built with Sites Cloud Service. When working with specific designs, most part of the carousels are specifically created for the design, including the required JS files as well as the Stylesheet, so in this post I will take a bootstrap template, create a Sites Cloud Service Theme based on it and create the custom component to replace the theme carousel with a slot in which a business user can drag&drop the component and configure it as they wish.