Open samucodesh opened 7 months ago
Name | Link |
---|---|
Latest commit | 78fda64a1c67d29d687fb75b92041184d9b438bb |
Latest deploy log | https://app.netlify.com/sites/sauced-intro/deploys/665556fe8fbae400081ff18d |
Deploy Preview | https://deploy-preview-115--sauced-intro.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Hi @samucodesh! :) Thanks for your translation! :) Can you link the corresponding issue in the Related Documents & Tickets section of your PR form?
Hi @samucodesh! :) The only piece of feedback is that we want to keep the word "open source" in English so turn
cΓ³digo abierto
back into English please.
Hi @CBID2 I understand, I will make the changes and make a new PR in the next few days
Hi @samucodesh! :) The only piece of feedback is that we want to keep the word "open source" in English so turn
cΓ³digo abierto
back into English please.Hi @CBID2 I understand, I will make the changes and make a new PR in the next few days
You can just make the changes in this one @samucodesh.
Hi @CBID2 ! Is it necessary to update the French translation files? (I do not speak French)
Hi @CBID2 ! Is it necessary to update the French translation files? (I do not speak French)
README
Navbar
Hi @samucodesh. Just focus on Spanish :)
So that's all for now, I'm looking forward to your comments.
Thank you very much for your feedback! @Mike-Salcedo @CBID2
Hey @samucodesh. Donβt forget to update your branch
Hey @samucodesh. Donβt forget to update your branch
Mission accomplished @CBID2 π«‘
@Mike-Salcedo are there still changes you want to see?
It took me several weeks to update my branch, I look forward to your feedback
Hey @samucodesh,
Thank you so much for the PR and for your initiative to update this branch with our latest changes! We truly appreciate it! β¨
We're sorry that our @open-sauced/docs team still have no time and resources to review your PR.
Also, heads up, we will have more (big) updates to come in the next few months. So, we're wondering if you're interested in hosting and maintaining this Spanish translation yourself in your forked repo as one of our community translations.
The benefit of doing so are:
Please let us know what do you think and we can discuss further from there.
Thank you! π
Absolutely! I completely understand about the @open-sauced/docs team's workload. I'd be thrilled to host and maintain the Spanish translation in my forked repo as a community translation. This would be a fantastic learning experience for me, and I'm confident I can get the Spanish version out quickly. I'm also happy to handle future updates as they come. Thank you so much for the opportunity!
Absolutely! I completely understand about the @open-sauced/docs team's workload. I'd be thrilled to host and maintain the Spanish translation in my forked repo as a community translation. This would be a fantastic learning experience for me, and I'm confident I can get the Spanish version out quickly. I'm also happy to handle future updates as they come. Thank you so much for the opportunity!
Thank you so much for your interest! β¨
This will be the pilot of our community translations and I'm as much as excited as you! π₯³
That said, you can start with getting ready to maintain and host the Spanish translation on your forked repository. ππ½
Please be noted, this is also new for me, so I still try to find the best way to do this. But I'll do my best to support you whenever I can! I'll document the process so we can help other translations. So, please keep me in the loop with the process in this discussion! π
Hey @samucodesh,
Heads up. I'm coverting this PR as draft as we're discussing on moving this as community translations. Thanks! π
Description
This PR adds a Spanish translation for the course. This will help Spanish and Latin Americans contributors start their journey towards open source.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Closes #116
Mobile & Desktop Screenshots/Recordings
README
navbar
sidebar
Steps to QA
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?