Getting it out there
Now that we have all of that beautiful, consolidated, enriched marketing content available in our Content Hub, it’s time to put it to good use. Making it available through the marketing portal UI is one way. This covers human users that can browse and download information and potentially supply it manually to other users or processes that consume this information. Next up are structural integrations to systems, platforms, and processes that are subscribers to the Content Hub. Channel management When publishing to downstream systems, the first part of the puzzle to solve is what set of content needs to go where, and in which formats. Typical downstream systems can include ecommerce, websites, CRM, and apps, as well as external sites or processes. This is handled through channel management. Every subscribing downstream platform is registered in the Content Hub. A filter is created that covers the slice of content that will be available to this platform. This functionality can easily be compared to what would be a functional security configuration for users. A second piece of the filter is to decide on the practicalities on how content—both files and data—is delivered. This is pretty close to the order processing options on the basket in the human user use case. Connectors and API’s Key to the Content Hub concept is that it should have a can-do attitude when it comes to connecting. The primary feature for connecting other platforms is an API. We have set the standard at a full CRUD, Hypermedia, Richardson level III API. Let’s elaborate on that. CRUD (Create-Read-Update-Delete) means that the API supports both reading and writing entities or data to the repository. Hypermedia —or RESTful—APIs use URLs to connect other platforms, much like one would navigate a browser to a webpage. The Hypermedia API is to enterprise software platforms what USB is to electronic devices. You can reasonably expect other platforms to be able to connect to it. The Richardson maturity level III means that the data in the repository is fully discoverable through the API. This has the important quality that third parties working on integration points need little or no introduction to the capabilities of the API because they can simply see what is available.
“The first part of the puzzle to solve is what set of content needs to go where, and in which formats.”
18
Made with FlippingBook Learn more on our blog