Bulgarian Translation Progress

[tesseralis]

Maintainer List

• @krasimir
• @RStankov
• @jumpalottahigh
• @kdichev
• @andrey-andreev
• @ValGeorgiev
• @deyan-a

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
3. Clone this repo, translate your page, and submit a pull request!

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 anymore, let the maintainers know so they can assign the page to someone else.

For Maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

• Home Page (@tesseralis) Bulgarian Translation Progress #1

When PRs are merged, make sure to mark that page as completed!

Core Pages

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

• Home Page (@krasimir) Превод на началната страница. #5
• Tutorial (@krasimir) Translating tutorial page #10

Basics

• Hello World (@jumpalottahigh) Translate hello-world page #7
• Introducing JSX (@jumpalottahigh) Translate introducing JSX #15
• Rendering Elements (@krasimir) Translating rendering elements #13
• Components and Props (@kdichev) Add Components and props translation #17
• State and Lifecycle (@andrey-andreev) Translate state and lifecycle page #18
• Handling Events (@jumpalottahigh) Translate handling events #27
• Conditional Rendering (@andrey-andreev) Translating conditional rendering page #22
• Lists and Keys (@krasimir) List and keys #20
• Forms (@kdichev)
• Lifting State Up (@andrey-andreev) Translate lifting state up page #24
• Composition vs Inheritance (@krasimir) Translating composition vs inheritance #23
• Thinking in React (@ValGeorgiev) Translate thinking in react page #26

API Reference

• React
• React.Component (@jumpalottahigh)
• ReactDOM (@ValGeorgiev) ReactDom translation #28
• ReactDOMServer (@ValGeorgiev) translate ReactDomServer #32
• DOM Elements (@deyan-a) Translated reference-dom-elements.md to Bulgarian #36
• SyntheticEvent (@krasimir) Translating synthetic event #29
• Test Utilities (@ValGeorgiev)
• Shallow Renderer (@ValGeorgiev) Translate Shallow Renderer #35
• Test Renderer (@ValGeorgiev) translate test-renderer #33
• JS Environment Requirements (@ValGeorgiev) Translate JS environment requirenments #34
• Glossary (@deyan-a) Bulgarian translation of reference-glossary.md #50

Navigation

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

• tutorial/nav.yml
• docs/nav.yml

Next Steps

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

Installation

• Getting Started (@deyan-a) chore: translate getting-started.md #206
• Add React to a Website (@deyan-a)
• Create a New React App
• CDN Links

Hooks

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

• Introducing Hooks
• Hooks at a Glance
• Using the State Hook
• Using the Effect Hook
• Rules of Hooks
• Building Your Own Hooks
• Hooks API Reference
• Hooks FAQ

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.

• dont-call-proptypes
• invalid-aria-prop
• invalid-hook-call-warning
• legacy-factories
• refs-must-have-owner
• special-props
• unknown-prop

Advanced Guides

• Accessibility
• Code-Splitting
• Context
• Error Boundaries
• Forwarding Refs
• Fragments
• Higher-Order Components
• Integrating with Other Libraries
• JSX In Depth
• Optimizing Performance
• Portals
• React Without ES6
• React Without JSX
• Reconciliation
• Refs and the DOM
• Render Props
• Static Type Checking
• Strict Mode
• Typechecking With PropTypes
• Uncontrolled Components
• Web Components

FAQ

• APIs and AJAX
• Babel, JSX, and Build Steps
• Passing Functions to Components
• Component State
• Styling and CSS
• File Structure
• Versioning Policy
• Virtual DOM and Internals

Contributing

Priority: Low

• How to Contribute
• Codebase Overview
• Implementation Notes
• Design Principles

Components

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

• CodeEditor
• CodeExample
• ErrorDecoder
• LayoutFooter
• LayoutHeader
• MarkdownPage

Additional Translations

These are not the primary translation targets.

• Blog
• Community

[tesseralis]

@krasimir, @RStankov please use this issue to keep track of your progress!

[krasimir]

• Home Page (@krasimir)

[tesseralis]

@krasimir you should be able to edit the issue directly like so:

[krasimir]

@tesseralis I think I don't have the rights to do it

