we are currently developing a vimeo implementation for asset source and we discovered some issues. We have a workaround to use vimeo like an image asset source, but we don’t have the feeling that this is a good way. Feels somehow hacky…
We tried first to use a new media type “vimeo/video” to differentiate between the source (vimeo) and the classes which should get used with it. But unfortunately at one point, the media type gets checked again and therefore our configuration is not working. So we decided to use vimeo like an image asset source.
What we are actually missing or haven’t just not found yet, is something we call a “virtual asset”. To explain this approach more, think of vimeo video. Vimeo delivers all data from their CDN, poster image, video embed url, etc. So actually, we don’t want to store any document, video or image asset. We just want to store the data of a video and pass it to a content element, when it’s get selected from the editor.
So the idea would be to have a predefined virtual asset, which does only say you have to deliver e.g.:
- Thumbnails Image (Url or Asset)
- “Media Type”
As this are the minimum information to get a rendered list of all (virtual) assets.
Also any additional information could be stored to an asset and passed to fusion.
This would make the approach of asset source so much more usefull, as you could e.g. also import data from any system like a product information management system (PIM), youtube, … .
Maybe this all is already possible and we just haven’t seen it, so we would be glad for any hints.