For Austrian Lotteries, we connected Bynder to Storyblok and implemented image delivery through CX Omnichannel. Editors choose images in the CMS. The website receives the size and crop needed for each placement.
From the asset library to the website
Bynder holds images, videos and other media in one place. This digital asset management system, or DAM, gives editorial, marketing and design teams a shared library to work from.
But a shared library does not stop copies multiplying. Without a CMS integration, an editor downloads an image, prepares it for a page and uploads it again. The next website needs another version. A few months later, the same photograph exists in several systems under different names, with different edits.
Our Storyblok integration removes that detour. The CMS stores a reference to the Bynder asset, while Bynder serves the image itself. There is no separate file to upload to Storyblok’s media library.
Editors choose images without leaving Storyblok
The existing Bynder integration lets editors browse and select images inside Storyblok. There is no need to switch systems or save files to a local drive.
That integration was our starting point. We connected it to the site’s content blocks and the way each block displays an image. A full-width lead image has different requirements from an article card or a compact listing. The integration applies the settings for the block being used.
Editors choose the photograph. They do not have to work out its output dimensions and file format each time they publish.
CX Omnichannel prepares and serves the image
Bynder CX Omnichannel handles image processing and delivery. Dynamic Asset Transformation produces different sizes, formats and crops from a single source file.
We configured presets for the site’s recurring components. Each preset defines dimensions, cropping and image quality; the website requests the appropriate version. For something as common as an article preview, that removes a job editors would otherwise repeat across the site.
When the design requirements change, the preset can change with them. Existing articles receive the revised image variant without anyone having to export the files again.
A desktop crop can miss the point on mobile
A wide photograph cannot always be cropped down the middle. A portrait needs to keep the person’s face in view. An event photograph needs to show the moment the editor chose it for. A crop can fit the box and still be wrong for the story.
We connected the frontend’s responsive layout to Bynder’s image delivery. The site requests the version needed for each view, with crop and focus-point settings keeping the important part of the image visible.
The same source image can then serve as a large lead image, a small preview and an image on a phone. Those differences are handled in the implementation rather than handed back to editors with every article.
Different websites can share the same DAM
A corporate website, a customer portal and a campaign site do not need the same CMS to use the same image library. Bynder remains the central DAM. Each connection is built around the system receiving the assets.
We use existing connectors where they fit and APIs for custom components and applications. Passing an image URL between systems is the easy part. The work is in giving each application the information it needs to display that image correctly.
The integration also has to account for day-to-day operation: picking up image changes, handling older versions in caches and avoiding a broken image when an asset is removed. Those rules need to work for both the website and the asset library.
Sharing a DAM is not, by itself, a reason to replace a working website. A focused integration is often all that is needed.
How Austrian Lotteries uses the integration
At Austrian Lotteries, images are managed in Bynder and articles are edited in Storyblok. CX Omnichannel serves the image variants, and the frontend requests the one needed for each view.
For editors, the task is straightforward: choose an image and use it in the article. Even when it appears in several places at different sizes, there are no separate variants to prepare and upload.