NixOS · Nov 16, 2020
Showing with 25 additions and 28 deletions.

+25 −28 overview.tt
diff --git a/overview.tt b/overview.tt
@@ -1,13 +1,12 @@
-[% WRAPPER layout.tt title="Overview" handlesLayout=1 %]
+[% WRAPPER layout.tt title="Explore" handlesLayout=1 %]
 
 <div class="page-title">
   <h1>Overview</h1>
 </div>
 
 <section class="overview-description">
-  Step on a journey to <strong>explore and learn</strong> why so many developers, system
-  administrators and other enthusiasts use Nix and cannot imagine a world
-  without it.
+  Find out why so many developers, system administrators and other enthusiasts
+  use Nix and cannot imagine a world without it.
 </section>
 
 <section class="overview-benefits">
@@ -32,6 +31,7 @@
                    in which we should explain how it works? and why it works
                    the way it is works?
         -->
+        <li>reproducibility</li>
         <li>complete dependencies</li>
         <li>build sandbox</li>
       </ul>
@@ -75,8 +75,9 @@
       <div>
         <p>
           Keeping the project's installation instructions up to date is a never
-          ending task. Nix allows you to specify your system dependencies
-          alongside your project's dependencies in a declarative way.
+          ending task. Language specific package managers are good at
+          dependencies in their specific language. But can not provide other
+          dependencies. Nix solves this TODO).
         </p>
         <p>
           Instead of complicated installation instructions, with Nix the
@@ -91,17 +92,12 @@
     [% PROCESS svg path="site-styles/assets/gfx-overview-looking.svg" %]
     <div>
       <h2>
-        Either it works or fails - always in the same way.
+        TODO: talk about CI
       </h2>
       <p>
-        With Nix there are two results: the code either works or fails always
-        in the same way. This gives you the power to reproduce (and avoid) any
-        build-related bugs.
       </p>
       <ul>
         <li>reproducibility</li>
-        <li>transparent source binary model</li>
-        <li>nix language</li>
         <li>continuous integration</li>
       </ul>
       <div>
@@ -110,6 +106,7 @@
           sync with continuous integration (CI) is a disaster waiting to
           happen. Being able to use the same environment locally or anywhere
           else is putting a developer back in control.
+          TODO: which this specificaly put developer in control
         </p>
       </div>
     </div>
@@ -121,8 +118,8 @@
         From zero to cloud.
       </h2>
       <p>
-        Use the same tool to build one project or even one hundred projects,
-        configure machines and deploy to the cloud.
+        Use the same tool to build projects, configure machines and deploy to
+        the cloud.
       </p>
       <ul>
         <li>cloud images</li>
@@ -136,10 +133,8 @@
           DevOps dream.
         </p>
         <p>
-          Forget <code>Dockerfile</code> and
-          gain peace of mind with the declarative approach Nix gives you. Nix
-          automatically calculates the optimal layer layout and only includes
-          software needed.
+          Forget <code>Dockerfile</code> and build docker images with Nix in a
+          declarative and efficient way.
           <strong>Nix and Docker is a match made in heaven.</strong>
         </p>
       </div>
@@ -150,29 +145,29 @@
     [% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
     <div>
       <h2>
-        Previous version better? Rollback anytime.
+        Previous version better? Roll back anytime.
       </h2>
       <p>
         Packages are never overwritten, and old versions are always stored.
-        Rollback to any previous version within milliseconds.
+        Rollback to previous version with ease.
       </p>
       <ul>
-        <li>generations</li>
+        <li>rollback</li>
         <li>garbage collection</li>
         <li>atomic</li>
         <li>nix store</li>
       </ul>
       <div>
         <p>
-          Since Nix never overwrites files in the Nix store, but just adds new
-          versions in different paths, upgrades are atomic. During an
-          upgrade, there is no time window in which some files exists from the
-          old version and some files from the new version - which would be bad
-          because a program might crash if it's restarted during that period.
+          Since Nix never overwrites files, but just adds new versions in
+          different paths, upgrades are atomic. During an upgrade, there is no
+          time window in which some files exists from the old version and some
+          files from the new version - which would be bad because a program
+          might crash if it's restarted during that period.
         </p>
         <p>
           And since nothing is overwritten, the old versions are still there
-          after an upgrade. This means that you can rollback to the old
+          after an upgrade. This means that you can quickly rollback to the old
           version.
         </p>
       </div>
@@ -187,7 +182,7 @@
         Experiment without fear.
       </h2>
       <ul>
-        <li>generations</li>
+        <li>rollback</li>
         <li>nix store</li>
       </ul>
       <p>
@@ -210,6 +205,7 @@
     </div>
   </div>
 
+  <!--
   <div>
     [% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
     <div>
@@ -237,6 +233,7 @@
       </div>
     </div>
   </div>
+  -->
 
   <div>
     [% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]