Oisin/rebase (#314)

* Just testing out the commit flow

* testing 2nd change

* An extra info box for CDVN, explaining that it's set to Holesky by default, and that the network can be changed with the .env.sample file.

This should go live on Feb 6th, at the same time that we change CDVN to Holesky by default.

* Changing the link to the DV Launchpad page of the docs with all the links, rather than a link directly to the Goerli launchpad page

* changed the link to docker to directly link to the Ubuntu installation page

* small changes

* re-did the quickstart, merged and deleted some pages. (Generally trying to reduce complexity of folders)

* adding back in the further reading folder as suggested by Toma

* removing "how and where to run DVs" until it's ready, as suggested by Toma

* implemented all changes suggested by Toma on our call in the morning of Feb 13th

* Copy changes

* Merge sdk static pages

* fixed broken links

* fixing more broken links

* fixed all broken links (hopefully)

* Fixing links (made a dummy /sdk for now)

* Update guides

* embed sdk markdown page in docs

* update sdk.md

* use docusaurus-plugin-typedoc

* bump a new version to use docSidebar navbar item instead of pushing to docs/next

* update versions

* comment out the plugin used to geenrate sdk docs

* update redoc version

* use static file for api docs until fetching from docs-json error is fixed

* reuse swagger json for api docs

* update yarn.lock

* update v0.19.1

* use static file for build to pass

* use the api url

* use updates sidebar with v0.19.1

* remove duplicate file

* Fix SDK ref, attempt to fix links with redirects plus some rollbacks

* redirect didn't work, just putting the faq folder back where it was

---------

Co-authored-by: “Max <“[email protected]”>
Co-authored-by: thomasheremans <[email protected]>
Co-authored-by: HananINouman <[email protected]>

Author: 4 people

.gitignore

@@ -21,3 +21,4 @@ yarn-debug.log*
 yarn-error.log*
 
 .idea/*
+.vscode/

docs/int/quickstart/advanced/_category_.json renamed to docs/advanced/_category_.json

@@ -1,5 +1,5 @@
 {
     "label": "Advanced Guides",
-    "position": 10,
+    "position": 3,
     "collapsed": true
   }

docs/int/quickstart/advanced/adv-docker-configs.md renamed to docs/advanced/adv-docker-configs.md

@@ -6,7 +6,7 @@ description: Run a distributed validator cluster with the builder API (MEV-Boost
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# Run a cluster with MEV enabled
+# Enable MEV
 
 :::caution
 Charon is in a beta state and should be used with caution according to its [Terms of Use](https://obol.tech/terms.pdf).

docs/int/quickstart/advanced/monitoring.md renamed to docs/advanced/monitoring.md

@@ -82,7 +82,7 @@ Run the following command:
 
 ```sh
 # Combine a clusters private keys
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v0.19.0 combine --cluster-dir /opt/charon/cluster --output-dir /opt/charon/combined
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v0.19.1 combine --cluster-dir /opt/charon/cluster --output-dir /opt/charon/combined
 ```
 
 This command will store the combined keys in the `output-dir`, in this case a folder named `combined`.

docs/int/quickstart/advanced/obol-monitoring.md renamed to docs/advanced/obol-monitoring.md

@@ -12,7 +12,7 @@ import TabItem from '@theme/TabItem';
 The Obol-SDK is in a beta state and should be used with caution on testnets only.
 :::
 
-This is a walkthrough of using the [Obol-SDK](https://www.npmjs.com/package/@obolnetwork/obol-sdk) to propose a four-node distributed validator cluster for creation using the [DV Launchpad](../../../dvl/intro.md).
+This is a walkthrough of using the [Obol-SDK](https://www.npmjs.com/package/@obolnetwork/obol-sdk) to propose a four-node distributed validator cluster for creation using the [DV Launchpad](../dvl/intro.md).
 
 ## Pre-requisites
 
@@ -85,9 +85,9 @@ console.log(
 
 ## Invite the Operators to complete the DKG
 
-Once the Obol-API returns a `configHash` string from the `createClusterDefinition` method, you can use this identifier to invite the operators to the [Launchpad](../../../dvl/intro.md) to complete the process
+Once the Obol-API returns a `configHash` string from the `createClusterDefinition` method, you can use this identifier to invite the operators to the [Launchpad](../dvl/intro.md) to complete the process
 
-1. Operators navigate to `https://<NETWORK_NAME_HERE>.launchpad.obol.tech/dv?configHash=<CONFIG_HASH_HERE>` and complete the [run a DV with others](../group/quickstart-group-operator.md) flow.
+1. Operators navigate to `https://<NETWORK_NAME_HERE>.launchpad.obol.tech/dv?configHash=<CONFIG_HASH_HERE>` and complete the [run a DV with others](../start/quickstart_group.md) flow.
 1. Once the DKG is complete, and operators are using the `--publish` flag, the created cluster details will be posted to the Obol API
 1. The creator will be able to retrieve this data with `obol.getClusterLock(configHash)`, to use for activating the newly created validator.
 

docs/int/quickstart/advanced/quickstart-builder-api.md renamed to docs/advanced/quickstart-builder-api.md

@@ -10,12 +10,12 @@ Charon is in a beta state and should be used with caution according to its [Term
 
 This process should only be used if you want to split an *existing validator private key* into multiple private key shares for use in a Distributed Validator Cluster. If your existing validator is not properly shut down before the Distributed Validator starts, your validator may be slashed.
 
-If you are starting a new validator, you should follow a [quickstart guide](../index.md) instead.
+If you are starting a new validator, you should follow a [quickstart guide](../start/quickstart_overview.md) instead.
 
 If you use MEV-Boost, make sure you turned off your MEV-Boost service for the time of splitting the keys, otherwise you may hit [this issue](https://github.com/ObolNetwork/charon/issues/2770).
 :::
 
-Split an existing Ethereum validator key into multiple key shares for use in an [Obol Distributed Validator Cluster](../../key-concepts#distributed-validator-cluster).
+Split an existing Ethereum validator key into multiple key shares for use in an [Obol Distributed Validator Cluster](../int/key-concepts.md#distributed-validator-cluster).
 
 
 ## Pre-requisites
@@ -58,7 +58,7 @@ At the end of this process, you should have a tree like this:
 Run the following docker command to split the keys:
 
 ```shell
-CHARON_VERSION=                # E.g. v0.19.0
+CHARON_VERSION=                # E.g. v0.19.1
 CLUSTER_NAME=                  # The name of the cluster you want to create.
 WITHDRAWAL_ADDRESS=            # The address you want to use for withdrawals.
 FEE_RECIPIENT_ADDRESS=         # The address you want to use for fee payments.

docs/int/quickstart/advanced/quickstart-combine.md renamed to docs/advanced/quickstart-combine.md

@@ -35,4 +35,4 @@ Configure **ALL** charon nodes in your cluster to use this relay:
 
 Note that a local `relay/.charon/charon-enr-private-key` file will be created next to `relay/docker-compose.yml` to ensure a persisted relay ENR across restarts.
 
-A list of publicly available relays that can be used is maintained [here](../../faq/risks.md#risk-obol-hosting-the-relay-infrastructure). 
+A list of publicly available relays that can be used is maintained [here](../int/faq/risks.md).