Skip to content
Pull request Compare This branch is 1233 commits behind bergie:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Vienna IKS Editables

VIE is a utility library for implementing decoupled Content Management systems.

Decoupled CMS communications

  • In French, vie means life, showcasing how VIE makes your website come alive
  • In English, vie means striving for victory or superiority

Common representation of content on HTML level

A web editing tool has to understand the contents of the page. It has to understand what parts of the page should be editable, and how they connect together. If there is a list of news for instance, the tool needs to understand it enough to enable users to add new news items. The easy way of accomplishing this is to add some semantic annotations to the HTML pages. These annotations could be handled via Microformats, HTML5 microdata, but the most power lies with RDFa.

RDFa is a way to describe the meaning of particular HTML elements using simple attributes. For example:

<div id="myarticle" typeof="" about="">
    <h1 property="dcterms:title">News item title</h1>
    <div property="sioc:content">News item contents</div>

Here we get all the necessary information for making a blog entry editable:

  • typeof tells us the type of the editable object. On typical CMSs this would map to a content model or a database table
  • about gives us the identifier of a particular object. On typical CMSs this would be the object identifier or database row primary key
  • property ties a particular HTML element to a property of the content object. On a CMS this could be a database column

As a side effect, this also makes pages more understandable to search engines and other semantic tools. So the annotations are not just needed for UI, but also for SEO.

Common representation of content on JavaScript level

Having contents of a page described via RDFa makes it very easy to extract the content model into JavaScript. We can have a common utility library for doing this, but we also should have a common way of keeping track of these content objects. Enter Backbone.js:

Backbone supplies structure to JavaScript-heavy applications by providing models with key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface.

With Backbone, the content extracted from the RDFa-annotated HTML page is easily manageable via JavaScript. Consider for example:

var objectInstance = VIE.ContainerManager.getInstanceForContainer(jQuery('#myarticle'));
objectInstance.set({title: 'Hello, world'});, {
    success: function(savedModel, response) {
        alert("Your article '" + savedModel.get('title') + "' was saved to server");

This JS would work across all the different CMS implementations. Backbone.js provides a quite nice RESTful implementation of communicating with the server with JSON, but it can be easily overridden with CMS-specific implementation by just implementing a new Backbone.sync method.


There is a full static HTML example of VIE at work. Saving outputs the edited contents as JSON into the JavaScript console:


Something went wrong with that request. Please try again.