Deploy website

Deploy website version based on 42286ded959034d779f737fc6bd0358826d3b72d

docs/assets/HermesLogo.svg

@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="492.75" height="377.55" viewBox="0 0 492.75 377.55"><defs><style>.a,.b,.c{fill:#2bb673;stroke:#3d3d3d;stroke-linecap:round;stroke-linejoin:round;stroke-width:15px;fill-rule:evenodd;}.a{fill-opacity:0.2;}.b{fill-opacity:0.6;}</style></defs><title>Hermes Full Color Logo</title><path class="a" d="M247.21,353.68l4.7-20.53c2-8.54,3.79-25.32,4.85-33.12-11.36-4.63-26.7-2-46.61-4.25a80.64,80.64,0,0,1-41.3-17.59l0,2.84A81.36,81.36,0,0,0,240.55,353Z" transform="translate(-100.62 -161.23)"/><path class="b" d="M179.85,240.67a81,81,0,0,1-41.52-17.21l0,.07A81.38,81.38,0,0,0,210,295.47l48.79,3.66C261.17,269.38,247.37,248.26,179.85,240.67Z" transform="translate(-100.62 -161.23)"/><path class="c" d="M563.07,168.85H512.35a30.56,30.56,0,0,0-29.92,24.31l-19.69,96.09a13.92,13.92,0,0,1-13.59,11.11l-76.35.22a13.9,13.9,0,0,1-13.66-16.74h0c12.39-59.36-31.35-115.11-115.81-115.11H108.12a81.4,81.4,0,0,0,71.73,71.94c89.19,10,82.24,46.07,72.06,90.48L212.46,503.39a22.79,22.79,0,0,0,22.22,27.88h47.95A30.55,30.55,0,0,0,312.54,507l20.72-98.62a13.91,13.91,0,0,1,13.57-11l76.83-.22a13.91,13.91,0,0,1,13.66,16.72l-18.4,89.1a22.8,22.8,0,0,0,22.22,27.89h50.73a30.57,30.57,0,0,0,29.91-24.32l63.51-309.73A22.79,22.79,0,0,0,563.07,168.85Z" transform="translate(-100.62 -161.23)"/></svg>

docs/communication-android.html

@@ -67,7 +67,7 @@ mReactRootView<span class="token punctuation">.</span><span class="token functio
 <p>It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.</p>
 <p>There is no way to update only a few properties at a time. We suggest that you build it into your own wrapper instead.</p>
 <blockquote>
-<p><strong><em>Note:</em></strong> Currently, JS functions <code>componentWillReceiveProps</code> and <code>componentWillUpdateProps</code> of the top level RN component will not be called after a prop update. However, you can access the new props in <code>componentWillMount</code> function.</p>
+<p><strong><em>Note:</em></strong> Currently, JS function <code>componentWillUpdateProps</code> of the top level RN component will not be called after a prop update. However, you can access the new props in <code>componentDidMount</code> function.</p>
 </blockquote>
 <h3><a class="anchor" aria-hidden="true" id="passing-properties-from-react-native-to-native"></a><a href="#passing-properties-from-react-native-to-native" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Passing properties from React Native to native</h3>
 <p>The problem exposing properties of native components is covered in detail in <a href="/react-native/docs/native-components-android#3-expose-view-property-setters-using-reactprop-or-reactpropgroup-annotation">this article</a>. In short, properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with <code>@ReactProp</code>, then just use them in React Native as if the component was an ordinary React Native component.</p>

docs/communication-android/index.html

@@ -67,7 +67,7 @@ mReactRootView<span class="token punctuation">.</span><span class="token functio
 <p>It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.</p>
 <p>There is no way to update only a few properties at a time. We suggest that you build it into your own wrapper instead.</p>
 <blockquote>
-<p><strong><em>Note:</em></strong> Currently, JS functions <code>componentWillReceiveProps</code> and <code>componentWillUpdateProps</code> of the top level RN component will not be called after a prop update. However, you can access the new props in <code>componentWillMount</code> function.</p>
+<p><strong><em>Note:</em></strong> Currently, JS function <code>componentWillUpdateProps</code> of the top level RN component will not be called after a prop update. However, you can access the new props in <code>componentDidMount</code> function.</p>
 </blockquote>
 <h3><a class="anchor" aria-hidden="true" id="passing-properties-from-react-native-to-native"></a><a href="#passing-properties-from-react-native-to-native" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Passing properties from React Native to native</h3>
 <p>The problem exposing properties of native components is covered in detail in <a href="/react-native/docs/native-components-android#3-expose-view-property-setters-using-reactprop-or-reactpropgroup-annotation">this article</a>. In short, properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with <code>@ReactProp</code>, then just use them in React Native as if the component was an ordinary React Native component.</p>