New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spanish translation #25
Comments
Whoa! @erickgnavar that would be awesome! I'm not entirely sure how we'd go about doing that but I will make it a priority this week to investigate. |
Hi! I'd like to help translating too. :) |
@erickgnavar & @ZuraGuerra thanks again for your offer! I was looking into our options for Jekyll and found this blog post. I like the approach outlined as opposed to the traditional i8ln language files. Do either of you have any thoughts? Super excited to get this kicked off. Thanks again 👍 |
Hi, I'm translating this site into Japanese at repos https://github.com/3100/elixir-school and its url is https://3100.github.io/elixir-school . It may be easier to build each language's website as a github project page if you don't care its url, though it will need some changes to work with subdirectory. (See my branch for more detail.) Of cource, I think i18nise is a good way, too. |
@3100 that's awesome! It's great to hear other people are using/enjoying/contributing! I think it's best to keep all of the content together in the same repo. Then we can maximize everyone's efforts and keep lessons in-sync easier. I've got time this week so I'm going to look into ways to handle hosting these different translations on elixirschool.com (and Jekyll). This is really exciting! |
I don't have experience with Jekyll but I think is better have all the translations in the same repo, the files can be separate by folders per language (like the Django Girls tutorial) or follow the the tutorial. |
I haven't used Jekyll either, do you suggest any reading aside from the docs? I also think it would be better to have every language under the same repo. I checked @doomspork link and according to it (please, correct me if I got it wrong) we could add the posts to language folders under lessons/advanced, lessons/basics and lessons/specifics. |
Support for translations has been merged! 🎉 Any suggestions on how about managing this? Should we create GitHub issues for each language and lesson? I'd be glad to add active contributors to the repo to speed things up. |
Awesome, I think that creating a issue per language and lesson is a good idea, I have a few translated lessons I'll make a PR tomorrow. |
Great 🎉 |
@erickgnavar, on which lessons are you working? If you are translating Basics, I can start with the Advanced section tomorrow. |
Yes, I'm working on basic lessons. |
Nice! |
@erickgnavar & @ZuraGuerra I'm going to close this issue now that we've sorted out the translation stuff. I created three separate issues for the actual translations. Let me know your thoughts: #37 — Spanish Basic Lessons |
That's perfect! |
Hi, I would like to contribute to translate the repo to spanish, could you guide me how to proceed?
Thanks
The text was updated successfully, but these errors were encountered: