Introduction to Assets and DAMs

Assets are often the most visually important part of your Site, but they can also be the largest. Storing large assets in your Git repository can become an issue, as most Git Repositories have a maximum storage amount, and larger Repositories have slower Build times.

You can configure a Digital Asset Manager to store your assets externally and connect it to your CloudCannon Site. DAMs also allow you to attach extra metadata to your assets, add complex sorting, and perform image transformations.

Articles in this section are useful for developers responsible for configuring asset storage and managing large files in CloudCannon.

In the Assets section of our Developer documentation, we cover:

• DAMs — Learn how to connect external storage like S3, Cloudinary, Azure, and more
• Configuring paths — Learn how to configure where assets are uploaded and how they are served

Let's briefly introduce a few of these topics.

DAMs#

CloudCannon integrates with several DAM providers to store your images and documents outside your Git repository. Your editors can upload and select assets from any editing interface, and the DAM serves them from a CDN.

For a more in-depth explanation of DAMs, including how to connect and configure them, please read our documentation:

• Creating an Azure DAM
• Creating a Cloudflare R2 DAM
• Creating a Cloudinary DAM
• Creating a DigitalOcean Spaces DAM
• Creating a Google Cloud Storage DAM
• Creating an S3 DAM
• Creating a Tenovos DAM
• Managing your connected DAMs
• Integrating your DAM with CloudCannon

Configuring paths#

For finer control of your assets, you can configure where CloudCannon will save new assets after a team member uploads one, and update the DAM asset URLs to use relative paths.

For a more in-depth explanation of upload paths and asset management, please read our documentation:

• Adjusting the uploads path
• DAM assets with relative paths