Start docs overhaul (#119)

* Website update (#104)

* Remove technical material from eth2 section + minor edits (#97)

* Update team.yml

* Update Nimbus docs

* add newsletter to header, footer, and mobile

* remove eth2-temp

* add mamy's feedback

* add donation address

* fix github link, add page on fluffy

* edit contribute message

* Update fluffy.md (#112)

Remove some outdated resources and small clean-up

* try and fix fluffy 404

* try and fix fluffy 404

* try and fix fluffy 404

* try and fix fluffy 404

* try and fix fluffy 404

* try and fix fluffy 404

* try and fix fluffy 404

* update homepage (#115)

* homepage edits

* cp

* update docs home

* doc updates

Co-authored-by: Kim De Mey <kim.demey@gmail.com>

source/docs/eth1.md

@@ -1,13 +1,13 @@
 ---
 id: eth1
-title: Connecting to the eth1 chain
+title: Execution layer client (eth1)
 ---
 
-While our core focus so far has been Ethereum 2.0, going forward we will be devoting significantly more resources to our Ethereum 1.0 client. As it stands, however, this software is very much experimental.
+While our core focus so far has been Ethereum 2, we are now devoting significant resources to our Ethereum 1 client.
 
 ## Quickstart
 
-To run Nimbus in [Ethereum 1.0 mode](https://github.com/status-im/nimbus-eth1), first [install the prerequisites](https://github.com/status-im/nimbus-eth1#prerequisites).
+To run Nimbus in [Ethereum 1 mode](https://github.com/status-im/nimbus-eth1), first [install the prerequisites](https://github.com/status-im/nimbus-eth1#prerequisites).
 
 Then run the following commands:
 
@@ -24,6 +24,6 @@ make nimbus
 ./build/nimbus
 ```
 
->  **Note:** We currently do not guarantee that Nimbus will work on Windows.
+Nimbus will now run and attempt to synchronize with the Ethereum 1 blockchain. 
 
-Nimbus will now run and attempt to synchronize with the Ethereum 1.0 blockchain. 
+For a more complete overview see the [repository README](https://github.com/status-im/nimbus-eth1).

source/docs/eth2.md

@@ -1,21 +1,14 @@
 ---
 id: eth2
-title: Connecting to the eth2 chain
+title: Consensus layer client (eth2)
 ---
 
-Depending on your objective, there are various ways to run Nimbus in [Ethereum 2.0 mode](https://github.com/status-im/nimbus-eth2).
+Depending on your objective, there are various ways to run Nimbus in [Ethereum 2 mode](https://github.com/status-im/nimbus-eth2).
 
 The reference documentation is [the Nimbus Book](https://nimbus.guide): it explains all the ways in which you can play with Nimbus, and use Nimbus to either monitor the eth2 chain or become a fully-fledged validator.
 
 We encourage you to check it out here: https://nimbus.guide
 
 
-## Prater testnet
-
-The latest Eth2 testnet, [Prater](https://twitter.com/Butta_eth/status/1374383003011452937), is now open to the public.
-
-Prater's objective is to ensure that the network remains stable under a higher load than we've seen so far on mainnet -- the genesis count for Prater was 210k (almost double the size of the Beacon Chain Mainnet).
-
-For more, see the [Prater page](https://nimbus.guide/prater.html) of the Nimbus guide.
 
 

themes/navy/languages/en.yml

@@ -21,8 +21,8 @@ sidebar:
   docs:
     Nimbus: Nimbus
     introduction: What Is Nimbus?
-    eth1: eth1 client
+    eth1: Execution layer (eth1) client
-    eth2: eth2 client
+    eth2: Consensus layer (eth2) client
     fluffy: Fluffy
     libraries: Software Libraries
     milestones: Milestones

themes/navy/layout/index.swig

@@ -21,7 +21,7 @@ Nimbus is a client implementation for both Ethereum 1 and Ethereum 2 that strive
         <div class="work-item">
                 <img class="work-item-image work-item-image-right" src="../img/graphic-platform-support.svg" />
                 <div class="work-item-inner">
-                    <h2>Consensus layer(eth2)</h2>
+                    <h2>Consensus layer (eth2)</h2>
                     <p>You can use Nimbus today to both monitor the eth2 chain and join the network as a fully-fledged validator.
                     </p>
         <a href="https://nimbus.guide">See our guide <img src="../img/arrow_orange.svg" /></a>