reactjs · deblasis · Mar 23, 2019 · Mar 22, 2019 · Mar 23, 2019 · Mar 23, 2019
diff --git a/GLOSSARY.md b/GLOSSARY.md
@@ -5,6 +5,8 @@ Glossary of the translations of technical and React-specific terms.
 ## Untranslatable terms
 - props (**core concept**)
 - state (**core concept**)
+- hooks (**core concept**)
+- ref (**core concept**)
 - footer
 - bug
 - browser
@@ -21,6 +23,10 @@ Glossary of the translations of technical and React-specific terms.
 - console
 - warning
 - form/forms
+- render props
+- strict mode
+- web components
+- build steps
 
 # Common Translations
 

diff --git a/content/blog/2015-12-18-react-components-elements-and-instances.md b/content/blog/2015-12-18-react-components-elements-and-instances.md
@@ -350,7 +350,7 @@ React will ask the `Form` component what element tree it returns, given those `p
 }
 ```
 
-This is a part of the process that React calls [reconciliation](/docs/reconciliation.html) which starts when you call [`ReactDOM.render()`](/docs/top-level-api.html#reactdom.render) or [`setState()`](/docs/component-api.html#setstate). By the end of the reconciliation, React knows the result DOM tree, and a renderer like `react-dom` or `react-native` applies the minimal set of changes necessary to update the DOM nodes (or the platform-specific views in case of React Native).
+This is a part of the process that React calls [riconciliazione](/docs/reconciliation.html) which starts when you call [`ReactDOM.render()`](/docs/top-level-api.html#reactdom.render) or [`setState()`](/docs/component-api.html#setstate). By the end of the reconciliation, React knows the result DOM tree, and a renderer like `react-dom` or `react-native` applies the minimal set of changes necessary to update the DOM nodes (or the platform-specific views in case of React Native).
 
 This gradual refining process is also the reason React apps are easy to optimize. If some parts of your component tree become too large for React to visit efficiently, you can tell it to [skip this “refining” and diffing certain parts of the tree if the relevant props have not changed](/docs/advanced-performance.html). It is very fast to calculate whether the props have changed if they are immutable, so React and immutability work great together, and can provide great optimizations with the minimal effort.
 

diff --git a/content/blog/2017-09-08-dom-attributes-in-react-16.md b/content/blog/2017-09-08-dom-attributes-in-react-16.md
@@ -80,7 +80,7 @@ Just like before, React lets you pass `data-` and `aria-` attributes freely:
 
 This has not changed.
 
-[Accessibility](/docs/accessibility.html) is very important, so even though React 16 passes any attributes through, it still validates that `aria-` props have correct names in development mode, just like React 15 did.
+[Accessibilità](/docs/accessibility.html) is very important, so even though React 16 passes any attributes through, it still validates that `aria-` props have correct names in development mode, just like React 15 did.
 
 ## Migration Path {#migration-path}
 

diff --git a/content/docs/accessibility.md b/content/docs/accessibility.md
@@ -1,6 +1,6 @@
 ---
 id: accessibility
-title: Accessibility
+title: Accessibilità
 permalink: docs/accessibility.html
 ---
 

diff --git a/content/docs/add-react-to-a-website.md b/content/docs/add-react-to-a-website.md
@@ -1,6 +1,6 @@
 ---
 id: add-react-to-a-website
-title: Add React to a Website
+title: Aggiungere React Ad Un Sito
 permalink: docs/add-react-to-a-website.html
 redirect_from:
   - "docs/add-react-to-an-existing-app.html"

diff --git a/content/docs/addons-animation.md b/content/docs/addons-animation.md
@@ -173,7 +173,7 @@ It is also possible to use custom class names for each of the steps in your tran
 
 In order for it to apply transitions to its children, the `ReactCSSTransitionGroup` must already be mounted in the DOM or the prop `transitionAppear` must be set to `true`.
 
-The example below would **not** work, because the `ReactCSSTransitionGroup` is being mounted along with the new item, instead of the new item being mounted within it. Compare this to the [Getting Started](#getting-started) section above to see the difference.
+The example below would **not** work, because the `ReactCSSTransitionGroup` is being mounted along with the new item, instead of the new item being mounted within it. Compare this to the [Primi Passi](#getting-started) section above to see the difference.
 
 ```javascript{4,6,13}
 render() {

diff --git a/content/docs/cdn-links.md b/content/docs/cdn-links.md
@@ -1,6 +1,6 @@
 ---
 id: cdn-links
-title: CDN Links
+title: Collegamenti a CDN
 permalink: docs/cdn-links.html
 prev: create-a-new-react-app.html
 next: hello-world.html

diff --git a/content/docs/codebase-overview.md b/content/docs/codebase-overview.md
@@ -1,6 +1,6 @@
 ---
 id: codebase-overview
-title: Codebase Overview
+title: Panoramica sul Codice
 layout: contributing
 permalink: docs/codebase-overview.html
 prev: how-to-contribute.html
@@ -165,7 +165,7 @@ The "core" of React includes all the [top-level `React` APIs](/docs/top-level-ap
 * `React.Component`
 * `React.Children`
 
-**React core only includes the APIs necessary to define components.** It does not include the [reconciliation](/docs/reconciliation.html) algorithm or any platform-specific code. It is used both by React DOM and React Native components.
+**React core only includes the APIs necessary to define components.** It does not include the [riconciliazione](/docs/reconciliation.html) algorithm or any platform-specific code. It is used both by React DOM and React Native components.
 
 The code for React core is located in [`packages/react`](https://github.com/facebook/react/tree/master/packages/react) in the source tree. It is available on npm as the [`react`](https://www.npmjs.com/package/react) package. The corresponding standalone browser build is called `react.js`, and it exports a global called `React`.
 
@@ -189,7 +189,7 @@ The only other officially supported renderer is [`react-art`](https://github.com
 
 ### Reconcilers {#reconcilers}
 
-Even vastly different renderers like React DOM and React Native need to share a lot of logic. In particular, the [reconciliation](/docs/reconciliation.html) algorithm should be as similar as possible so that declarative rendering, custom components, state, lifecycle methods, and refs work consistently across platforms.
+Even vastly different renderers like React DOM and React Native need to share a lot of logic. In particular, the [riconciliazione](/docs/reconciliation.html) algorithm should be as similar as possible so that declarative rendering, custom components, state, lifecycle methods, and refs work consistently across platforms.
 
 To solve this, different renderers share some code between them. We call this part of React a "reconciler". When an update such as `setState()` is scheduled, the reconciler calls `render()` on components in the tree and mounts, updates, or unmounts them.
 

diff --git a/content/docs/create-a-new-react-app.md b/content/docs/create-a-new-react-app.md
@@ -1,6 +1,6 @@
 ---
 id: create-a-new-react-app
-title: Create a New React App
+title: Creare una Nuova App React
 permalink: docs/create-a-new-react-app.html
 redirect_from:
   - "docs/add-react-to-a-new-app.html"

diff --git a/content/docs/design-principles.md b/content/docs/design-principles.md
@@ -1,6 +1,6 @@
 ---
 id: design-principles
-title: Design Principles
+title: Principi di Design
 layout: contributing
 permalink: docs/design-principles.html
 prev: implementation-notes.html

diff --git a/content/docs/faq-ajax.md b/content/docs/faq-ajax.md
@@ -1,6 +1,6 @@
 ---
 id: faq-ajax
-title: AJAX and APIs
+title: AJAX ed APIs
 permalink: docs/faq-ajax.html
 layout: docs
 category: FAQ

diff --git a/content/docs/faq-functions.md b/content/docs/faq-functions.md
@@ -1,6 +1,6 @@
 ---
 id: faq-functions
-title: Passing Functions to Components
+title: Passare Funzioni ai Componenti
 permalink: docs/faq-functions.html
 layout: docs
 category: FAQ

diff --git a/content/docs/faq-internals.md b/content/docs/faq-internals.md
@@ -1,14 +1,14 @@
 ---
 id: faq-internals
-title: Virtual DOM and Internals
+title: Virtual DOM ed Interni
 permalink: docs/faq-internals.html
 layout: docs
 category: FAQ
 ---
 
 ### What is the Virtual DOM? {#what-is-the-virtual-dom}
 
-The virtual DOM (VDOM) is a programming concept where an ideal, or "virtual", representation of a UI is kept in memory and synced with the "real" DOM by a library such as ReactDOM. This process is called [reconciliation](/docs/reconciliation.html).
+The virtual DOM (VDOM) is a programming concept where an ideal, or "virtual", representation of a UI is kept in memory and synced with the "real" DOM by a library such as ReactDOM. This process is called [riconciliazione](/docs/reconciliation.html).
 
 This approach enables the declarative API of React: You tell React what state you want the UI to be in, and it makes sure the DOM matches that state. This abstracts out the attribute manipulation, event handling, and manual DOM updating that you would otherwise have to use to build your app.
 

diff --git a/content/docs/faq-state.md b/content/docs/faq-state.md
@@ -1,6 +1,6 @@
 ---
 id: faq-state
-title: Component State
+title: State dei Componenti
 permalink: docs/faq-state.html
 layout: docs
 category: FAQ

diff --git a/content/docs/faq-structure.md b/content/docs/faq-structure.md
@@ -1,6 +1,6 @@
 ---
 id: faq-structure
-title: File Structure
+title: Struttura dei File
 permalink: docs/faq-structure.html
 layout: docs
 category: FAQ

diff --git a/content/docs/faq-styling.md b/content/docs/faq-styling.md
@@ -1,6 +1,6 @@
 ---
 id: faq-styling
-title: Styling and CSS
+title: Stili e CSS
 permalink: docs/faq-styling.html
 layout: docs
 category: FAQ

diff --git a/content/docs/faq-versioning.md b/content/docs/faq-versioning.md
@@ -1,6 +1,6 @@
 ---
 id: faq-versioning
-title: Versioning Policy
+title: Regole di Versionamento
 permalink: docs/faq-versioning.html
 layout: docs
 category: FAQ

diff --git a/content/docs/forwarding-refs.md b/content/docs/forwarding-refs.md
@@ -1,6 +1,6 @@
 ---
 id: forwarding-refs
-title: Forwarding Refs
+title: Inoltrare Refs
 permalink: docs/forwarding-refs.html
 ---
 

diff --git a/content/docs/fragments.md b/content/docs/fragments.md
@@ -1,6 +1,6 @@
 ---
 id: fragments
-title: Fragments
+title: Frammenti
 permalink: docs/fragments.html
 ---
 

diff --git a/content/docs/getting-started.md b/content/docs/getting-started.md
@@ -1,6 +1,6 @@
 ---
 id: getting-started
-title: Getting Started
+title: Primi Passi
 permalink: docs/getting-started.html
 next: add-react-to-a-website.html
 redirect_from:

diff --git a/content/docs/higher-order-components.md b/content/docs/higher-order-components.md
@@ -1,6 +1,6 @@
 ---
 id: higher-order-components
-title: Higher-Order Components
+title: Componenti di Ordine Superiore
 permalink: docs/higher-order-components.html
 ---
 
@@ -320,7 +320,7 @@ Higher-order components come with a few caveats that aren't immediately obvious
 
 ### Don't Use HOCs Inside the render Method {#dont-use-hocs-inside-the-render-method}
 
-React's diffing algorithm (called reconciliation) uses component identity to determine whether it should update the existing subtree or throw it away and mount a new one. If the component returned from `render` is identical (`===`) to the component from the previous render, React recursively updates the subtree by diffing it with the new one. If they're not equal, the previous subtree is unmounted completely.
+React's diffing algorithm (called riconciliazione) uses component identity to determine whether it should update the existing subtree or throw it away and mount a new one. If the component returned from `render` is identical (`===`) to the component from the previous render, React recursively updates the subtree by diffing it with the new one. If they're not equal, the previous subtree is unmounted completely.
 
 Normally, you shouldn't need to think about this. But it matters for HOCs because it means you can't apply a HOC to a component within the render method of a component:
 

diff --git a/content/docs/hooks-custom.md b/content/docs/hooks-custom.md
@@ -1,6 +1,6 @@
 ---
 id: hooks-custom
-title: Building Your Own Hooks
+title: Hooks Personalizzati
 permalink: docs/hooks-custom.html
 next: hooks-reference.html
 prev: hooks-rules.html

diff --git a/content/docs/hooks-effect.md b/content/docs/hooks-effect.md
@@ -1,6 +1,6 @@
 ---
 id: hooks-state
-title: Using the Effect Hook
+title: Usare l'Hook Effect
 permalink: docs/hooks-effect.html
 next: hooks-rules.html
 prev: hooks-state.html
-Original file line number
+Diff line change
@@ Expand Up @@
     }
     ```
-    This is a part of the process that React calls [reconciliation](/docs/reconciliation.html) which starts when you call [`ReactDOM.render()`](/docs/top-level-api.html#reactdom.render) or [`setState()`](/docs/component-api.html#setstate). By the end of the reconciliation, React knows the result DOM tree, and a renderer like `react-dom` or `react-native` applies the minimal set of changes necessary to update the DOM nodes (or the platform-specific views in case of React Native).
+    This is a part of the process that React calls [riconciliazione](/docs/reconciliation.html) which starts when you call [`ReactDOM.render()`](/docs/top-level-api.html#reactdom.render) or [`setState()`](/docs/component-api.html#setstate). By the end of the reconciliation, React knows the result DOM tree, and a renderer like `react-dom` or `react-native` applies the minimal set of changes necessary to update the DOM nodes (or the platform-specific views in case of React Native).
     This gradual refining process is also the reason React apps are easy to optimize. If some parts of your component tree become too large for React to visit efficiently, you can tell it to [skip this “refining” and diffing certain parts of the tree if the relevant props have not changed](/docs/advanced-performance.html). It is very fast to calculate whether the props have changed if they are immutable, so React and immutability work great together, and can provide great optimizations with the minimal effort.
@@ Expand Down @@