Spanish Translation Progress

[tesseralis]

🚨 Please Read this before contributing 🚨

Maintainer List

• @alejandronanez
• @carburo
• @dmoralesm
• @Darking360

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below. Do not create new issues claiming for new work please, let's keep everything here. If you already have an issue opened, please close it after your PR gets merged 🎉. Thanks!
2. Comment below with the name of the page you would like to translate. Take only one page at a time.
3. Submit a PR, assign @dmoralesm, @carburo, @Darking360 or @alejandronanez and add a link to it to your comment!

Please check the style guide to make sure translations are written in a consistent manner.

Also, check out the Crowdin repository before starting the translation of a new article. Click and open each article to see how much work has been actually done. "0%" in the index page does not mean the article has not been translated!

Work List

(🏃 Work in Progress; 👀 In Review)

Core Pages

To do before releasing as an "official" translation. Please translate these pages first.

• [x] Home Page (@Zitle-Nancy) #123
• [x] Tutorial (@ivandevp) #83

Basics

• [x] Hello World (@alejandronanez) #5
• [x] Introducing JSX (@icarlossz) #8
• [x] Rendering Elements (@shmesa22) #9
• [x] Components and Props (@EzequielMonforte) #10
• [x] State and Lifecycle (@carburo) #62
• [x] Handling Events (@shmesa22) #77
• [x] Conditional Rendering (@ElRodrigote) #19
• [x] Lists and Keys (@EzequielMonforte) #22
• [x] Forms (@Darking360) #132
• [x] Lifting State Up (@sigfriedCub1990) #135
• [x] Composition vs Inheritance (@jesgarciamartinez) #150
• [x] Thinking in React (@sergiodxa) #27

API Reference

• [x] React (@karolincastano) #139
• [x] React.Component (@semoal) #61
• [x] ReactDOM (@Darking360) #33
• [x] ReactDOMServer (@devrchancay) #110
• [x] DOM Elements (@LuisRevillaM) #59
• [x] SyntheticEvent (@michaelcavallaro03) #29
• [x] Test Utilities (@d4vsanchez) #73
• [x] Shallow Renderer (@tmjoseantonio) #130
• [x] Test Renderer (@elyalvarado) #37
• [x] JS Environment Requirements (@angelitaooo) #87
• [x] Glossary (@dmoralesm) #1 https://github.com/reactjs/es.reactjs.org/pull/16

Navigation

These are the navigation links that appear in the sidebar. Possibly wait until the corresponding sections are translated to do these.

• [x] tutorial/nav.yml (@ivandevp) #83
• [x] docs/nav.yml (@devrchancay) #155

Next Steps

These are the next most important translations, ordered by importance:

Installation

• [x] Getting Started (@Darking360) #76
• [x] Add React to a Website (@d4vsanchez) #148
• [x] Create a New React App (@elyalvarado) #68
• [x] CDN Links (@loconluis) #142

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

• [x] Introducing Hooks (@KevinGomezDev) #156
• [x] Hooks at a Glance (@GiuMagnani) #70
• [x] Using the State Hook (@a13marquez) #60
• [x] Using the Effect Hook (@escorponox) #66
• [x] Rules of Hooks (@icarlossz) #71
• [x] Building Your Own Hooks (@EzequielMonforte) #34
• [x] Hooks API Reference (@jvelezpo) #35
• [x] Hooks FAQ (@caal-15) #151

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.

• [x] dont-call-proptypes (@jvelezpo) https://github.com/reactjs/es.reactjs.org/pull/81
• [x] invalid-aria-prop (@jvelezpo) https://github.com/reactjs/es.reactjs.org/pull/81
• [x] invalid-hook-call-warning (@jpvg10) #141
• [x] legacy-factories (@jpvg10) #138
• [x] refs-must-have-owner (@jvelezpo) https://github.com/reactjs/es.reactjs.org/pull/81
• [x] special-props (@jvelezpo) #69
• [x] unknown-prop (@jvelezpo) #69

Advanced Guides

