Cobalt is a framework for building front-ends for digital content distribution. You can use it to feed content to a virtually unlimited range of channels and devices.
Cobalt’s core components use standard technologies you’re already familiar with – no steep learning curve!
Cobalt is entirely developed in Java.
Data is normalized and exposed in JSON format.
Data persistence is handled by PostgreSQL.
Search is powered by ElasticSearch.
The integrated template engine is Freemarker compatible.
In common with open-source solutions, Cobalt uses a modular, service-oriented architecture interacting through standard REST protocols.
At the same time Cobalt’s core components and API’s are:
Cobalt’s core components give you a firm basis on which to create innovative solutions, without having to reinvent basic functionalities.
And you can do it confident that you’re working within a technological framework that is robust and fully documented.
That’s a key consideration when the solution you’re building is critical to your organization’s operations.
Cobalt is a decoupled solution, with a clear separation of delivery from the content creation processes, however complex these may be.
Content from any standard CMS or legacy system is normalized into a documented JSON format with HTML5 tagging for maximum versatility in subsequent delivery.
This allows Cobalt to act as highly effective bridge between existent content depositories and an unlimited range of destinations.
Have a look at some coding examples:
The example shows you how to list all the articles that belong to a specific section (passed as a query parameter) by using the Cobalt APIs in plain PHP code:
Once you have the content correctly converted into a PHP object, you can parse its content using the object operator. For example, to list all the articles in the section, you can use a piece of code like this:
This example shows you how to print a site structure using Cobalt APIs in plain Node.js code.
The first thing to do is retrieve the site structure using the /site API:
Once we have the JSON object containing the site structure, we can parse it recursively (because it has a tree structure):
This example will show you the steps needed to publish content from a third-party source. This example uses Google Docs but the same process can be applied to any other source.
First log in to Cobalt to get a valid session token (called emauth) to be used in the subsequent API call. To log in, call the /sessions/login API using data from an HTML form rendered in the Google Docs web panel:
Once you have logged in to Cobalt, you can start the publication process:
This code launches a Google Script function (analyzeDocument). The function parses the file and returns the HTML5-transformed document and other meta-information (i.e. images, blobs, author info etc.). If the call is successful, you can proceed to the first step in publication which is the preparation phase. This phase requests a slot in the repository and returns a publication ID to be used in all subsequent phases.
Once the preparation has been completed, you can move to the next phase which consists of a series of calls, one for each object involved in the publication (i.e. the story and each of its media objects):
The update call launches the /publication/update API to upload the content to Cobalt.
Once all the update processes have been completed, publication proceeds with a call to the /publication/publish API. This step may be considered a commit and publication will be confirmed.
If, for any reason, one or more update steps failed, you can roll back the entire publication by calling the /publication/abort API.
This example shows how to use a template engine to render contents on a webpage. The example uses Freemarker, although other template engines are also supported.
A webpage is logically divided into different zones, which may be seen as 'content buckets'.
If you don't know the name of the zone you want to render, you can iterate through all the defined zone names like this:
Once you have the name of the zone, you can iterate through its content, leaving the template engine to render each item, mainly on the basis of its item type. An item could be an article, an image, a video, a widget etc.:
You can use Cobalt out of the box, but this is not its real strength. Cobalt’s standard core modules are easily extended to add new functionality and are compatible with a wide range of third-party plug ins or extensions.
Cobalt’s SDK gives you the tools to make the most of its resources and develop innovative solutions quickly and easily.
Cobalt integrates the FreeMarker template engine. Designers can use themes and templates to rapidly develop new page and layout formats without manual coding. Cobalt’s APIs allow use of popular toolkits like Bootstrap or AngularJS.
You can use Cobalt to manage extremely large website portfolios (100+) based on a single CMS with advantages like content-sharing, integrated access, single sign-on, etc.
Cobalt handles different language versions as multi-lingual stories. They may be processed through different workflows and published to different delivery channels but are updated and archived as a single editorial object.
Cobalt incorporates powerful tools to measure site performance - in-page analytics, visitor engagement plots and scroll-depth statistics. Cobalt also allows A/B and multivariate testing runs to be launched with just a few clicks, proving valuable feedback about site performance.
Cobalt lets you develop your solutions in incremental mode, with frequent upgrades and deployments to keep pace with changing user requirements.
Cobalt’s service-oriented architecture supports scalability and availability features for use in both private cloud environments as well as major cloud providers like Amazon Web Services (AWS).
EidosMedia is a certified AWS Advanced Partner.