(or maybe it's me not clicking the right button :) )

[tesseralis]

@krasimir you need to accept the invite to join the "reactjs" organization. Check your email! If you can't find it, let me know and I can invite you again.

[krasimir]

@tesseralis thank you for the clarification. It looks like I didn't get the email. I checked also my spam folder but there is no such email. Can you re-send the invite please.

[tesseralis]

@krasimir resent!

[krasimir]

Yep, this time it worked. Thanks!

[jumpalottahigh]

Hi, all! @tesseralis I could help out with reviews (and translations) too. Could you please add me to the team?

[tesseralis]

Yup! Just submit a pull request to reactjs.org-translation and edit the bg.json file with your name on it!

[jumpalottahigh]

I'd like to work on the Hello World translation to get things started, could anyone add my name to it or provide edit access to the issue?

[tesseralis]

@jumpalottahigh accept the email invite to join the reactjs organization and it'll give you edit access.

[jumpalottahigh]

Thanks a ton @tesseralis !

[kdichev]

Hey, I would like to join and help out. I can start with Components and Props

[jumpalottahigh]

@kdichev That's awesome! Have at it!

[andrey-andreev]

Hi guys, I'll like to help with the translations too. Can I take the next page State and Lifecycle ?

[jumpalottahigh]

Great! All yours, @andrey-andreev :)

[andrey-andreev]

Thanks !

[kdichev]

I am taking Forms. Let me know if that's alright with you, guys.

[jumpalottahigh]

Just FIY, I've been and will be a bit less active in the next couple of weeks as I have too many things going on, prepping talks etc. But looking forward to contributing as soon as possible :)

[krasimir]

@jumpalottahigh no worries. Take care.

[ValGeorgiev]

Hi guys, joining to help. I will take Thinking in React once I am added to the organisation.

[jumpalottahigh]

Hi @ValGeorgiev and welcome! I have now reviewed and merged the PR adding you to the maintainers list. Should I add your name to the Thinking in React translation?

[ValGeorgiev]

Hi @jumpalottahigh, thanks for your approval. Yes, please add me to the Thinking in React, thank you. I don't have rights to edit this issue yet.

[deyan-a]

Hi guys,
I'd be more than happy to join the effort and contribute to translating the docs to Bulgarian. How can I join in? I can see that the basics have been covered, so I guess I can start with the beginning of API - Reference React

[jumpalottahigh]

@deyan-a Create a pull request in this repository, adding yourself in the list of the maintainers to this file - https://github.com/reactjs/reactjs.org-translation/blob/master/langs/bg.json

[ju-mihaylova]

Hi @tesseralis. I would like to help out with the translations. Can you please send me an invite to join the reactjs organization. Then I can take up React from the API Reference section. Thank you.

[deyan-a]

hi @ju-mihaylova , as suggested by @jumpalottahigh a post above:

Create a pull request in this repository, adding yourself in the list of the maintainers to this file - https://github.com/reactjs/reactjs.org-translation/blob/master/langs/bg.json

[ju-mihaylova]

Hi @deyan-a, thank you for your feedback, but I am already on the list of maintainers. Is this enough to start translating or do I need to join the reactjs organization?

[jumpalottahigh]

@ju-mihaylova You can start translating and open a pull request with your translation at any time, nothing is holding you back from this. But if you also want to be a part of the organization, you do have to follow the steps above and once you've been added to the organizations, I or any of the others can add you to the Bulgarian translation team.

[kirilchristov]

Hi guys, hello from Los Angeles. I would like to join and start helping with the translation. I may start with Hooks. Although I got a newbie question. Do we have any understanding of what kind of word we do not translate (terms like 'hooks' for example?) Do we have any internal guidelines? I tried to find some but maybe I missed it. Thank you all for translating React in Bulgarian btw. I can't wait to join.

[jumpalottahigh]

Hi @kirilchristov and thanks for the interest! To get started, create a PR in this repo by adding your name to the list: https://github.com/reactjs/reactjs.org-translation/blob/master/langs/bg.json

Regarding which words to leave off untranslated, we have a discussion and rough guidelines here:
#6
We try to be as consistent as possible. Feel free to add suggestions and extend the discussion.

[d3ltaf0rc3]

Hey, guys! I'd like to help with the translation. I'm going to take the Add React to a Website page in the Installation section.

[d3ltaf0rc3]

Hey, guys! I created a PR adding myself as a maintainer. Can you add me to the organization?

[gaearon]

It looks like this translation has stalled, and is now very outdated.
I'm going to archive this repo, but if someone wants to pick up, please start a new effort.