reactjs / reactjs/tr.react.dev

New Turkish Translation Progress

Aberta
#397 146 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Linguagem predominante
JavaScript
Estrelas
172
Forks
172
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

Çeviri Yapmadan Önce Lütfen Aşağıdaki Kuralları Okuyunuz

Çeviri yapma süreci üç adımda gerçekleştirilir:

  1. Kontrol listesinde kimsenin işaretlemediği bölümleri seçiniz. Altındaki yorumları kontrol ederek emin olunuz. İpucu: CTRL+F ile istediğiniz bölümle ilgili arama yaparak kontrol edebilirsiniz.

  2. Hangi sayfayı çevireceğinizi yorum kısmına yazınız. Lütfen bir seferde birden fazla sayfa almayınız!

  3. Projeyi yerel makinenize clone'layınız. Sayfayı çevirdiğinizde commit ederek, pull request gönderiniz.

  4. Commit mesajlarini ingilizce yaziniz.

  5. Commit mesajlarinda gecmis zaman formu kullanmayiniz. translated tutorial page yerine translate tutorial page. ya da fixed a typo in docs yerine fix a typo in docs.

Tercüme etmeden önce, çeviri kurallarını mutlaka okuyunuz.

İlgili tartışmalara dahil olmak için Slack #tr kanalına katılın.

💡 Repoda Discussions kismi enable edildi. Soru-cevap ya da fikir alisverisi gibi konular icin orayi kullanabiliriz.

Maintainer List

  • @bilalkarakollu
  • @anilcanboga

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:

[x] Home Page (@tesseralis) #12345

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

Main Content

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

Note that each section has an index page, which needs to be translated too.

Learn React
  • Quick Start (@serkanisyapan) #528

    • Tutorial: Tic Tac Toe (@serkanisyapan) 94ce329
    • Thinking in React (@alioguzhan) #503
  • Installation (@yunusemredilber) 373161ed

    • Start a New React Project (@bbolek) #401
    • Add React to an Existing Project (@MizginYildirak) #443
    • Editor Setup (@kuntik17) #405
    • Using Typescript (@halilxibrahim) #566
    • React Developer Tools (@kuntik17) #402
    • React Compiler (@anilcanboga) #604
  • Describing the UI (@TolgaYuceel) #530

    • Your First Component (@serkanisyapan) #509
    • Importing and Exporting Components (@akcoren) #403
    • Writing Markup with JSX (@mervekrblt) #426
    • JavaScript in JSX with Curly Braces (@Cansualtun) #444
    • Passing Props to a Component (@buraksakalli) #416
    • Conditional Rendering (@serkanisyapan) #421
    • Rendering Lists (@serkanisyapan) #410
    • Keeping Components Pure (@MizginYildirak) #418
    • Understanding Your UI as a Tree (@TolgaYuceel ) #532
  • Adding Interactivity (@serkanisyapan) #511

    • Responding to Events (@baspinarenes) #413
    • State: A Component's Memory (@agmmnn) #425
    • Render and Commit (@serkanisyapan) #434
    • State as a Snapshot (@emrecanberktas) #468
    • Queueing a Series of State Updates (@serkanisyapan) #447
    • Updating Objects in State (@enesakkose) #445
    • Updating Arrays in State (@serkanisyapan) #460
  • Managing State (@serkanisyapan) 5ba09bc

    • Reacting to Input with State (@itsba2) #406
    • Choosing the State Structure (@seckinoter) #457
    • Sharing State Between Components (@cydexx) (@alioguzhan) #438
    • Preserving and Resetting State (@serkanisyapan) #463
    • Extracting State Logic into a Reducer (@agmmnn) #446
    • Passing Data Deeply with Context (@Rogultum) #472
    • Scaling Up with Reducer and Context (@TolgaYuceel) #527
  • Escape Hatches (@serkanisyapan) #578

    • Referencing Values with Refs (@furkanmavili) #455
    • Manipulating the DOM with Refs (@dilarauluturhan) #485
    • Synchronizing with Effects (@serkanisyapan) #505
    • You Might Not Need an Effect (@enesakkose) #469
    • Lifecycle of Reactive Effects (@burakcihan61) #490 #491
    • Separating Events from Effects (@burakcihan61) #493
    • Removing Effect Dependencies (@TolgaYuceel) #552
    • Reusing Logic with Custom Hooks (@anilcanboga) #590
