Add Sign Language Video Style Guide to index.md #3313
Conversation
added the sign language video style guide
Deafveloper
requested review from
caniszczyk,
seokho-son,
iamNoah1,
jihoon-seo,
nate-double-u and
castrojo
as code owners
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Deafveloper
changed the title
Deleted extra space and made the text bold with the bullet points. Signed-off-by: Destiny O'Connor <[email protected]>
changed the heading into regular text under the SL video guide heading Signed-off-by: Destiny O'Connor <[email protected]>
content/en/style-guide/_index.md
Outdated
| ## Sign Language Video Style Guide {#sign-language-style-guide} | ||
|
|
||
|
|
||
| ### If you are contributing a sign language video, please follow these guidelines to ensure our videos are clear, informative, and accessible to a wide audience (Including hearing community members). |
There was a problem hiding this comment.
I don't think this part needs to be in bold.
|
Hi @Deafveloper, this PR includes many commits from other contributors. :) Let me check if simply changing the target branch to main branch will fix the issue. (I don't mind if we use the main branch directly.) |
|
Yes, the base branch of your local/feature is main. You can see this PR includes your commits only. So, we either need to change the target branch of this PR (which I’ve already done) or change your base branch to dev-sign (though this isn't simple). Why don’t we just use the main branch for this PR? We can decide when to merge it once the reviews are completed. |
|
@seokho-son Yes that is exactly what happened. I changed the branch after my commit. I’m still getting the hang of the Git/GitHub branch concepts, so I appreciate your patience. I’m happy to learn and follow any steps you suggest. Thanks again for your help! |
|
|
||
|
|
||
| * **Signing Space:** Use as much space as possible, ensuring you have full signing space while sitting or standing. | ||
|
|
There was a problem hiding this comment.
-
Lighting: Use frontal lighting to ensure your face and hands are well-lit.
-
Background: Record in front of a flat, solid background to avoid distractions from the signing. Ensure no distracting decorations are included.
-
Dress Code: Wear a solid, single-color top (no prints) that contrasts with your skin tone.
-
Camera Position: Ensure that your head to your elbows are visible on the screen, and position the camera at eye level. The camera should be perpendicular to the background so that it appears straight, not slanted.
-
Signing Space: Use as much space as possible to ensure you have full signing space while sitting or standing.
| * **Fingerspelling:** Use sign language for the word as much as possible as fingerspelling is the last resort, commonly reserved for abbreviated or short words. | ||
|
|
||
|
|
||
| * **Posture:** While signing, only maintain frontal orientation with eyes facing the camera while positioned. Demonstrating signs using side orientation is unnecessary. When at rest, arms should be down with hands relaxed. |
There was a problem hiding this comment.
Signing
-
Clarity and Accuracy: Record the sign twice from a frontal orientation, signing slowly enough for non-signers to see and mimic it. Demonstrating signs from the side is unnecessary unless it adds clarity.
-
Facial Expression: Use natural facial expressions and avoid exaggerations or grimaces that might distract. Maintain eye contact with the camera if possible.
-
Frequency: Only one sign is needed for each video, as playback can be looped. Repeating the sign within a video is unnecessary.
-
Duration: The total length of the video should not exceed 7 seconds.
-
Fingerspelling: Use sign language for the word as much as possible. Fingerspelling is a last resort, commonly reserved for abbreviated or short words.
-
Posture: Maintain a frontal orientation with eyes facing the camera while signing. When at rest, arms should be down with hands relaxed.
| * **Save storage space:** Please remember the shorter the video, the smaller the file would be. The quicker it would be when uploading. | ||
|
|
||
|
|
||
| * **Mistakes are good:** Keep the recording running while making several attempts. It is more likely you will find a good clip in between several tries and you would only need to trim the unwanted parts out. This is more efficient than making multiple recordings with one sign attempt in each. |
There was a problem hiding this comment.
Tips
-
Save Storage Space: Remember that the shorter the video, the smaller the file size will be, and the faster it will upload.
-
Mistakes Are Good: Keep the recording running while making several attempts. This increases the likelihood of capturing a good clip between tries, and you can trim unwanted parts later. This is more efficient than making multiple recordings with one sign attempt in each.
-
Video Examples: Please refer to the CNCF Glossary: Cloud Native Signs playlist for examples.
|
|
||
| * **Upload:** Please do not upload the videos to your personal YouTube as YouTube could potentially remove duplicate videos from all accounts using the same videos (to prevent monetizing abuse) as CNCF uses YouTube to upload final videos. | ||
|
|
||
|
|
There was a problem hiding this comment.
Post-Production
-
Editing: If necessary, trim the beginning and the end of the video.
-
Label: At a minimum, the filename of the video should contain the glossary term of the sign before uploading. For example,
kubernetes.mp4. -
Audio: Remove the audio track entirely, if possible.
-
Upload: Share the video on the #glossary-sign-language Slack channel and ask for feedback. If approved, the Sign Language Glossary leads will help you upload the video to the CNCF Playlist. Please do not upload the videos to your personal YouTube account, as YouTube could potentially remove duplicate videos from all accounts using the same content (to prevent monetization abuse), and CNCF uses YouTube to upload final videos.
added the sign language video style guide
Describe your changes
Added an anchor link under Audience and added the video style guide after getting started with a google doc
Related issue number or link (ex:
resolves #issue-number)related to issue #3040
Checklist before opening this PR (put
xin the checkboxes)git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to yourgitconfigby runninggit config --global alias.ci "commit -s".