Editorial team: who writes the Banned.Video guides
Bylines on Banned.Video name editorial teams, not invented personas. Each team writes about the work it knows.
Two teams write every Banned.Video guide. The Banned.Video Editor covers hosting, uploads, formats, streaming, players and quality. The Creator Desk covers running a channel.
Infrastructure and playback. The engineers who run Banned.Video's upload, encoding and delivery pipeline. They write about what the platform actually does: formats, transcoding ladders, HLS delivery and the trade-offs behind each choice.
Video encoding, adaptive streaming, storage and CDN deliveryCreator growth and channel strategy. The team that supports channels on Banned.Video. They write practical guidance on starting a channel, titles, thumbnails, publishing habits, analytics and the ways creators earn from video.
Channel growth, audience retention, monetisationThe two editorial teams
Each team writes about the work it does on Banned.Video. That way, the people closest to a system explain it.
Banned.Video Editor
The Banned.Video Editor writes guides on hosting, uploading, formats, streaming, players and quality. It runs the systems it writes about, so its guides describe how video really moves from a file to a screen. Read more on the Banned.Video Editor page.
Banned.Video Creator Desk
The Creator Desk writes Banned.Video's guides for people who run a channel. It covers how to start, how to be found and chosen, how to read your numbers and how creators earn. Read more on the Creator Desk page.
| Desk | Guide hubs | Expertise |
|---|---|---|
| Banned.Video Editor | Video hosting, Uploading video, Formats and codecs, Streaming and HLS, Player and embedding, Quality and resolution | Video encoding, adaptive streaming, storage and CDN delivery |
| Creator Desk | Creators | Channel growth, audience retention, monetisation |
Why bylines name teams, not people
Each desk works on the part of Banned.Video it writes about, so the byline names the team. In our structured data, each desk is marked up as an organisation, never as a person.
We will not invent writers, job titles or awards to make a page look more trusted. The facts in a guide have to earn that trust on their own.
How the desks check facts
- Technical claims are checked against specifications and official documents, and each guide lists its sources.
- When a guide says what Banned.Video does, it describes the live product, not a plan.
- Mistakes are fixed in place, and the guide's updated date changes.
The full rules are in the editorial policy. To browse everything the desks have written, start at the guides index.
