Change:
## Документация <del> Hackage предоставляет документацию для Haskell </del> <ins> [Haskell.org](https://www.haskell.org/documentation) - книги, курсы по Haskell [Hackage](https://hackage.haskell.org) - пакетный менеджер для Haskell </ins> ## Хотите узнать больше? <del> *   [Ссылка на](https://wiki.haskell.org/Haskell) Haskell wiki </del>  No newline at end of file <ins> *   [wiki](https://wiki.haskell.org/Haskell) Haskell wiki </ins>

Discussion:
We need your help in translating the contributing documentations for Arabic, Chinese, Portuguese, Russian and Spanish. There are the individual issues that you can help on, if you speak any of these: [x] Arabic: [ ] Chinese: [ ] Portuguese: [ ] Russian: [ ] Spanish: Please reach out to us in or for any queries. Happy contributing. There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
i want to help you to translate in spanish, but i cannot see the issue
Hi I have updated the post, thanks.
Hi! I want to help you translate the contributing documentations into Chinese.
you did a great job translating the Guide README to French . Maybe you could help us translate the Contributing Doc to French if you have some time?
Hey ! I'd love to help with translating the Contributing Doc to French, I'm going to start working on it.
I'd love to help with translating the FreeCodeCamp Curriculum in Italian and Romanian, Do you know when we can start working on it and when it will be open to work on?
Hi, and thanks a lot for taking the time to contribute to At the minute we are focused to have translations only in the 5 additional languages as you see on the contributing doc. This is primarily because of the operational logistics involved in maintaining the separate platforms. We want these languages to be ready and stable before going firth with other languages. We will definitely consider additional languages in future, however we do not have any timeline on these. We will make an announcement when that happens. Thanks.
Hi Mrugesh, Thank you for getting back to me. I didn't know all of this and I just sent 2 pull requests for Creating the Romanian and Italian translation for the Contribution Guidelines. Mostly I did it after I read Quincy's article "I just got my free Hacktoberfest shirt. Here’s a quick way you can get yours.". At this point, I don't know if I should continue up to 5 pull requests as it says in the article and you just put it on the side until you are ready to go with the Romanian and Italian versions or I should try other modifications for the pull requests.I'm new myself to all of this stuff and I'm trying to learn as fast as possible.

Please let me know how you like me to proceed or what works best in your interest. Thank you. Linda Kovacs
Hi you should close those PRs. Do not worry, they will still count as valid contributions. And you should proceed with working on other areas. We apologise if this were not clarified in due time, and you had to spend your efforts on this. Thanks once again for all your contributions.
I just closed my PR and . Thank you for your help.
I can help with Arabic translation but I have a problem with Document Direction as Arabic is RTL Language. Is there a solution for this issue ?
I have some problems with my pull request for Created Italian translation for the freeCodeCamp README.MD file. Something went wrong. Could you please help me? Here is the link of the file on Github: Thank you.
I have some problems with my pull request for . Something went wrong. Could you please help me? Thank you.
I don't have any translation skills, but I fixed the links in the READMEs to go to the correct language documents that everyone is doing such an awesome job translating.
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.