Cloudinary End Users
Overview
This documentation aims to set out the end users for Cloudinary and in which phase we will support them.
Phases
| End User | Phase |
|---|---|
| Digital Merchandising | 1 |
| Digital Brand | 1 |
| Mobile | 2 |
| Regional Teams | 3 |
Digital Merchandising
Firstly we need to support Digital Merchandising by replacing the process of ingesting images from Amplience to Hybris to Cloudinary to Hybris. This means they are able to set images for galleries, mannequins and triptychs with improved workflows. This should be one of our primary focuses for phase 1.
Digital Brand
Secondly we need to support Digital Brand by improving their current workflows. This includes improving governance around filenames and folder structures as well as improving workflows with teams external to them. This should be our other focus during phase 1.
Mobile
During phase 2 we need to support mobile transitioning to Cloudinary. Some of the main aspects we need to cover for them are:
SDK Integration
Cloudinary's iOS SDK provides simple, yet comprehensive image and video upload, transformation, optimization, and delivery capabilities that you can implement using code that integrates seamlessly with your existing iOS application.
Moderation
Via one of the add-ons such as Amazon Rekognition AI Moderation we can easy to add image analysis to our mobile application. With Amazon Rekognition's AI Moderation add-on, we can extend Cloudinary's powerful cloud-based image media library and delivery capabilities with automatic artificial intelligence based moderation of our photos. Protecting other users from explicit and suggestive adult content in our user uploaded images, making sure that no offensive photos are displayed to our mobile viewers.
Other
- Retiring image transformations via Cloudflare
- Retiring the use of S3 for user generated media
Regional Teams
Finally for phase 3 we should look to support our regional teams. Currently regional teams create their own assets for social media platforms as well as clubhouses. We should focus on improving the digital aspects and workflows via:
Eager transformations
Generate transformed assets during the upload call so that those transformations will already be available for delivery before your users access them for the first time. These transformations are generated in addition to storing the original asset as is. This is especially useful when generating assets for social media platforms to be used by our regional teams.