• [x] Accessibility (@ElRodrigote) #74
• [x] Code-Splitting (@LuisRevillaM) #145
• [x] Context (@ricardoerl) #78
• [x] Error Boundaries (@jesgarciamartinez) #147
• [x] Forwarding Refs (@elyalvarado) #72
• [x] Fragments (@RamirezAlex) #82
• [x] Higher-Order Components (@elyalvarado) #125
• [x] Integrating with Other Libraries (@jvelezpo) #175
• [x] JSX In Depth (@jvelezpo) #128
• [x] Optimizing Performance (@RamirezAlex and @DanielGarc) #191
• [x] Portals (@khriztianmoreno) #131
• [x] React Without ES6 (@adielhercules) #118
• [x] React Without JSX (@vickvasquez) #120
• [x] Reconciliation (@devrchancay) #152
• [x] Refs and the DOM (@Darking360) #86
• [x] Render Props (@jonathanpalma) #182
• [x] Static Type Checking (@Paolore) #136
• [x] Strict Mode (@d4vsanchez) #126
• [x] Typechecking With PropTypes (@jnosornov) #113
• [x] Uncontrolled Components (@Paolore) #117
• [x] Web Components (@Paolore) #88

FAQ

• [x] APIs and AJAX (@kevinwolfcr) #2
• [x] Babel, JSX, and Build Steps (@loconluis)
• [x] Passing Functions to Components (@florenciasilva) #124
• [x] Component State (@GiuMagnani) #75
• [x] Styling and CSS (@GiuMagnani) #108
• [x] File Structure (@GiuMagnani) #121
• [x] Versioning Policy @alejandrogarciasalas #154
• [x] Virtual DOM and Internals @giossa94 #133

Contributing

Priority: Low

• [x] How to Contribute (@maudel) #153
• [x] Codebase Overview - (@jnosornov) #186
• [x] Implementation Notes (@devrchancay and @marcorichetta)
• [x] Design Principles (@elyalvarado) #146

Components

Components in src/components that have some text in them.

• [x] CodeEditor (@icarlossz) #164
• [x] CodeExample (@icarlossz) #164
• [x] ErrorDecoder (@icarlossz) #164
• [x] LayoutFooter (@Zitle-Nancy) #160
• [x] LayoutHeader (@Zitle-Nancy) #160
• [x] MarkdownPage (@icarlossz) #164

Additional Translations

Community Resources

• [x] Support
• [x] Courses
• [x] Examples
• [x] Meetups
• [ ] Conferences
• [x] Articles
• [x] Podcasts
• [x] Videos
• [x] External Resources

Tools

• [ ] Debugging
• [ ] Component Workbenches
• [ ] JSX Integrations
• [ ] Starter Kits
• [x] Routing
• [ ] Model Management
• [ ] Data Fetching
• [x] Testing
• [ ] UI Components
• [ ] Miscellaneous

Blog

• [x] Is React Translated Yet? (@carburo)
• [ ] React v16.8
• [ ] React v16.7
• [ ] React 16 Roadmap
• [ ] React Conf Recap
• (and more...)

[simonhoyos]

I would like to work on Introducing JSX

[alejandronanez]

Hey @shmesa22, I updated the description with your name on it! Thanks for helping us! 👍

Introducing JSX is issue https://github.com/reactjs/es.reactjs.org/issues/7

Let us know if you have any questions!

[icarlossz]

Hey @shmesa22, I didn't see your comment and I started with that one. Sorry.

[EzequielMonforte]

Hi. I want to work on Components and Props

[simonhoyos]

@icarlossz, no worries. I haven't started working on it, I can take another one

[simonhoyos]

I would like to work on Rendering Elements then

[tesseralis]

~~@shmesa22 @EzequielMonforte are you able to edit the issue to add your name on it?~~

Never mind, seems like you can't. Can you create issues for the pages you would like to translate and assign yourselves?

[simonhoyos]

Hi @tesseralis, I was able to create the issue, but not to assign it to me

[simonhoyos]

Hi everyone, any thoughts or any good translation for callback?

[sergiodxa]

I would like to work in Thinking in React

[sergiodxa]

@shmesa22 I'm not sure there is a good translation for that, the correct one would be llamar de vuelta, maybe paraphrasing it it could fit in the sentence, however callback is a word commonly used in Spanish communities too so it may be an option avoid translating it.

