reactjs / reactjs/it.react.dev

New Italian Translation Progress

Open
#418 53 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
37
Forks
82
Avg merge
4h 21m
Merged PRs (30d)
82

Description

Maintainer List

  • @deblasis
  • @mattia-sanfilippo

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:

  • Quick Start (@tesseralis) #12345

When human translation PRs are merged, mark the page as completed: [x] (@translator) #NNN.

For AI-assisted translations (translationStatus: ai-draft), keep [x] Titolo πŸ€– (AI draft) #NNN even after merge β€” maintainer supervision is not a community editorial pass. Change to [x] (@reviewer) #NNN only after a full community revision (and remove translationStatus + <Note> from the page). See STYLE_GUIDE.md β€” Traduzioni assistite (AI).

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 (@mattia-sanfilippo) #423

    • Tutorial: Tic Tac Toe (@mattia-sanfilippo) #437
    • Thinking in React (@SamuelePiazzesi) #421
  • Installation (@Th3Wall) #422

  • Describing the UI (@Ago95Dev) #427

    • Your First Component (@eliamaino-fp) #420
    • Importing and Exporting Components (@eliamaino-fp) #444
    • Writing Markup with JSX (@Ago95Dev) #424
    • JavaScript in JSX with Curly Braces (@SamuelePiazzesi) #426
    • Passing Props to a Component (@Th3Wall) #428
    • Conditional Rendering (@Th3Wall) #431
    • Rendering Lists (@SamuelePiazzesi) #442
    • Keeping Components Pure (@Ago95Dev) #430
  • Adding Interactivity (@oxcened) #434

    • Responding to Events (@Th3Wall) #438
    • State: A Component's Memory (@oxcened) #439
    • Render and Commit (@Ago95Dev) #446
    • State as a Snapshot (@NeilChavez) #440
    • Queueing a Series of State Updates πŸ€– (AI draft) #625
    • Updating Objects in State (@oxcened) #443
    • Updating Arrays in State (@paolapog) #448
  • Managing State (@webdiego) #450

    • Reacting to Input with State πŸ€– (AI draft) #626
    • Choosing the State Structure (@giuseppe-osenda) #557
    • Condividere lo State tra i Componenti πŸ€– (AI draft) #734
    • Preservare e Reimpostare lo State πŸ€– (AI draft) #735
    • Extracting State Logic into a Reducer (@paolapog) #480
    • Passing Data Deeply with Context (@oxcened) #470
    • Scaling Up with Reducer and Context (@lorenzoceglia) #594
  • Escape Hatches

    • Escape Hatches (index) πŸ€– (AI draft) #709
    • Referencing Values with Refs πŸ€– (AI draft) #628
    • Manipulating the DOM with Refs πŸ€– (AI draft) #629
    • Synchronizing with Effects πŸ€– (AI draft) #630
    • You Might Not Need an Effect (@mattveraldi) #502
    • Lifecycle of Reactive Effects πŸ€– (AI draft) #631
    • Separating Events from Effects πŸ€– (AI draft) #632
    • Removing Effect Dependencies πŸ€– (AI draft) #633
    • Reusing Logic with Custom Hooks πŸ€– (AI draft) #634
API Reference
  • react: Hooks (@fmineo) #455

    • useCallback πŸ€– (AI draft) #638
    • useContext πŸ€– (AI draft) #639
    • useDebugValue πŸ€– (AI draft) #641
    • useDeferredValue πŸ€– (AI draft) #642
    • useEffect πŸ€– (AI draft) #643
    • useId πŸ€– (AI draft) #644
    • useImperativeHandle πŸ€– (AI draft) #645
    • useInsertionEffect πŸ€– (AI draft) #646
    • useLayoutEffect πŸ€– (AI draft) #647
    • useMemo πŸ€– (AI draft) #648
    • useReducer πŸ€– (AI draft) #649
    • useRef πŸ€– (AI draft) #650
    • useState πŸ€– (AI draft) #651
    • useSyncExternalStore πŸ€– (AI draft) #652
    • useTransition πŸ€– (AI draft) #653
  • react: Components

    • <Fragment> (<>) πŸ€– (AI draft) #654
    • <Profiler> πŸ€– (AI draft) #687
    • <StrictMode> πŸ€– (AI draft) #688
    • <Suspense> πŸ€– (AI draft) #690
  • react: APIs

    • createContext πŸ€– (AI draft) #691
    • forwardRef πŸ€– (AI draft) #693
    • lazy πŸ€– (AI draft) #694
    • memo πŸ€– (AI draft) #692
    • startTransition πŸ€– (AI draft) #695
  • React DOM APIs (index) πŸ€– (AI draft) #723

  • react-dom: Components

    • Common (e.g. <div>) πŸ€– (AI draft) #696
    • <input> πŸ€– (AI draft) #697
    • <option> πŸ€– (AI draft) #698
    • <progress> πŸ€– (AI draft) #699
    • <select> πŸ€– (AI draft) #700
    • <textarea> πŸ€– (AI draft) #701
  • react-dom: APIs

    • createPortal πŸ€– (AI draft) #702
    • flushSync πŸ€– (AI draft) #703
    • findDOMNode (no page in react.dev; linked from React DOM index only)
    • hydrate (no page in react.dev; linked from React DOM index only)
    • render (no page in react.dev; linked from React DOM index only)
    • unmountComponentAtNode (no page in react.dev; linked from React DOM index only)
  • react-dom/client: Client APIs

    • createRoot πŸ€– (AI draft) #704
    • hydrateRoot πŸ€– (AI draft) #705
  • react-dom/server: Server APIs

    • React DOM Server APIs (index) πŸ€– (AI draft) #724
    • renderToNodeStream (deprecated; no page file; linked from server index only)
    • renderToPipeableStream πŸ€– (AI draft) #689
    • renderToReadableStream πŸ€– (AI draft) #706
    • renderToStaticMarkup πŸ€– (AI draft) #707
    • renderToStaticNodeStream (deprecated; no page file; linked from server index only)
    • renderToString πŸ€– (AI draft) #708
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) (@deblasis) #417
  • Sidebars πŸ€– (AI draft) #719
  • Top-level navigation πŸ€– (AI draft) #717
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
    • Legacy React APIs (index) πŸ€– (AI draft) #725
    • Children πŸ€– (AI draft) #710
    • cloneElement πŸ€– (AI draft) #711
    • Component πŸ€– (AI draft) #712
    • createElement πŸ€– (AI draft) #713
    • createFactory (deprecated; no page file; linked from legacy index only)
    • createRef πŸ€– (AI draft) #714
    • isValidElement πŸ€– (AI draft) #715
    • PureComponent πŸ€– (AI draft) #716

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 πŸ€– (AI draft) #720, #721, #722
  • Blog πŸ€– (AI draft) #728, #729, #731, #730, #732, #727
  • Warnings πŸ€– (AI draft) #718

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up β€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the checklist in this issue and STYLE_GUIDE.md; they describe the translation workflow and AI-draft review rules. All listed pages are already marked complete, so there is no specific unclaimed page or file to change. If continuing project work, verify the language-release step in Seo.tsx.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
documentation, internationalization, localization
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.