Repository files navigation

This repository hosts the English content of the Modern JavaScript Tutorial, published athttps://javascript.info.

74e6955587c79199fea1d11af83805efc3e1b657

Please help us to make the translation better.

<<<<<<< HEAD

• See theSpanish Translate Progress issue.
• Choose an unchecked article you'd like to translate.
• Add a comment to that issue to inform the maintainer that you're translating it.
• Fork the repository, translate and send a PR when done.

🎉 Thank you!

Your name and the contribution size will appear in the "About project" page when the translation gets published.

P.S. The full list of languages can be found athttps://github.com/javascript-tutorial/translate.

Every chapter, an article or a task resides in its own folder.

The folder is namedN-url, whereN – is the number for sorting (articles are ordered), andurl is the URL-slug on the site.

The folder has one of files:

• index.md for a section,
• article.md for an article,
• task.md for a task formulation (+solution.md with the solution text if any).=======We'd like to make the tutorial available in many languages. Please help us to translate.

Seehttps://github.com/javascript-tutorial/translate for the details.

We'd also like to collaborate on the tutorial with other people.

Something's wrong? A topic is missing? Explain it to people, add as PR 👏

You can edit the text in any editor. The tutorial uses enhanced "markdown" format, easy to grasp. And if you want to see how it looks on-site, there's a server to run the tutorial locally athttps://github.com/iliakan/javascript-tutorial-server.

The list of contributors is available athttps://javascript.info/about#contributors.

74e6955587c79199fea1d11af83805efc3e1b657

A file starts with the# Title Header, and then the text in Markdown-like format, editable in a simple text editor.

Additional resources and examples for the article or the task, are also in the same folder.

The translation doesn't have to be word-by-word precise. It should be technically correct and explain well.

If you see that the English version can be improved – great, please send a PR to it.

• Translate comments.
• Translate user-messages and example strings.
• Don't translate variables, classes, identifiers.
• Ensure that the code works after the translation :)

Example:

// Exampleconsttext="Hello, world";document.querySelector('.hello').innerHTML=text;

✅ DO (translate comment):

// Ejemploconsttext='Hola mundo';document.querySelector('.hello').innerHTML=text;

❌ DON'T (translate class):

// Ejemploconsttext='Hola mundo';// ".hello" is a class// DO NOT TRANSLATEdocument.querySelector('.hola').innerHTML=text;

If an external link is to Wikipedia, e.g.https://en.wikipedia.org/wiki/JavaScript, and a version of that article exists in your language that is of decent quality, link to that version instead.

Example:

[JavaScript](https://en.wikipedia.org/wiki/JavaScript) is a programming language.

✅ OK (en -> es):

[JavaScript](https://es.wikipedia.org/wiki/JavaScript) es un lenguaje de programación.

For links to MDN, that are only partially translated, also use the language-specific version.

If a linked article has no translated version, leave the link "as is".

You can run the tutorial locally, to immediately see the changes on-site.

Each of these files starts from the# Main header.

It's very easy to add something new.

💓
Ilya Kantor

74e6955587c79199fea1d11af83805efc3e1b657