Try Watson Content Hub for free

Watson Content Hub – 2017 recap

The past 12 months have been incredibly busy for the Watson Content Hub team. We’ve gone well beyond the initial capability that we shipped in 2016 and added a lot of new features. There’s still a long way to go of course, but it seems like a good time to turn and look back and see just how far we’ve come.

This post is a recap of 12 months of feature deliveries. I’ve organised it into five sections and provided references to the monthly post where you can read more about a feature. The five sections are:

In the coming few weeks, I’ll write a forward-looking post about the year ahead. The list below covers the main features we added – of course it is complemented by a great many behind the scenes improvements too. We also delivered a great range of samples, which are there to accelerate developers adoption of WCH. These can be viewed in the online sample gallery.



Watson Content Hub now has many customers building applications and several are in production. This incldues, which is our very first official reference – you can read all about that here. We have also got parts of live with WCH and have customers stressing the system at quite high volumes. Many customers have tens or hundreds of thousands of assets and content items, with some pushing the boundaries well beyond that.


Editing Experience

The editing user interface is where most people interact with WCH features, so the list in this section is long as it’s the visible part of the system. Here’s a run-down on the main features we added in 2017.

User Interface enhancements

  • Viewer role (Jan)
  • Search everywhere (Jan)
  • Card view (Mar)
  • Expanded asset meta-data (Mar)
  • Developer information in UI (Mar, Apr, May)
  • Switch between tenants (Apr)
  • Similar images recommendations (Jun, Nov)
  • Usage rights metadata (Jul)
  • Bulk delete (Dec)
  • Tag content items via Watson (Jun)
  • Multi-select from list views (Oct)
  • Review and commenting for content (Sep) and assets (Oct)
  • View developer assets (Dec)

New element types

  • Location element (Apr)
  • Reference element to published content (Jun) and draft content (Jul)
  • Multi-valued elements (Jun)
  • Index custom content elements (Dec)
  • Selection elements (Dec)
  • Formatted text element (Jul)

Localisation support

  • Locale on content items (Mar)
  • Korean & Swedish language support (Jun)
  • Asset tagging in Japanese, Korean, German, Italian and Spanish (Aug)

Publishing enhancements

  • Dependency resolution on publish (Sep)
  • Scheduled publish (Nov)
  • Bulk publish (Sep)
  • Asset lifecycle (Sep)


Headless CMS

The first half of 2017 was spent enriching the “headless CMS” capabilities of WCH, by providing richer APIs and improved delivery capabilities. Headless CMS usage leverages the editing enhancements in the previous section, as well as those listed here:

  • Sample content for all new trials (Jul)
  • Asset & Content Publishing (Feb)
  • Delivery Search (Feb)
  • Templated content publishing (Jul)
  • Secure content publishing (Aug)


Building Websites

In the summer of 2017, we launched WCH Standard Edition, which extends the “headless CMS” concept by providing the capability to natively manage a website. This mean that WCH can be used to both deliver content to mobile apps, or IOT devices, and deliver a website, like a traditional web CMS. This builds on everything up until now in this post, plus several key features.

  • Hosting web assets on WCH (Feb)
  • Starter site template (Sep)
  • Site manager (Sep)
  • Managing page content (Sep, Dec)
  • Customizable starter site template and utilities (Sep, Nov)
  • Custom hostnames (Oct)
  • Crawlable URLs (Oct)
  • Site search APIs (Oct)
  • Inline editing (Nov)
  • Hide page from navigation (Dec)
  • Delivery Render API (Nov)



Finally, the WCH team also delivered a set of capabilities to integrate WCH with other products in the IBM family and beyond. This is a key element of our strategy, in delivering ways to access WCH content from many other applications.

  • Federated Authentication (Mar)
  • Conversion tool for WCM content (Apr)
  • Forms Experience Builder integration (Jun)
  • WordPress plugin (link)
  • Sample Storefront (Jul, Oct)
  • WCH DAM for DX (Nov)
  • Watson Content Hub is included in IBM Digital Commerce (Jun)
  • WCH plugin for Watson Campaign Automation (link)

Finally, the Command Line Interface team has been very busy keeping up-to-date with API enhancements, as well as providing new capabilities. The CLI is a key part of our strategy for WCH developer experience. It allows developers to work offline and synchronise code and assets with WCH when ready. The CLI is available on Github at and can be extended.

Join The Discussion

Your email address will not be published. Required fields are marked *