-
Notifications
You must be signed in to change notification settings - Fork 83
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
[OLD] Legacy Italian Translation Progress #1
Comments
Fantastic! Thanks @tesseralis ! Actually, I already have Homepage ready for review and around 40% of the tutorial. I'll update the issue later. @LucaBlackDragon, please pick something else so that we don't do things twice! 👍 Obviously, I'll ask you to review. Ciaoo! |
@tesseralis thank you! |
I have also opened and pinned two issues for the Style Guide and Glossary, should we need it |
Great! I can see some very good progress here already. I have updated the issue adding work items tracking emojis (not super useful now that it's just the two of us but I reckon it will help loads when we will have many contributors 😄 hopefully!) |
I have created a new PR (#8), also removed the tracking emojis just because... better to use tags. I will copy a few of the tags used by our Brazilian friends and let's see how that goes! 😉 |
Hey! Can I join? I'd like to help translate a page too. |
Hi @medenagan ! Of course! Feel free to pick a page from the list and follow the instructions, shout if you need help with anything. |
Added CircleCI webhook |
@deblasis @LucaBlackDragon cool! Is it okay if I pick |
Ok I'll assign that page to you! Just be sure to read the style guide and glossary before beginning to translate (and feel free to contribute to those too) |
Hi guys! I think we need to attract more people, we need help! I was thinking about creating issues with the flags "help wanted" and "good first issue" for all the open/unassigned tasks in the progress issue. I know that there are a lot of people that search for those tags in order to find projects to contribute on. Then I thought... I can automate this thing and maybe other teams could find this script useful! So... I am gonna run it then I'm gonna shout about it and let's see what happens :D perhaps you guys could do the same! |
Ciao! Can I start working on Hooks -> Rules of Hooks #47 ? |
Ciao @hawz ! Sure, all yours. |
Hi @acifani, sure! |
Hi! Can I take Fragments #63? I have already translated it |
Ciao! Can I start working on #65 ? @deblasis @LucaBlackDragon @lssmn Is still open this project? |
Ciao! Can I start working on #58 ? @deblasis @LucaBlackDragon @lssmn |
Ciao! Can I start working on #59 ? @deblasis @LucaBlackDragon @lssmn |
Ciao! Can I work on #60 ? I have already translated it @deblasis @LucaBlackDragon @lssmn |
Ciao! Can I start working on #61 ? @deblasis @LucaBlackDragon @lssmn |
Ciao, can I take Reconciliation #71 ? |
Ciao @DennisBoanini ! All yours 👍 |
Hello 😊, I would love to start working on FAQ page number #79. |
Ciao! Can I start working on #84 ? |
Hi, absolute beginner here trying to make his first steps in the open source world. I would like to be assigned on #83, 'FAQ - Styling and CSS' |
Ciao! Can I start working on #70 ? |
👋 Benvenuto! |
All yours @mattia-sanfilippo ! |
Ciao! We are now translating the new website that's currently in beta! (https://beta.reactjs.org/) All the ongoing translations are suspended as it only makes sense to focus on the new website content as described here. This issue has been updated. More info in #328 |
Ciao @LucaBlackDragon e @lssmn ! Long time no see!! Come va? Siete ancora interessati a collaborare? Ho appena creato la PR #374 e mi farebbe piacere che qualcuno gli dia uno sguardo :) Nessun problema se non avete tempo. |
Thanks to everyone who contributed to the old website translation! |
Maintainer List
For New Translators
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
Beta website (https://beta.reactjs.org/)
We are now focusing our translation efforts on the new Beta website.
The new docs aren't fully written yet, and some parts will definitely change. However, a lot of the pages are already "stable". We suggest to use this checklist for the beginning. ✅ means "ok to translate", 🔴 means "don't translate yet".
Legacy website
Emojis:
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.
Tutorial
page #6Basics
Introducing jsx
page #14Rendering Elements
page #16API Reference
Navigation
These are the navigation links that appear in the sidebar. Possibly wait until
the corresponding sections are translated to do these.
Next Steps
These are the next most important translations, ordered by importance:
Installation
Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
Warnings
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.
Advanced Guides
FAQ
Contributing
Priority: Low
Components
Components in
src/components
that have some text in them.Additional Translations
These are not the primary translation targets.
The text was updated successfully, but these errors were encountered: