In Sitecore Content Hub™ you can extend the media processing flows to create new asset renditions. The best practices provided here can help you configure the renditions creation according to your business needs.
Extending media processing flows
As a general rule, you should apply the following best practices when extending media processing flows:
Keep the number of different renditions limited in media processing to avoid generating many renditions. Indeed, each time you upload an asset, you trigger the creation of all its renditions.
Favor using the existing renditions (Medium/Preview, Thumbnail, Big Thumbnail) whenever possible.
If the rendition you want to create is smaller than 1100x1100, use the existing Preview flow and extend it with an extra task. If the rendition you want to create is bigger than 1100x1100, create a new flow from the original one.
Provide the fewest renditions that fit the most use cases possible for users to download and use locally.
Provide the fewest standard renditions that fit the most downstream use cases possible, and leverage public links with transformations as much as possible.
You can manually create public links when smart cropping or crop to center transformations do not produce good results for edge cases.
Creating new renditions
You might want to create a new rendition for a single-use purpose, or you might need it to persist in the system for future use in Content Hub. In this case, use the following decision tree to implement the best solution:
You can either make your rendition available for cloud integration or only for local download by users.
If you want to make your rendition available for cloud integration with downstream or upstream systems such as wCMS, eCommerce, ERP, or MDM, you should:
Create the fewest high-resolution and one-size-fits-all renditions that fit the most system integrations as possible for the various file types in Sitecore Digital Asset Management (DAM)™.
Generate special downstream formats for EPS, AI, or PSD raw files if necessary.
If you want your rendition to be available for local download by Content Hub users, you should:
Create a new rendition flow in the media processing and save the rendition link.
Add the rendition link to the download UI options on the Asset details page.
For use case examples, see Media processing use cases.
Assuming a public link was previously created for an asset rendition when you set up a new file as master:
- If the new master file rendition is the same as the previous master file rendition, then the public link remains valid for this new master file.
- If you delete the old file rendition from the asset, the link still shows on the asset details page but is disabled. If you want to fix the link, you need to regenerate the deleted rendition.
- If the new and old master file renditions are different (for example, Original and Preview), the public link becomes invalid. If you want a public link for the new master file, you need to create one for the new master file rendition.
Can we improve this article ? Provide feedback