OCL Migration

.gitignore

@@ -1,18 +1,28 @@
-.DS_Store
-.idea
-
-node_modules
+# Dependencies
+/node_modules
 
-lib/core/metadata.js
-lib/core/MetadataBlog.js
+# Production
+/build
+/dist
 
-website/translated_docs
-website/build/
-website/yarn.lock
-website/node_modules
-website/i18n/*
+# Generated files
+.docusaurus
+.cache-loader
 
-website/static/img/~$Prysm_Docs.pptx
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+.env
+.idea/
+.vscode/
 
-*.vscode
-*.vscode/*
+# Logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+logs
+*.log

README.md

@@ -1,37 +1,53 @@
 # Prysm Documentation Portal
 
-This repository houses all the documentation pertaining to the Prysm client and Ethereum 2. It is generated with [Docusaurus](https://github.com/facebook/docusaurus). 
+This repository houses all the documentation pertaining to the Prysm client and Ethereum. It is generated with [Docusaurus](https://github.com/facebook/docusaurus) and deployed with [Vercel](https://vercel.com/).
 
-Below are steps for initialising and reproducing this portal for development.
+Below are steps for initializing and reproducing this portal for development.
 
 ## Dependencies
 
-1.  The latest version of [Node](https://nodejs.org/en/download/) installed. 
-2. The latest version of [Yarn](https://yarnpkg.com/en/docs/install) installed. (Optional, but recommended)
+1. The latest version of [Node](https://nodejs.org/en/download/) installed.
+2. npm (comes with Node.js)
 
-    > You have to be on Node >= 8.x and Yarn >= 1.5.
+   > You have to be on Node >= 8.x.
 
 ## Installation
 
 1. Clone this repository.
-2. Enter the newly cloned repo and enter the `website` directory.
-3. Issue the command `npm install`
+2. Enter the newly cloned repo.
+3. Issue the command `npm install`.
 4. Wait for the installation process to complete.
 
-## Running the development server  
+## Running the development server
 
-1. From within the `website` directory, run the local web server using `yarn start` or `npm start`.
-2.  Load the example site at http://localhost:3000 if it did not already open automatically. If port 3000 has already been taken, another port will be used. Look at the console messages to see which.
+1. From the root directory, run the local web server using `npm start`.
+2. Load the example site at http://localhost:3000/prsym/docs if it did not already open automatically. If port 3000 has already been taken, another port will be used. Look at the console messages to see which.
+
+   You should see the example site loaded in your web browser. There's also a LiveReload server running, and any changes made to the docs and files in the project directory will cause the page to refresh.
 
-    You should see the example site loaded in your web browser. There's also a LiveReload server running, and any changes made to the docs and files in the `website` directory will cause the page to refresh.
-
-
 ## Building Static HTML Pages
 
-To create a static build of the documentation portal, run the following script from the `website` directory:
+To create a static build of the documentation portal, run the following script from the root directory:
 
 ```bash
-yarn run build # or `npm run build`
+npm run build
 ```
 
-This will generate a `build` subdirectory within the `website` directory, containing the `.html` files from all of the docs and other files included in `pages`.
+This will generate a `build` directory containing the `.html` files from all of the docs and other files included in `pages`.
+
+## Deployment with Vercel
+
+This project is configured to be deployed with Vercel. The `vercel.json` file in the root directory contains the necessary configuration for deployment.
+
+To deploy:
+
+1. Push your changes to GitHub.
+2. Connect your GitHub repository to Vercel.
+3. Vercel will automatically build and deploy the site.
+
+Alternatively, you can use the Vercel CLI to deploy from your local machine:
+
+```bash
+npm install -g vercel
+vercel
+```

docs/404.md

@@ -0,0 +1,29 @@
+---
+title: Page Not Found
+description: The requested page could not be found
+hide_table_of_contents: true
+---
+
+# Page Not Found
+
+Sorry, we couldn't find the page you were looking for. This might be because:
+
+- The page has been moved or renamed
+- The URL contains a typo
+- The page no longer exists
+
+## What Can You Do?
+
+Here are some helpful links to get you back on track:
+
+- [Getting Started Guide](/) - Learn how to run Prysm
+- [Installation Options](//install/install-with-script) - Different ways to install Prysm
+- [FAQ](/faq) - Frequently asked questions
+- [Technical Documentation](/how-prysm-works/beacon-node) - Deep dive into how Prysm works
+
+You can also:
+- Use the search bar at the top of the page
+- Check the navigation menu on the left
+- [Report this broken link](https://github.com/prysmaticlabs/documentation/issues/new) if you think this is an error
+
+Need more help? Join our [Discord community](https://discord.gg/prysmaticlabs) for support.

website/docs/advanced/beacon_node_api.md → docs/advanced/beacon_node_api.md

@@ -26,7 +26,7 @@ While the default setting is sufficient for regular beacon chain functionality,
 
 ## Beacon chain API information  
 
-Full details of the Ethereum beacon API are available in the [Ethereum public API section](../how-prysm-works/ethereum-public-api.md). 
+Full details of the Ethereum beacon API are available in the [Ethereum public API section](/how-prysm-works/ethereum-public-api.md). 
 
 ## Command line/Configuration file usage:
 

website/docs/advanced/builder.md → docs/advanced/builder.md

@@ -6,7 +6,7 @@ sidebar_label: Configure MEV Builder
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
-import BuilderPng from '@site/static/img/builder.png';
+import BuilderPng from '@site/static/images/builder.png';
 
 :::caution
 
@@ -174,13 +174,13 @@ removing the `--http-mev-relay` flag from the beacon node will disconnect the bu
 ### Advanced Validator Registration
 There are other ways to configure your validator registrations for more granular control on which validator keys should be registered to use the custom builder and which ones should use local execution.
 In these cases you would replace the `--suggested-fee-recipient` flag with  `--proposer-settings-file` flag or `--proposer-settings-url` flag.
-- if configuring with the `--proposer-settings-file` flag and provide it with a suitable JSON or YAML file. This file should include the necessary configuration for the builder. For detailed guidance and an example of this configuration, refer to the [MEV Builder and Gas Limit configuration guide](../execution-node/fee-recipient.md#advanced-configure-mev-builder-and-gas-limit).
- - if configuring with the `--proposer-settings-url` flag provide a url that returns the JSON response with the suitable proposer-settings. A guide and example on this configuration can be found [here](../execution-node/fee-recipient.md#advanced-configure-mev-builder-and-gas-limit).
+- if configuring with the `--proposer-settings-file` flag and provide it with a suitable JSON or YAML file. This file should include the necessary configuration for the builder. For detailed guidance and an example of this configuration, refer to the [MEV Builder and Gas Limit configuration guide](/execution-node/fee-recipient.md#advanced-configure-mev-builder-and-gas-limit).
+ - if configuring with the `--proposer-settings-url` flag provide a url that returns the JSON response with the suitable proposer-settings. A guide and example on this configuration can be found [here](/execution-node/fee-recipient.md#advanced-configure-mev-builder-and-gas-limit).
  - if configuring with the `--proposer-settings-file` or `--proposer-settings-url` flag with no builder settings but providing the `--enable-builder` flag instead. Optionally, you can also add the `--suggested-gas-limit` to adjust the default gas limit for the builder, this only applies with `--enable-builder`.
 
 :::info
 
-Validators updated through the [Keymanager-API's](../how-prysm-works/keymanager-api.md) fee recipient APIs will take on the default `proposer-settings` provided.
+Validators updated through the [Keymanager-API's](/how-prysm-works/keymanager-api.md) fee recipient APIs will take on the default `proposer-settings` provided.
 
 If the `--enable-builder` flag is used without providing `--suggested-fee-recipient`, `--proposer-settings-file`, or `--proposer-settings-url` it will override builder settings from the db if proposer settings are saved, or it will set default builder settings and only save to the db if fee-recipient settings are saved through the keymanager APIs.
 
@@ -247,4 +247,4 @@ In the Prysm client, the builder is used through the relay to get transactions t
 
 **Q:** What if the earnings from the builder are lower than from local execution?
 
-**A:** The block from local execution will be used. This could also be triggered through `--local-block-value-boost` if the earnings from the builder don't pass some percentage threshold.
+**A:** The block from local execution will be used. This could also be triggered through `--local-block-value-boost` if the earnings from the builder don't pass some percentage threshold.

website/docs/advanced/maintaining-uptime.md → docs/advanced/maintaining-uptime.md

@@ -12,13 +12,13 @@ Validators should be online as much as possible. If you're running your validato
 
 :::caution
 
-This may be overkill for at-home stakers who use the `prysm.sh` script to run Prysm. To those users, we recommend **keeping it simple** by occasionally checking the status of your validator. See [Check Software Status](../monitoring/checking-status) to learn more.
+This may be overkill for at-home stakers who use the `prysm.sh` script to run Prysm. To those users, we recommend **keeping it simple** by occasionally checking the status of your validator. See [Check Software Status](/monitoring/checking-status) to learn more.
 
 :::
 
 ### Docker
 
-You can use Docker to run your beacon node and validators as background services. See [Install with Docker](../install/install-with-docker). You can monitor and view your running Docker containers using `docker ps`.
+You can use Docker to run your beacon node and validators as background services. See [Install with Docker](/install/install-with-docker). You can monitor and view your running Docker containers using `docker ps`.
 
 ### Systemd (Linux)
 

website/docs/advanced/migrating-keys.md → docs/advanced/migrating-keys.md

@@ -12,7 +12,7 @@ This document provides guidance on migrating Prysm and your validator keys from
 
 :::danger Slashing Prevention
 
-The following best practices will help minimize the risk of [slashing](../concepts/slashing.md) while migrating between machines:
+The following best practices will help minimize the risk of [slashing](/concepts/slashing.md) while migrating between machines:
 
 1.	Never run more than a single validator process with the same keys loaded.
 2.  Delete your keys from the old machine before starting your new machine.
@@ -202,7 +202,7 @@ You can also run the accounts backup command non-interactively by using the foll
 **Flag Usage**
 
 | Flag                     | Usage                                                                                                  |
-| ------------------------ | :----------------------------------------------------------------------------------------------------- |
+|--------------------------|:-------------------------------------------------------------------------------------------------------|
 | `--wallet-dir`           | Path to a wallet directory (default: "$HOME/Eth2Validators/prysm-wallet-v2")                           |
 | `--wallet-password-file` | Path to a plain-text, .txt file containing your wallet's password.                                     |
 | `--backup-dir`           | Path to a directory where accounts will be backed up into a zip file. (default: $HOME/Eth2Validators/) |
@@ -357,5 +357,3 @@ Once complete, verify the account removal using the validator accounts list comm
 **When I migrate my slashing protection history from Machine A -> Machine B, or Client A -> Client B, do I need to retain A's slashing protection history after importing to B?**
 
 No. After successfully importing your slashing protection history from A -> B, you can discard A. If you need to migrate from B -> C, B's slashing protection history is all you need to export/import.
-
-

website/docs/advanced/switch-clients.md → docs/advanced/switch-clients.md

@@ -12,7 +12,7 @@ This document provides guidance on moving from Prysm to a new consensus-layer cl
 
 :::danger Slashing Prevention
 
-The following best practices will help minimize the risk of [slashing](../concepts/slashing.md) while migrating between clients:
+The following best practices will help minimize the risk of [slashing](/concepts/slashing.md) while migrating between clients:
 
 1.	Never run more than a single validator process with the same keys loaded.
 2.	Maintain and utilize slashing protection.
@@ -27,7 +27,7 @@ Regardless of which client you are switching to, the first step of the process w
 
 Installation documentation links for each client can be found below:
 
-- Prysm: https://docs.prylabs.network/docs/install/install-with-script
+- Prysm: [Quickstart](/install/install-with-script)
 - Teku: https://docs.teku.consensys.io/development/get-started/install/install-binaries
 - Nimbus: https://nimbus.guide/quick-start.html  
 - Lighthouse: https://lighthouse-book.sigmaprime.io/installation.html  
@@ -39,19 +39,19 @@ Ensuring you stop and disable Prysm is critical to avoiding slashing events befo
 
 Disabling Prysm prevents it from automatically starting up again after a reboot. 
 
-Remove Prysm's validator keys as an added protection by following [these](http://localhost:3000/docs/advanced/migrating-keys#step-5--verification-and-restarting-the-validator-client) instructions.  
+Remove Prysm's validator keys as an added protection by following [these](/advanced/migrating-keys#step-5--verification-and-restarting-the-validator-client) instructions.  
 
 ### Step 3: Export slashing protection history
 
 Ensure that you stop Prysm before exporting slashing protection in order to capture all validator actions. 
 
-We have a section dedicated to exporting and importing slashing protection history [here.](https://docs.prylabs.network/docs/wallet/slashing-protection) Follow the steps regarding exporting slashing protection history. 
+We have a section dedicated to exporting and importing slashing protection history [here.](/wallet/slashing-protection) Follow the steps regarding exporting slashing protection history. 
 
 ### Step 4: Update port forwarding
 
 This step is not required for nodes which are running on a virtual public cloud, but keep in mind - nodes will be required to run a an execution client locally post merge!  
 
-By default, Prysm uses TCP/13000 and UDP/12000. Remove those two rules and replace them with the appropriate port forwards for the client you are switching to. The process will be very similar to the steps laid out [here.](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#port-forwarding) 
+By default, Prysm uses TCP/13000 and UDP/12000. Remove those two rules and replace them with the appropriate port forwards for the client you are switching to. The process will be very similar to the steps laid out [here.](/prysm-usage/p2p-host-ip#port-forwarding) 
 
 Teku, Nimbus, and Lighthouse all use port 9000 for both TCP and UDP. 
 
@@ -148,5 +148,3 @@ https://chainsafe.github.io/lodestar/run/validator-management/validator-cli#vali
 Ensure your beacon node is fully synced with the network by checking your clients logs prior to starting your validator. Once it is fully synced, start the validator.  
 
 Search a block explorer like https://beaconcha.in with your validator's public key to confirm that your validator is now active!
-
-

website/docs/audits/phase0.md → docs/audits/phase0.md

@@ -73,4 +73,4 @@ multiple scenarios.
 
 **Completion Date**: October 6, 2020
 
-**Report link**: [Trail of Bits - Prysm Phase 0 Final Report.pdf](/assets/Trail_of_Bits_Prysm_Phase_0_Final_Report.pdf)
+**Report link**: [Trail of Bits - Prysm Phase 0 Final Report.pdf](/assets/Trail_of_Bits_Prysm_Phase_0_Final_Report.pdf)

website/docs/concepts/blobs.md → docs/concepts/blobs.md

@@ -4,7 +4,7 @@ title: Blobs
 sidebar_label: Blobs
 ---
 
-import BlobsPng from '@site/static/img/blobs.png';
+import BlobsPng from '@site/static/images/blobs.png';
 
 
 :::info