Use localization strings in networking page

locales/en-US/networking.ftl

@@ -0,0 +1,72 @@
+## templates/what/networking.hbs
+
+networking-header = Networking
+
+## templates/components/what/networking/get-started.hbs
+
+networking-get-started-header = Get started!
+networking-get-started = Rust has a growing ecosystem of easy-to-use libraries for the web. Here are just two examples:
+networking-get-started-post-json = POST some JSON
+networking-get-started-take-json = Handle a JSON POST
+networking-get-started-reqwest = Learn more about reqwest
+networking-get-started-rocket = Learn more about Rocket
+
+## templates/components/what/networking/pitch.hbs
+
+networking-pitch-why = Why Rust?
+networking-pitch-footprint-header = Low footprint
+networking-pitch-footprint =
+    Take control over resource usage to keep memory and CPU footprint to a minimum.
+    Get help from the compiler to make sure you’ve got it right.
+    And do this with an ecosystem that is productive and pleasant to use.
+networking-pitch-footprint-alt = A feather
+
+
+networking-pitch-secure-header = Secure and reliable
+networking-pitch-secure =
+    Rust’s powerful type checker prevents whole classes of bugs.
+    Make sure you know exactly when and where state is shared and mutated.
+    Get help catching points of failure — before deployment.
+networking-pitch-secure-alt = A shield
+
+
+networking-pitch-concurrent-header = Concurrent at scale
+networking-pitch-concurrent =
+    Use any mixture of concurrency approaches that works for you.
+    Rust will make sure you don’t accidentally share state between threads or tasks.
+    It empowers you to squeeze every last bit of scaling, fearlessly.
+networking-pitch-concurrent-alt = Connected gears
+
+
+## templates/components/what/networking/production.hbs
+
+networking-production = Production use
+
+networking-production-testimonial-mozilla =
+    Migrating our Push connection infrastructure to Rust has provided us with an easier to maintain
+    code-base with a focus on correctness while delivering fantastic performance. We are now
+    handling up to 20 million websocket connections at once during peak hours with Rust servers.
+networking-production-testimonial-mozilla-attribution = Benjamin Bangert, Staff Engineer, Mozilla
+
+networking-production-testimonial-buoyant =
+    Rust is foundational to the Linkerd project’s technology roadmap. Its type system allows us to
+    build modular, testable, composable units without sacrificing runtime performance. What’s been
+    most surprising, though, is how Rust’s lifetime/borrow checking system allows us to avoid large
+    classes of resource leaks. After 2 years, I really can’t imagine using any other language for
+    the job.
+networking-production-testimonial-buoyant-attribution = Oliver Gould, CTO, <a href="https://buoyant.io/">Buoyant</a>
+
+networking-production-testimonial-1aim =
+    Rust's powerful type system enables safe refactoring and catches many classes of bugs at
+    compile time. Its low footprint and high performance, complemented by guaranteed memory safety
+    and rock-solid error handling make it perfect for writing security critical and complex
+    business logic for our backend. The ultra-high stability means that our Rust applications are
+    the last part of our stack we ever have to worry about. We have been running a almost 100% Rust
+    backend in production since end of 2015 and it has never failed us so far!
+
+networking-production-testimonial-1aim-attribution = Yann Leretaille, <a href="https://1aim.com/">1aim</a>
+
+
+
+
+

templates/components/what/networking/get-started.hbs

@@ -1,28 +1,28 @@
 <section id="networking-get-started" class="red">
     <div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
         <header>
-            <h2>Get started!</h2>
+            <h2>{{text networking-get-started-header}}</h2>
             <div class="highlight"></div>
         </header>
 
         <div>
-            <p>Rust has a growing ecosystem of easy-to-use libraries for the web. Here are just two examples:
+            <p>{{text networking-get-started}}
             </p>
         </div>
 
         <div class="flex-l">
             <article class="w-50-l mr4-l">
-                <h3>POST some JSON</h3>
+                <h3>{{text networking-get-started-post-json}}</h3>
                 <pre><code>{{> components/what/networking/post-json }}</code></pre>
 
-                <a href="https://docs.rs/reqwest/" class="button button-secondary">Learn more about reqwest</a>
+                <a href="https://docs.rs/reqwest/" class="button button-secondary">{{text networking-get-started-reqwest}}</a>
             </article>
 
             <article class="w-50-l ml4-l mt5 mt0-l">
-                <h3>Handle a JSON POST</h3>
+                <h3>{{text networking-get-started-take-json}}</h3>
                 <pre><code>{{> components/what/networking/take-json }}</code></pre>
 
-                <a href="https://rocket.rs/" class="button button-secondary">Learn more about Rocket</a>
+                <a href="https://rocket.rs/" class="button button-secondary">{{text networking-get-started-rocket}}</a>
             </article>
         </div>
     </div>

templates/components/what/networking/pitch.hbs

@@ -1,41 +1,35 @@
 <section id="wasm-why" class="purple">
     <div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
         <header>
-            <h2>Why Rust?</h2>
+            <h2>{{text networking-pitch-why}}</h2>
             <div class="highlight"></div>
         </header>
         <div class="flex-l">
             <div class="w-33-l ph5 ph0-l">
                 <div class="domain-icon">