API Reference
  • react: Hooks (@alioguzhan) #504

    • useCallback (@baspinarenes) #470
    • useContext (@osmandlsmn) #423
    • useDebugValue (@buraksakalli) #454
    • useDeferredValue (@baspinarenes) #462
    • useEffect (@serkanisyapan) #471
    • useId (@baspinarenes) #415
    • useImperativeHandle (@buraksakalli) #456
    • useInsertionEffect (@enesakkose) #459
    • useLayoutEffect (@baspinarenes) #420
    • useMemo (@iefendiev) #451
    • useReducer (@buraksakalli) #428
    • useRef (@coskuncakir) #407
    • useState (@serkanisyapan) #508
    • useSyncExternalStore (@baspinarenes) #452
    • useTransition (@halilatilla) #450
  • react: Components (@TarcosS) #548

    • <Fragment> (<>) (@K2adir) #419
    • <Profiler> (@agmmnn) #431
    • <StrictMode> (@hasancankucuk) #482
    • <Suspense> (@andyanday33) #440
  • react: APIs (@baspinarenes) #453

    • createContext (@halilatilla) #409
    • forwardRef (@halilatilla) #427
    • lazy (@baspinarenes) #422
    • memo (@baspinarenes) #436
    • startTransition (@halilatilla) #442
    • legacy (@bilalkarakollu ) #603
  • react-dom: Components (@agmmnn) #430

    • Common (e.g. <div>) (@itsba2) #519
    • <input> (@hasancankucuk) #481
    • <option> (@K2adir) #435
    • <progress> (@agmmnn) #429
    • <select> (@serkanisyapan) #466
    • <textarea> (@hasancankucuk) #479
  • react-dom: APIs (@agmmnn) #431

    • createPortal (@arif-ozberk) #483
    • flushSync (@K2adir) #448
    • findDOMNode (@enesthedev) #496
    • hydrate (@ctnkaan) #555
    • render (@buraksakalli) #465
    • unmountComponentAtNode (@ctnkaan) #536
  • react-dom/client: Client APIs (@altankurt) #424

    • createRoot (@alpererdogan8) #523
    • hydrateRoot (@bilalkarakollu)
  • react-dom/server: Server APIs (@andyanday33) #439

    • renderToNodeStream (@Rekl0w) #545
    • renderToPipeableStream (@hasancankucuk) #487
    • renderToReadableStream (@anilcanboga) #693
    • renderToStaticMarkup (@Rekl0w) #544
    • renderToStaticNodeStream (@arif-ozberk) #473
    • renderToString (@arif-ozberk) #480
    • resume (@anilcanboga )
    • resumeToPipeableStream (@anilcanboga )
  • React Server Components: Server Components (@bilalkarakollu) #589

    • Server Functions (@anilcanboga )
    • Directives (@anilcanboga)
    • use client (@anilcanboga)
    • use server (@anilcanboga)
Navigation and UI

We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.

  • Homepage (currently in HomeContent.js) (@turkerdev) #404
  • Sidebars (currently in src/sidebar*.json) (@alioguzhan) dd0d22df0117b23615e86fa8cb04e8b5749f4e4a
  • Top-level navigation (currently in TopNav.tsx) (@alioguzhan) #504
When You're Ready...

After everything above is translated, add your language to deployedLanguages in Seo.tsx of the original reactjs/react.dev repository.

Secondary Content

These API pages should ideally be translated too, but they're less urgent and can be done after the others:

  • Legacy React APIs (@bilalkarakollu) #603
    • Children (@anilcanboga) #696
    • cloneElement (@anilcanboga) #695
    • Component (@mvtandas) #707
    • createElement (@anilcanboga)
    • createFactory
    • createRef (@anilcanboga)
    • isValidElement (@mvtandas) #705
    • PureComponent (@mvtandas) #706

Optional Content

These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:

  • Community (@coderdal) #477

  • Blog (@anilcanboga) #597

  • Special Props Warning #605

  • Not Found (@anilcanboga) #595

  • Feedback component (@anilcanboga) #596

  • React Reference Overview (@anilcanboga) #593

  • React Rules

    • Overview (@anilcanboga) #624
    • Rules of Hooks (@anilcanboga) #626

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Direção de pesquisa

Comece lendo as regras da TRANSLATION.md vinculada e, em seguida, verifique a checklist da issue e os comentários antes de assumir a página restante de createFactory. Traduza essa página para turco, envie um pull request com uma mensagem de commit em inglês no imperativo e atualize a checklist quando ela estiver concluída.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
react
Domínio
documentation
Tipo de issue
Documentação
Dificuldade
2/5
Tempo estimado
1-3 horas
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.