Release Note- 8th June
Dynamic Content and Dynamic Media- Static assets and virtual staging
In this release we've made some changes to our virtual staging service to allow you to consume unpublished static assets. This is useful if you want to consume static assets such as SVGs or PDFs from within a Dynamic Content visualization or preview.
Using static assets with virtual staging environments
Static assets are those that are served directly using a Static URL, rather than the Dynamic URL used to manipulate an image on the fly with Dynamic Media. Static assets can include image formats such as SVG and animated GIFs, as well as PDFs and other asset types.
Previously in order to consume static assets within a virtual staging environment, for example in Dynamic Content preview and visualization, the assets would first need to be published. Now you can replace the static domain, for example:
ampproduct.a.bigcontent.io to retrieve the unpublished version of the asset.
Consuming unpublished static assets
The following is the URL for an SVG that has been published and that we want to consume statically:
If we want to consume the unpublished asset, then we can replace the static domain with a virtual staging environment. In this example the VSE is
To retrieve the unpublished asset using this VSE you would use:
You can find out a lot more about virtual staging concepts in the introduction to virtual staging section. The virtual staging and Dynamic Content page explains the specifics of using virtual staging with Dynamic Content for visualization and preview.