> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/branding-and-onboarding/tips-for-an-upcoming-video-shoot.md). # Tips for an upcoming video shoot ### Having custom video content on your website can bring a variety of benefits. Custom videos are a great way to engage customers and establish trust with them. They can be used to introduce people to your practice, providers, or services. Using video content is an effective way of increasing user engagement by providing a visual representation that captures the audience's attention far better than written words alone. #### **Here are some helpful tips for you to pass along to your videographer.** * The focal point will need to be in the center of the video so that when the video is compressed on your mobile site, it is still visible. * For the purpose of the website, the video should be shot in landscape orientation. **If you want to use custom footage for your home page's video banner, we recommend the following shots:** * Shots of the exterior and interior of the facility * The doctor/staff interacting with patients (greetings the patient, performing a consultation, etc.) * The doctor/staff performing noninvasive, nonsurgical treatments (injectables, facials, etc.) As a reminder, the final video loop will need to be 10-15 seconds, maximum to preserve your site's page load speeds. \ Need more advice or tips? Contact your Customer Success Manager for more information. Click here to set a meeting through their booking link: --- # 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://help.doctorlogic.com/docs/branding-and-onboarding/tips-for-an-upcoming-video-shoot.md?ask=&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.