Image renditions are the different dimensions your image can be displayed in your content. One of your team with a user role of developer, admin, or manager create image profiles that define the different sizes of images they want to use in your content.
When you upload assets, you select the image profiles to use with each asset. The same is true for assets sourced from Shutterstock. Acoustic Content automatically creates different renditions for an image based on the renditions defined in each image profile assigned to the asset. Each rendition saves a different scale and crop of the original image. You'll probably want to review and update the renditions generated by your hub just in case your CEO's head gets cropped by mistake in a publicity shot.
Adding image renditions to your content
When you create content, you can either select images from your org's asset collection using a palette, or upload your own images.
Figure 2. Multiple renditions are created from one source image
Different things can happen when selecting or uploading an image:
- If the image selected from the palette is already mapped to the same image profile used by the image element, then the content item inherits the renditions from the selected image asset.
- If the image selected isn't mapped to the same image profile, or if you upload your own image, then the image profile is automatically assigned to the image asset. Acoustic Content then creates renditions on the image asset as defined in the image profile. Again, you'll probably want to review and update the renditions generated just in case your featured product is out of frame.
- If the image element in the content form hasn't been assigned an image profile, no additional renditions are created.
When you upload an image to an image element, you can configure the element to either accept all updates from the original asset or to retain the original version of the image and any renditions. In most cases, you don't need to change the default value of Accept all updates. By maintaining images and their renditions in the asset collection rather than in individual content items, you only need to go to one place to update an image everywhere it's used. Only choose not to accept updates from the original asset if a particular piece of content needs an image to remain unchanged for some reason.
Publishing image renditions
Now, here's some nerdy stuff for any developers reading this topic. After an asset or content item's status is changed to published, developers use APIs to retrieve the different image renditions. Akamai serves both the original image and each rendition. Renditions are applied "at the edge" so only a single image is stored in your org and Akamai. This feature helps images to render super fast on a website or app. Pretty cool, huh!
Figure 3. API calls for specific renditions of a source image