Decide your asset approach
When content is discussed, everyone often imagines just text. However, most content would be far from effective without a proper visual segment. Images and videos as well as other downloadable files are vital in presenting information online. Together, they create your assets.
Table of contents
- Content isn't just text but also assets – images, videos, downloadable files. Think up a way of asset management that will be comfortable for your users.
- With Kontent, you can use either a built-in asset library or external digital asset management systems (DAMs). In both cases, assets can be accompanied by metadata.
- Use the image transformation features to avoid adjusting images for different devices manually.
Choose your preferred approach
Kontent offers two approaches to your asset library. You can also combine both if necessary.
A) Built-in asset library
If you don't have any dedicated platform to manage your images or files, you can conveniently store them directly in the built-in library. In the library, you can use folders to keep your files organized. All files contain a title and a description in each language by default. Thanks to content modeling of assets, this is further extendable based on your needs.
Using the built-in asset library is a good way to go or at least start as migrating your assets elsewhere later is always an option with Kontent.
B) External digital asset management (DAM)
If you prefer to keep your assets elsewhere, you can use any service suitable for this task with an API. That's typically a digital asset management (DAM) system, such as Bynder or Flicker.
To interconnect your DAM and Kontent, one of the options is using a custom element. You can create a picker with Bynder gallery thumbnails or with a filter. The limits of the integration are only in the DAM's API. There is also a gallery of existing custom elements available that you can use or customize for your scenario.
Content creators can then search for the assets stored in the DAM directly from content editing, without ever leaving Kontent and losing time switching between applications.
Model your assets when modeling content
Adding an image or a different asset may be enough for some use cases. Often, though, you want your assets to contain other metadata like tags or alternative texts. That can be done for assets from both the built-in library and DAM.
If you model the assets, you'll open the door to multiple different scenarios like:
- Clickable images – Create a content type that will include an image and a URL.
- Presentation and layout options – Add a multiple-choice element so that your editors can choose how the image will be presented on the front end. Let them define its size, emphasis, or whatever they'll need.
- Image categorization – Add taxonomy to your image and use it to organize the images in the Kontent app.
Optimizing images for different devices
When displaying an image, you can apply different transformations to every image. Without having multiple versions of the image stored, you can have multiple versions of it delivered instead.
For example, you have the promo.png image stored in HD quality. In many CMSs, you'd need to create promo_small.png and promo_mobile.png to display different resolutions elsewhere. This would eventually clutter your asset library. It's also a hell when you want to update such an image. With Kontent, you can use the image transformation and resize or trim the image based on the device within your code automatically.
You can also integrate a custom element for editing assets directly when you're editing content. This enables content creators to modify the assets for their use case at the time.
The decision about your asset approach will help you build a bigger picture of your project and make you more sure when creating your content model. When you're finished choosing the asset approach, that's the next step.Model your content