-
Have a URL which directs to editing of the content object
It would be great to have a URL which would get us to the editing of a specific content object. This would allow to use a headless front where editing of individual objects could be handled by opening the editing view of Content Hub.0
-
Increase font types
There is a request to improve the message composer. There are very few font types, so we would like you to increase it. we used to source code on content builder. However, message composer cannot edit the source code when creating templete by...2 In development
-
API Update all related records
Currently the API to update contacts only updates one record, even if the sync field matches more than one record. The Acoustic database allows duplicates records, but the API will only update one of those records (the oldest one, based on what th...0 Likely to implement
-
Akamai Image Optimization Features
The current integration of IBM's Watson Content Hub with Akamai does not include image compression settings. Akamai fully supports image compression settings but these features have not been included with Watson Content Hub. The absence of image c...0 Future consideration
-
Migration of Content and Content Types between content tenants
The standard way of developing a site indicates you work on a DEV or TEST environment at first and then, once everything is ready, you push the site to PROD. As it is now, doing this migration of content between tenants is hard. We need to use the...2 Future consideration
-
Extend asset URL format to allow addressing image renditions
WCH supports the concepts of image profiles defining a set of renditions for images. The renditions define image aspects like cropping and resizing. The actual Image transformation is driven via well-known Image URL parameters consumed and process...0 Will not implement
-
Pre-defined Profile and renditions with common standards
There are common standards to web, mobile and social renditions. It would be great for this to be pre-defined with a brand new Content instance.0 Future consideration
-
Publish Content on Online Media
Allow Acoustic Content publish content on Facebook, Instagram, Twitter, WhatsApp, YouTube, Twitter, LinkedIn, DSP, DCO and so on.0 Future consideration
-
Ability to Add Custom Meta Data Fields to Assets
We would like to attach meta data fields beyond tags and categories to include fields such as the date an asset was last requested from one of our websites in order to automate usage tracking. Another example, would be to maintain a list of websit... -
Allow to reference a published image via rendition name
Goal Add ability to reference a published image via a rendition name, e.g. * /delivery/v1/resources/3666d876-e143-4c29-b648-fc81be4039a0?rendition=mobile* /delivery/v1/resources/3666d876-e143-4c29-b648-fc81be4039a0?rendition=desktop* /delivery/v1/...1