Content Renditions

There has been a real explosion in the number of channels that our customers need to manage and support. Every year new channels become available for marketers to engage their customers, and it is literally impossible to know what channels will be available to marketers in three or more years from now.​ In short, marketers need to create and reuse image and video assets in new and evolving channels. 

Marketers need to create and reuse image and video assets in new and evolving channels. 

Marketers, designers, and developers creating, managing , and consuming the different images needed to fuel campaigns via the different channels.

By partnering with PM we discovered that our main competitor, Adobe Experience Manager, solved this same issue through a feature they referred to as "Image Presets". We did some competitive analysis against them and also gathered data and ideas from other metadata intensive image editors. 

After gaining a thorough understanding of the feature area and the scenarios we needed to cover from end-to-end, designing this feature was a matter of reusing existing building blocks and patterns from our design system. In that regard, it was rather straight forward, but our patterns and design system did have some limitations, so several proposals to extend our library had to be made. 

1) The secondary call to action button styles used to "Add Rendition" were practically invisible in the image rendition pages, we discussed this with the design system team so we could fix that across the product and across the design system. Also, First-item help boilerplates for when the panels are empty provided instructions on how to upload renditions if you have permissions. Note the boilerplate text link "Add" really helped the usablity issue we faced with the gray "Add Renditions" button.  

2) The list of renditions had to be divided in two: Default and Custom. First, we tried a simple divider and one list, but eventually we had to go with a tabbed panel approach because of how differently both types of renditions were handled by the API and because one usability and discoverability issues the initial design presented. 

3) We needed to add a banner within a panel to explain why sometimes some users couldn't add renditions.