DAM Kick Off Session

• We are migrating away from Amplience as both our Digital Asset Management (DAM) tool and our CMS.
• Our new DAM will be Cloudinary and the new CMS will be Contentful
• We need to consider our options for the migration, and how they impact the timelines of other projects that are running.
• Main drivers for this are:
  • Amplience contract is coming to an end in September 2022
  • We will make significate site speed improvements for new and old architecture
  • Cost saving

What do we know already?

We ran a proof of concept with Cloudinary to establish before/after performance metrics with the as-is image sizing being served from Amplience, and to-be automatically optimised images served from Cloudinary. We covered the following scenarios:

• Monitor the performance of the 3 PDPs over a 2 week period
• Copy all photography and video from the 3 PDPs from Amplience to Cloudinary, and update the image/video URLs in Hybris’s product and content catalogs for these to point at the Cloudinary sources

After the 2 week period we saw a significant saving of around 50% on all assets served via Cloudinary. We identified that there were futher reductions and savings we could make by updating our query params which effect image/video optimisations.

Amplience

Amplience is our current CMS which means it is where the trading and content teams upload content for the website. For products, there are two types of assets uploaded to Amplience, mannequin images and gallery sets (hero images, triptych etc.).

Mannequin image sets are linked to each variant SKU. These images are shown on PLP and PDPs when scrolling through the colour swatches of each product.

Gallery sets are linked to the base product SKU. These images are shown on the PDP.

Hybris

The steps to upload content to Amplience and ingest this into Hybris are as follows:

1. Upload the images into Ampliance
2. Create a media set from the appropriate images
3. Save the media set in Amplience
4. Approve and publish in Amplience
5. Manifest Files - Amplience provides two Manifest files to automate the sync with Hybris
   1. Full - runs daily (midnight?), contains all exisiting media sets, is overwritten each day
   2. Delta - runs hourly, contains delta of the media sets, filename is timestamped so it’s not overwritten
6. Hybris ingestion - Hybris runs a cronjob to ingest these updates.
   1. full-amplience-assetmediaset-import for FULL import, and
   2. delta-amplience-assetmediaset-import for DELTA import.
7. Sync staging with online in Hybris as the ingestion is done into staged catalog
8. The items will publish

Content

Content	Description	Team	Mandatory	Naming Convention
Mannequin Images	Main mannequin images linked to the style variant shown on PLP and PDP	Trading	Y	baseSKU_varSKU_Product_SEASON_01 (“02” second image, “03” third) Eg. “PTT02SS_BLK_Product_H121_01” “PTT02SS_BLK_Product_H121_02”
Category Gallery (Hero Carousel)	Category images linked to the base level shown on the PLP	Trading	N	N/A Trading upload image manually onto Hybris, using the image's Dynamic URL from Amplience
Product Gallery (Hero Carousel)	Product images linked to the base level shown on the PDP	Trading	N	baseSKU_GallerySet eg. PTT02SS_GallerySet
Triptych Images	3 product images on the PDP linked to the base level product	Trading	N	baseSKU_TriptychSet eg. PTT02SS_TriptychSet
Video Carousel	Video featued beneath the Triptych images eg. here	Trading	N
Features Carousel	3 paginated images in the features section in the PDP	Trading	N	Multiple depending on file Image Block - “baseSKU_ib_01” (02,03) Media Container - “baseSKU_mc_01” Paginated Carousel Item - “baseSKU-pci_01”

Resources

Documentation	URL
How to create a new Amplience component type in Hybris	https://raphatech.atlassian.net/wiki/spaces/HT/pages/1339490311
Approach for Amplience to Contentful migration	https://raphatech.atlassian.net/wiki/spaces/OM/pages/2924085249/Approach+for+Amplience+to+Contentful+migration
Amplience to Hybris	https://raphatech.atlassian.net/wiki/spaces/NS/pages/100892780 https://raphatech.atlassian.net/wiki/spaces/NS/pages/115441997/Adding+and+Updating+Video+Assets+to+the+PDP+from+Amplience
Amplience Sync	https://raphatech.atlassian.net/wiki/spaces/NS/pages/109445125

Architectural decisions

• See below

Technical Approach

We have a few technical proof of concepts to complete before making recommodations on how we move forward.

1. Investigation: Replacing the process of creating manifest files - Amplience provides two Manifest files to automate the sync with Hybris. This functionality does not exist with Cloudinary so we need to investigate the api documentation and produce architectural designs.
2. Investigation: Using Cloudinary assets with Amplience components.
3. Investigation: Moving directly to Contentful to replace the Amplience components.
4. Identify templates to update image and video optimisations.
   1. Map amplience to cloudinary query params
   2. Produce before/after performance metrics for targeted pages / templates.

Futher Considerations

1. How replacing our eCommerce impacts us. This is mostly how we build our more dynamic pages in CMS such as PDP/PLP and the implications of session.