chore(docs): refactoring guides and some other nits

docs/.gitignore

@@ -25,3 +25,4 @@ yarn-error.log*
 
 package-lock.json
 versions.json
+.supermavenignore

docs/README.md

@@ -28,7 +28,13 @@ yarn build
 ### Local Development
 
 ```
-yarn workspace docs start
+yarn workspace docs version
+```
+
+This command fetches and compiles the list of documentation versions to build with.
+
+```
+yarn workspace docs dev
 ```
 
 This command starts a local development server and opens up a browser window. Most changes are

docs/docs/getting_started/installation/other_install_methods.md → docs/docs/getting_started/noir_installation.md

@@ -1,5 +1,5 @@
 ---
-title: Alternative Installations
+title: Standalone Noir Installation
 description: There are different ways to install Nargo, the one-stop shop and command-line tool for developing Noir programs. This guide explains how to specify which version to install when using noirup, and using WSL for windows.
 keywords: [
     Installation
@@ -14,11 +14,9 @@ keywords: [
     Direnv
     Uninstalling Nargo
   ]
-sidebar_position: 1
+sidebar_position: 2
 ---
 
-## Encouraged Installation Method: Noirup
-
 Noirup is the endorsed method for installing Nargo, streamlining the process of fetching binaries or compiling from source. It supports a range of options to cater to your specific needs, from nightly builds and specific versions to compiling from various sources.
 
 ### Installing Noirup
@@ -40,6 +38,7 @@ With `noirup`, you can easily switch between different Nargo versions, including
   ```
 
 - **Specific Version**: Install a specific version of Nargo.
+
   ```sh
   noirup --version <version>
   ```
@@ -79,6 +78,7 @@ With `noirup`, you can easily switch between different Nargo versions, including
   ```
 
 - **From Local Source**: Compile and install from a local directory.
+
   ```sh
   noirup --path ./path/to/local/source
   ```
@@ -89,7 +89,7 @@ The default backend for Noir (Barretenberg) doesn't provide Windows binaries at
 
 Step 1: Follow the instructions [here](https://learn.microsoft.com/en-us/windows/wsl/install) to install and run WSL.
 
-step 2: Follow the [Noirup instructions](#encouraged-installation-method-noirup).
+step 2: Follow the [Noirup instructions](#installing-noirup).
 
 ## Uninstalling Nargo
 

docs/docs/getting_started/hello_noir/project_breakdown.md → docs/docs/getting_started/project_breakdown.md

@@ -5,7 +5,7 @@ description:
   file, and how to prove and verify your program.
 keywords:
   [Nargo, Nargo project, Prover.toml, proof verification, private asset transfer]
-sidebar_position: 2 
+sidebar_position: 1
 ---
 
 This section breaks down our hello world program from the previous section.
@@ -46,7 +46,7 @@ license = "MIT"
 ecrecover = {tag = "v0.9.0", git = "https://github.com/colinnielsen/ecrecover-noir.git"}
 ```
 
-Nargo.toml for a [workspace](../../noir/modules_packages_crates/workspaces.md) will look a bit different. For example:
+Nargo.toml for a [workspace](../noir/modules_packages_crates/workspaces.md) will look a bit different. For example:
 
 ```toml
 [workspace]
@@ -66,11 +66,11 @@ The package section defines a number of fields including:
 - `entry` (optional) - a relative filepath to use as the entry point into your package (overrides the default of `src/lib.nr` or `src/main.nr`)
 - `backend` (optional)
 - `license` (optional)
-- `expression_width` (optional) - Sets the default backend expression width. This field will override the default backend expression width specified by the Noir compiler (currently set to width 4). 
+- `expression_width` (optional) - Sets the default backend expression width. This field will override the default backend expression width specified by the Noir compiler (currently set to width 4).
 
 #### Dependencies section
 
-This is where you will specify any dependencies for your project. See the [Dependencies page](../../noir/modules_packages_crates/dependencies.md) for more info.
+This is where you will specify any dependencies for your project. See the [Dependencies page](../noir/modules_packages_crates/dependencies.md) for more info.
 
 `./proofs/` and `./contract/` directories will not be immediately visible until you create a proof or
 verifier contract respectively.