-                    <img src="/static/images/feather.svg" alt="A feather" />
-                    <h3>Low footprint</h3>
+                    <img src="/static/images/feather.svg" alt="{{text networking-pitch-footprint-alt}}" />
+                    <h3>{{text networking-pitch-footprint-header}}</h3>
                 </div>
                 <p>
-                    Take control over resource usage to keep memory and CPU footprint to a minimum.
-                    Get help from the compiler to make sure you’ve got it right.
-                    And do this with an ecosystem that is productive and pleasant to use.
+                    {{text networking-pitch-footprint}}
                 </p>
             </div>
             <div class="w-33-l ml5-l ph5 ph0-l mt5 mt0-l">
                 <div class="domain-icon">
-                    <img src="/static/images/secure-shield.svg" alt="A shield" />
-                    <h3>Secure and reliable</h3>
+                    <img src="/static/images/secure-shield.svg" alt="{{text networking-pitch-secure-alt}}" />
+                    <h3>{{text networking-pitch-secure-header}}</h3>
                 </div>
                 <p>
-                    Rust’s powerful type checker prevents whole classes of bugs.
-                    Make sure you know exactly when and where state is shared and mutated.
-                    Get help catching points of failure &mdash; before deployment.
+                    {{text networking-pitch-secure}}
                 </p>
             </div>
             <div class="w-33-l ml5-l ph5 ph0-l mt5 mt0-l">
                 <div class="domain-icon">
-                    <img src="/static/images/gears-network.svg" alt="Connected gears" />
-                    <h3>Concurrent at scale</h3>
+                    <img src="/static/images/gears-network.svg" alt="{{text networking-pitch-concurrent-alt}}" />
+                    <h3>{{text networking-pitch-concurrent-header}}</h3>
                 </div>
                 <p>
-                    Use any mixture of concurrency approaches that works for you.
-                    Rust will make sure you don’t accidentally share state between threads or tasks.
-                    It empowers you to squeeze every last bit of scaling, fearlessly.
+                    {{text networking-pitch-concurrent}}
                 </p>
             </div>
         </div>

templates/components/what/networking/production.hbs

@@ -1,7 +1,7 @@
 <section id="production" class="white">
     <div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
         <header>
-            <h2>Production use</h2>
+            <h2>{{text networking-production}}</h2>
             <div class="highlight"></div>
         </header>
         <div class="testimonials">
@@ -10,29 +10,17 @@
                     <img src="/static/images/firefox.png" alt="firefox" />
                 </div>
                 <div class="w-70-l">
-                    <blockquote>
-                        Migrating our Push connection infrastructure to Rust has provided us with an easier to maintain
-                        code-base with a focus on correctness while delivering fantastic performance. We are now
-                        handling up to 20 million websocket connections at once during peak hours with Rust servers.
-                    </blockquote>
+                    <blockquote>{{text networking-production-testimonial-mozilla}}</blockquote>
                     <p class="attribution">
-                        &ndash; Benjamin Bangert, Staff Engineer,
-                        Mozilla
+                        &ndash; {{text networking-production-testimonial-mozilla-attribution}}
                     </p>
                 </div>
             </div>
             <div class="testimonial flex flex-row">
                 <div class="w-70-l">
-                    <blockquote>
-                        Rust is foundational to the Linkerd project’s technology roadmap. Its type system allows us to
-                        build modular, testable, composable units without sacrificing runtime performance. What’s been
-                        most surprising, though, is how Rust’s lifetime/borrow checking system allows us to avoid large
-                        classes of resource leaks. After 2 years, I really can’t imagine using any other language for
-                        the job.
-                    </blockquote>
+                    <blockquote>{{text networking-production-testimonial-buoyant}}</blockquote>
                     <p class="attribution">
-                        &ndash; Oliver Gould, CTO,
-                        <a href="https://buoyant.io/">Buoyant</a>
+                        &ndash; {{text networking-production-testimonial-buoyant-attribution}}
                     </p>
                 </div>
                 <div class="w-30-l tc pa3">
@@ -44,17 +32,9 @@
                     <img src="/static/images/1aim.svg" alt="1aim" />
                 </div>
                 <div class="w-70-l">
-                    <blockquote>
-                        Rust's powerful type system enables safe refactoring and catches many classes of bugs at
-                        compile time. Its low footprint and high performance, complemented by guaranteed memory safety
-                        and rock-solid error handling make it perfect for writing security critical and complex
-                        business logic for our backend. The ultra-high stability means that our Rust applications are
-                        the last part of our stack we ever have to worry about. We have been running a almost 100% Rust
-                        backend in production since end of 2015 and it has never failed us so far!
-                    </blockquote>
+                    <blockquote>{{text networking-production-testimonial-1aim}}</blockquote>
                     <p class="attribution">
-                        &ndash; Yann Leretaille,
-                        <a href="https://1aim.com/">1aim</a>
+                        &ndash; {{text networking-production-testimonial-1aim-attribution}}
                     </p>
                 </div>
             </div>

templates/what/networking.hbs

@@ -2,7 +2,7 @@
 
 <header class="mt3 mt2-ns mb4 mb5-ns tc tl-ns">
   <div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
-    <h1>Networking</h1>
+    <h1>{{text networking-header}}</h1>
   </div>
 </header>