Video Editorial Guidelines
It is important to understand the subject matter you are producing content for so learners of any experience level can grasp the material. The better you know the content, the easier it is to introduce new material and keep learners engaged. By using clear examples, simple word choice, and digestible sentences, you can create a better learner experience.
In video lessons, you’ll speak to learners as "Codecademy". We want to empower, educate, and guide our learners through our content so they can use what they learn in the real world. You should have an enthusiastic, energetic, and kind tone—some fun is encouraged! Think of Codecademy's voice as a brainy, empathetic friend.
- Please record using QuickTime Player recording software for Mac OS or Windows OS. You can find a video tutorial on how to record your screen with a voice-over.
- Please export all recordings with the 1080p aspect ratio (also known as 1920 pixels by 1080 pixels)
The voice of your video content should use the royal we.
Unless you are addressing the learner in a specific task, you should never use the second person or the first person singular. For example, in an assessment or a project step, you may say, “You should create…“ in reference to what the learner specifically needs to do. You should use “we” throughout the rest of the video and article instruction. For example, “Now we want to check that the variable has been....” or “If we wanted to define…”.
The tone of the video should be:
- Encouraging, but not patronizing
- Confident, but not brash
- Smart, but not stiff
- Fun, but not silly
- Informal, but not sloppy
- Expert, but not bossy
- Optimistic, but not hollow
At Codecademy, we strive for inclusivity and accessibility in our content! We trust you to use your best judgment during content production, however, some inclusivity pitfalls are less obvious. The content should:
- Be culturally sensitive
- Avoid addressing narrow demographics
- Avoid niche or cultural references (e.g. memes, country-specific idioms)
- Avoid negative language (e.g. "that was lame", "that's crazy", or references to mental illnesses or any disabilities)
Never refer to code the learner hasn’t seen very recently. This is important. Your example code may feel vivid to you, but that does not mean it's as easy for a learner to recall.
This content will be taken by learners with different technical backgrounds and frames of reference. If you feel strongly that some content covered in a video will be essential to some learners but irrelevant to others, consider whether it’s possible to cut the video up into smaller, well-labeled, chunks.
- Wear headphones or a lapel microphone to reduce background noise during recording.
- Your recording should sound well-prepared and confident. Avoid filler sounds like “umms” and “uhhs”. Also avoid recording background noises, hums, or echo sounds.
- Avoid making mistakes while recording. If you misspeak or mistype, please reshoot rather than record yourself debugging.
- Note: Consider breaking the script down into small sections that you record individually. It can also be helpful to record the audio and visual components separately.
- Use clear diction and avoid slurring your words.
- Speak with a consistent volume throughout the recording.