This is my first Pull Request.

This is the page I translated. The MDN Web Media documentation offers comprehensive guides and reference materials for implementing and controlling audio, video, streaming, and related media technologies in web applications.

Before attempting to translate the page, I thoroughly wen through all of the rules about translating:

https://github.com/mdn/translated-content/blob/main/CONTRIBUTING.md

https://github.com/mdn/translated-content/blob/main/docs/README.md

This is the pipeline I followed:

The navigation and execution were pretty straightforward, but since it was my first time translating it, I was a bit unsure about the accuracy and correctness of my translation, considering that the text consisted of a lot of technical terms. I forked both of the repositories (source one and the translated content one) -> copied the source file to the translation-content repository -> edited the source commit, and the front matter of the document -> checked the layout of the translated page locally -> pushed my changes -> created the pull request.

The page is 71 line long and did not consist any of the code or difficult technical terms.

Checks: Automated CI validated Markdown syntax, linting, and link integrity.

Before pushing in order to check if the layout of the page is correct and there have been no mistakes, MDN community uses a simple shell command (echo … >> .env) to create a dotenv file that defines the CONTENT_TRANSLATED_ROOT environment variable (pointing the preview server at your local copy of the translated-content files), and then run yarn start (invoking the project’s Node-based dev server) to load those settings and serve the translated MDN site at http://localhost:5042 for live testing. I used it to check if the layout is correct and there are no visual errors.

After I created my PR, it was automatically checked on Automated CI-validated Markdown syntax, linting, and link integrity. Afterwards, I was assigned a reviewer.