> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/blocks/video.md).

# Video

<figure><img src="https://3146423938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZQuVfmt0J7tzTvfBqG6C%2Fuploads%2FC3Xb4bEhtgWwlgQ9hD6n%2Fimage.png?alt=media&amp;token=47fa1b28-2eb6-43a1-bfd8-e6752939e2f1" alt="Screenshot of a placeholder YouTube video on the Primavera Precision preset"><figcaption><p>External video, Primavera's dedicated section for YouTube or Vimeo videos</p></figcaption></figure>

This is a versatile block that allows you to either load a Shopify-hosted video or an external video.

### Settings

* **Video:** Select or upload a Shopify-hosted video
* **External video link**: Enter the video URL, e.g. `https://www.youtube.com/watch?v=_9VUPq3SxOc`&#x20;
* **External video poster image:** If you're using an external video, add a poster image. This is displayed before the video is loaded and should match the aspect ratio of the video for better results (the video takes on the same aspect ratio as the poster).
* **Enable autoplay**: This will autoplay the video when it's in view. If you have concerns about accessibility, we do not recommend enabling this option. Note that by enabling autoplay, your video will be muted. If you need the video to include sound, please disable autoplay.
* **External video description**: Describe the video for accessibility purposes
* **Button style:** Choose between primary, secondary or text for video controls


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ultramarinastudios.com/blocks/video.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
