https://discuss.asciidoctor.org/Including-Vimeo-videos-in-a-document-tp492p505.html
These are great suggestions Alex. Thanks for posting them!
To provide a little background, the video template in Asciidoctor currently matches the template in AsciiDoc. Admittedly, it's a bit narrowly focused on use case which is not really the norm at all. Most of the time when we link to a video, it's on a major service like YouTube, Vimeo and so on.
As Alex mentioned, the block macros in 0.1.4 (now in master) would allow you to put something together quite easily. You could create something like:
youtube::videoid[start="1:00", options="autoplay"]
Though, when I originally envisioned the video macro, I imagined it would be able to handle any video service. That way, we don't have tons of different macros for videos when really we are just specifying an option...the video service. Here's what I had in mind:
video::videoid[service="youtube", start="1:00", options="autoplay"]
The "service" is the central piece here. It determines which template fragment will be used to create the HTML output. Alternatively, we could use a URI scheme:
video::youtube://videoid[start="1:00", options="autoplay"]
An example slim template (based on using the service attribute) might look like:
.videoblock id=@id class=[@style,role]
- if title?
.title=captioned_title
.content
- if attr? :service, 'youtube'
iframe(id=@id type="text/html" width=(attr :width, 640) height=(attr :height, 480)
src="<a href="http://www.youtube.com/embed/#{attr">http://www.youtube.com/embed/#{attr 'target'}?autoplay="#{option?('autoplay') ? 1 : 0}")
- elsif attr? :service, 'vimeo'
/ add template fo
- else
video(src=media_uri(attr :target) width=(attr :width) height=(attr :height)
poster=((attr :poster) ? media_uri(attr :poster) : nil) autoplay=(option? 'autoplay')
controls=!(option? 'nocontrols') loop=(option? 'loop'))
|Your browser does not support the video tag.
I'd be happy to add support for YouTube and Vimeo out of the box. We just need to settle on where the service name is going to go in the macro (so we can align on a standard notation). Would you be willing to file an issue?
> Do you know if Asciidoctor 0.1.4 is going to be ready soon ?
As soon as possible. All but one of the outstanding pull requests have been merged and there are just a few minor things to cleanup. We'll most certainly have a release out by the beginning of next week.
-Dan