[simonhoyos]

Thank you @sergiodxa, that's what I was thinking. I left it like that.

Also, I would like to start working on handling events.

[tesseralis]

@shmesa22 Once it's done, we should have the glossary as a reference on how to translate common terms. @dmoralesm how is that progress going?

[simonhoyos]

@tesseralis any way we can add or recommend words for the glossary?

[sergiodxa]

who is going to create the glossary? what's the criteria?

[tesseralis]

@shmesa22 The original English glossary or the Spanish version? The Spanish docs should just be translation of the English version.

@sergiodxa The "glossary" in question is the translation of the version in the English docs: https://reactjs.org/docs/glossary.html

Currently @dmoralesm is assigned to translate it but if it's not done soon we should hand over the work to someone else.

[dmoralesm]

@shmesa22 Once it's done, we should have the glossary as a reference on how to translate common terms. @dmoralesm how is that progress going?

I'm about to finish

[sergiodxa]

I mean "a reference on how to translate common terms" that glossary.

[simonhoyos]

Same here, I was thinking on some glossary on how to translate words like callback or camelCase

[sergiodxa]

mock too

[sergiodxa]

Or at least define what words not to translate because they are used as is in Spanish

[tesseralis]

We'll probably have a TRANSLATION folder with style-guide.md and other useful guides in there. Let me get that set up.

[sergiodxa]

Great!

I have another question, what about links to external sites? In Thinking in React there is a link to a Wikipedia page which has a Spanish translation, should I change the link to the Spanish version? or keep the English one?

[tesseralis]

@sergiodxa that seems like a good idea, but I'll leave it to more experienced translators. We can also put our decision in the style guide!

[sergiodxa]

Also what about text in block codes?

[
  {category: "Sporting Goods", price: "$49.99", stocked: true, name: "Football"},
  {category: "Sporting Goods", price: "$9.99", stocked: true, name: "Baseball"},
  {category: "Sporting Goods", price: "$29.99", stocked: false, name: "Basketball"},
  {category: "Electronics", price: "$99.99", stocked: true, name: "iPod Touch"},
  {category: "Electronics", price: "$399.99", stocked: false, name: "iPhone 5"},
  {category: "Electronics", price: "$199.99", stocked: true, name: "Nexus 7"}
];

That's also in Thinking in React, should I translate the categories and names? (when they are not direct product names) I read on the main issue they will be copied as if in the future they are modified on the original version, also since it's data it could be left as is as an example.

[tesseralis]

@sergiodxa maybe reference translations in other sites/languages to see what they do? Or see if you can find style guides from other technical projects we can use as a base for ours.

[gariasf]

Also what about text in block codes?

[
  {category: "Sporting Goods", price: "$49.99", stocked: true, name: "Football"},
  {category: "Sporting Goods", price: "$9.99", stocked: true, name: "Baseball"},
  {category: "Sporting Goods", price: "$29.99", stocked: false, name: "Basketball"},
  {category: "Electronics", price: "$99.99", stocked: true, name: "iPod Touch"},
  {category: "Electronics", price: "$399.99", stocked: false, name: "iPhone 5"},
  {category: "Electronics", price: "$199.99", stocked: true, name: "Nexus 7"}
];

That's also in Thinking in React, should I translate the categories and names? (when they are not direct product names) I read on the main issue they will be copied as if in the future they are modified on the original version, also since it's data it could be left as is as an example.

I would leave code as is with the exception of comments.

[dmoralesm]

I would leave code as is with the exception of comments.

I agree with @gariasf

[tesseralis]

@sergiodxa @shmesa22 I added TRANSLATION.md as a source for translation information, including a style guide: https://github.com/reactjs/es.reactjs.org/blob/master/TRANSLATION.md. Feel free to edit and suggest style guide tips.

[dmoralesm]

@sergiodxa @shmesa22 I added TRANSLATION.md as a source for translation information, including a style guide: https://github.com/reactjs/es.reactjs.org/blob/master/TRANSLATION.md. Feel free to edit and suggest style guide tips.

@tesseralis I would like to create a list of words that we must avoid to translate, such as string or callback. Is TRANSLATION.md a proper place to do it?