Asset scenarios

Scenario 1: FTP and Asset API

In this scenario, the customer synchronizes assets from their local server to the CloudSuite FTP(S) server. This method is suitable for managing assets directly within the CloudSuite ecosystem.

Accepted File Types

CloudSuite supports the following image formats:

JPG
JPEG
PNG
GIF
WEBP

CloudSuite automatically resizes uploaded images into predefined sizes: mini, small, normal, and large.

Non-image assets are not resized and must be linked using an asset-type URL.

Uploading Assets

To upload assets to the CloudSuite FTP(S) server, follow these best practices:

Upload only new or updated images. This minimizes unnecessary data transfer and avoids redundant resizing operations.
Ensure file names match exactly, as the FTP server is case-sensitive.

Linking Assets

After uploading assets, link them to the corresponding product using the Assets API. This step associates the uploaded assets with the appropriate items in your catalog.

Scenario 2 - External URLs with Asset API

In this scenario, the customer hosts assets on an external server, and CloudSuite retrieves images directly from the specified URLs.

This approach is ideal for customers who prefer to manage assets outside the CloudSuite system.

Linking External Assets

To link externally hosted assets, use the Assets API. https://cloudsuite.atlassian.net/wiki/x/kIC5Iw

Important Notes for Image Assets

On-the-fly resizing: External servers must support on-the-fly image resizing. This means the server should allow URL parameters to specify image dimensions. Example formats include:
- https://some-imageserver.com/myimage-200x200.png
- https://some-imageserver.com/200x200/myimage.png

The size parameters in the URLs must be implemented in the customer’s front-end theme.