This is a sample post demonstrating embedded video playback inside a CORD blog article. The video is hosted in the Directus file library and served via the public assets endpoint with HTTP Range support, so visitors can seek and the file streams in chunks.
How the embed works
The post body contains a native HTML5 <video> element that points at the Directus file UUID. The site sanitiser allows <video>, <source>, and <track> tags with safe attributes (controls, preload, poster, captions). Inline event handlers and unsafe URI schemes are stripped.
Why native <video>?
Three reasons:
- No third-party tracking. Visitors aren't pinged by YouTube, Vimeo, or any analytics provider beyond ours.
- Predictable performance. The browser fetches the file directly from our origin. With Range requests, only the bytes the user actually watches are transferred.
- Simpler content workflow. Editors upload to the Directus file library and reference the UUID. No external accounts needed.
What about size?
The nginx upload limit was bumped to 200 MB so editors can post short videos directly. For longer-form content, host on YouTube and embed the iframe — the sanitiser already permits YouTube domains.