-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Feature: Translate guestbook directions into other languages #79
Comments
@CBID2, because this isn't docsify, we might need to approach it in a different way. Do you have a suggestion for how to do that? |
@CBID2 this repo is markdown only, though. I don't think you can do that in markdown. |
@CBID2 here's my suggestion: we make a folder structure that's linked in the ReadMe for the translations. Along with that, we have an issue that's always up that's for translations--we can ask people to comment on the language they would like to work on, and we can add a note that the translations are not actively maintained by the maintainers, but by contributors. So, the folder structure would look like this:
Translations > READMEWelcome to our Guestbook translations! Below, you'll find links to the folders of all the translations we currently have. If you'd like to add a translation, check out this issue.
French Folder
With all that said, I think we should wait for @adiati98's PR, bc we can't translate the CLI, but we can translate manual changes. One thing we need to note is that the info they put in must be in English and appear as exactly as it appears for other contributors. Meaning, the spelling can't change. (It breaks the CLI too--ask me how I found out, lol). |
Great idea @BekahHW! :) We should also wait for French PR that I did with @geoffreylgv |
By the way @BekahHW, @antonio-pedro99 did the Portuguese translation, not @adiati98 lol 😂 |
@CBID2 I know. I was referring to Ayu's PR for this issue |
Ohh thanks for clarifying @BekahHW. Lol, silly me 🤦🏾♀️ |
|
The issue just got the green light today. So I haven't worked on it yet as I was outside the whole day 🙂 |
Ah great. I always find myself to be more focused after exercising outside |
For the project structure related to the translations, we can have like @BekahHW said, Also, in the |
Hey @BekahHW! 😊 Once and if we get more volunteers to translate, OpenSauced should definitely consider implementing Crowdin. One of the translate leads from FreecodeCamp has shown me how they implement it: https://contribute.freecodecamp.org/#/how-to-translate-files |
@CBID2 I did look into Crowdin. I think we need to make sure there's interest. I'm super excited to have folks interested in translating, but we need to gauge how many people are using the translated versions as part of the discussion. Maybe we should consider adding something to the PR template to ask them to select the language they used to complete the task. |
That's a great idea! :) I do a PR for that part if you'd like. |
@CBID2 that would be great! |
Type of feature
🍕 Feature
Current behavior
The guestbook directions are written only in English, which can make new open source contributors, especially those who have English as a second language or do not speak it all.
Suggested solution
In the spirit of @antonio-pedro99's suggestion in issue #16 of the intro course's repo, I think it would be helpful to have the directions for the guestbook in Portuguese.
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: