Good questions make better guides.
Send corrections, editorial feedback, or topic suggestions to [email protected].
Send a useful correction
Include the address of the page, the passage you are referring to, a description of the concern, and a relevant official source. For a changing platform requirement, identify the documentation version or the date of the reference when possible. This makes the issue easier to assess without guessing which workflow you mean.
Suggest a future topic
Describe the creative or technical decision you are trying to make. A concrete question about source timing, caption review, or a publishing handoff is more useful than a request for a feature this website does not operate. Suggestions help identify where explanations need more depth.
Keep private information out
Do not email passwords, API keys, access tokens, unpublished client footage, private review links, or confidential account details. A description of the issue and a public reference are usually enough for an editorial question. This contact channel is not an account-recovery or live API support service.
Before you write
The FAQ explains the scope of the site, while the editorial policy describes examples and references. No response-time commitment or technical support entitlement is offered.