Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

We would like to keep the list small and focused to the best resources. Reason: We don’t want to frustrate people who like to learn JavaScript with a list that:

• is too long to get through
• offers too many possibilities

Ensure your pull request adheres to the following guidelines, if you would like to add something that must be on that list:

• Search previous suggestions before making a new one, as yours may be a duplicate.
• If you just created something, wait at least a couple of weeks before submitting.
• You should of course have read, watched or used the thing you're submitting.
• Make an individual pull request for each suggestion.
• Use the following format: [name](link) - Description.
• Keep descriptions short and simple, but descriptive.
• Start the description with a capital and end with a full stop/period.
• Check your spelling and grammar.
• Make sure your text editor is set to remove trailing whitespace.
• Link additions should be added to the bottom of the relevant section.
• New categories or improvements to the existing categorization are welcome.
  • To regenerate the table of contents:

    • npm install
      npm run toc
      

• Pull requests should have a useful title and include a link to the resource and why it should be included.

Thank you for your suggestion!

A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. There's no need to open a new PR, just edit the existing one. If you're not sure how to do that, here is a guide on the different ways you can update your PR so that we can merge it.