update Changing_Tutorial_Text with all changes from main

.gitignore

@@ -9,7 +9,6 @@
 .cache-loader
 
 # Misc
-.idea
 .DS_Store
 .env.local
 .env.development.local
@@ -19,6 +18,3 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
-
-# Editor
-.idea

README.md

@@ -1,118 +1,41 @@
-# Deploy Docusaurus website to GitHub Pages using GitHub Actions
+# Website
 
-This repository is an example of deploying a Docusaurus website to GitHub Pages using GitHub Actions.
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
 
-## Configuring the GitHub repository
+### Installation
 
-It uses the _new_ GitHub Pages experience with GitHub Actions to deploy the website.
-
-Enable this experience in _GitHub.com -> Repository -> Settings -> Pages -> Build and deployment -> Source_ by selecting _GitHub Actions_ instead of the legacy _Deploy from a branch_ option.
-
-In _GitHub.com -> Repository -> Settings -> Environments_ you should see a GitHub Environment named `github-pages`.
-
-## Configuring Docusaurus
+```
+$ yarn
+```
 
-Generate a Docusuarus website using the following command:
+### Local Development
 
-```shell
-yarn create docusaurus <folder-name> classic --typescript
+```
+$ yarn start
 ```
 
-Make the following changes to the `docusaurus.config.js` configuration file:
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
 
-1. Create the constants `organizationName` and `projectName`
-   ```javascript
-   const organizationName = "<github-organization-name>";
-   const projectName = "<repository-name>";
-   ```
-1. Set the URL
-   ```javascript
-   const config = {
-     // (...)
-     url: `https://${organizationName}.github.io`,
-   };
-   const baseUrl = /${projectName}/`;
-   ```
-1. Configure the base URL
-   ```javascript
-   const config = {
-     // (...)
-     baseUrl: `/${projectName}/`,
-   };
-   ```
-1. Set the `organizationName` and `projectName` options
+### Build
 
-   ```javascript
-   const organizationName = "<github-organization-name>";
-   const projectName = "<repository-name>";
+```
+$ yarn build
+```
 
-   const config = {
-     // (...)
-     organizationName,
-     projectName,
-   };
-   ```
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
 
-1. Configure the blog and docs edit URLs
-   ```javascript
-   const config = {
-     // (...)
-     presets: [
-       [
-         "classic",
-         /** @type {import('@docusaurus/preset-classic').Options} */
-         ({
-           // (...)
-           docs: {
-             // (...)
-             editUrl: `https://github.com/${organizationName}/${projectName}/tree/main/`,
-           },
-           blog: {
-             // (...)
-             editUrl: `https://github.com/${organizationName}/${projectName}/tree/main/`,
-           },
-         }),
-       ],
-     ],
-   };
-   ```
+### Deployment
 
-## Adding a GitHub Actions deployment workflow
+Using SSH:
 
-Use a GitHub Actions workflow template for GitHub Pages from the [`actions/starter-workflows`](https://github.com/actions/starter-workflows) repository. Place it in `.github/workflows/<workflow-name>.yml`.
+```
+$ USE_SSH=true yarn deploy
+```
 
-Add steps for building the website before the GitHub Pages actions are executed and specify the `path` to the `actions/upload-pages-artifact`:
+Not using SSH:
 
-```yaml
-# (...)
-jobs:
-  deploy:
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-      # 👇 Build steps
-      - name: Set up Node.js
-        uses: actions/setup-node@v3
-        with:
-          node-version: 16.x
-          cache: yarn
-      - name: Install dependencies
-        run: yarn install --frozen-lockfile --non-interactive
-      - name: Build
-        run: yarn build
-      # 👆 Build steps
-      - name: Setup Pages
-        uses: actions/configure-pages@v1
-      - name: Upload artifact
-        uses: actions/upload-pages-artifact@v1
-        with:
-          # 👇 Specify build output path
-          path: build
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v1
 ```
+$ GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

blog/tags.yml

@@ -0,0 +1,16 @@
+facebook:
+  label: Facebook
+  permalink: /facebook
+  description: Facebook tag description
+hello:
+  label: Hello
+  permalink: /hello
+  description: Hello tag description
+docusaurus:
+  label: Docusaurus
+  permalink: /docusaurus
+  description: Docusaurus tag description
+hola:
+  label: Hola
+  permalink: /hola
+  description: Hola tag description

docs/Resources/contract-documentation/bridge/BridgeCustomErrors.md → docs/Contract-Documentation/Bridge-Contract-Documentation/Bridge-Custom-Errors.md

@@ -1,8 +1,8 @@
 ---
-title: BridgeCustomErrors
+sidebar_position: 2
 ---
 
-## BridgeCustomErrors
+# Bridge Custom Errors
 
 ### B_CANNOT_RECEIVE
 
@@ -134,4 +134,4 @@ error B_WRONG_TO_ADDRESS()
 
 ```solidity
 error B_ZERO_SIGNAL()
-```
+```

docs/Resources/contract-documentation/bridge/BridgedERC20.md → docs/Contract-Documentation/Bridge-Contract-Documentation/Bridge-ERC20.md

@@ -1,4 +1,8 @@
-## BridgedERC20
+---
+sidebar_position: 4
+---
+
+# Bridged ERC20
 
 ### srcToken
 
@@ -70,4 +74,4 @@ _any address can call this_
 function source() public view returns (address, uint256)
 ```
 
-_returns the srcToken being bridged and the srcChainId_
+_returns the srcToken being bridged and the srcChainId_

docs/Resources/contract-documentation/bridge/BridgeErrors.md → docs/Contract-Documentation/Bridge-Contract-Documentation/Bridge-Errors.md

@@ -1,4 +1,8 @@
-## BridgeErrors
+---
+sidebar_position: 3
+---
+
+# Bridge Errors
 
 ### B_CANNOT_RECEIVE
 
@@ -130,4 +134,4 @@ error B_WRONG_TO_ADDRESS()
 
 ```solidity
 error B_ZERO_SIGNAL()
-```
+```

docs/Resources/contract-documentation/bridge/Bridge.md → docs/Contract-Documentation/Bridge-Contract-Documentation/Bridge.md

@@ -1,4 +1,8 @@
-## Bridge
+---
+sidebar_position: 1
+---
+
+# Bridge
 
 Bridge contract which is deployed on both L1 and L2. Mostly a thin wrapper
 which calls the library implementations. See _IBridge_ for more details.
@@ -122,4 +126,4 @@ function hashMessage(struct IBridge.Message message) public pure returns (bytes3
 
 ```solidity
 function getMessageStatusSlot(bytes32 msgHash) public pure returns (bytes32)
-```
+```

docs/Resources/contract-documentation/bridge/EtherVault.md → docs/Contract-Documentation/Bridge-Contract-Documentation/Ether-Vault.md

@@ -1,4 +1,8 @@
-## EtherVault
+---
+sidebar_position: 5
+---
+
+# Ether Vault
 
 EtherVault is a special vault contract that:
 
@@ -94,4 +98,4 @@ Get the authorized status of an address.
 
 | Name | Type    | Description                              |
 | ---- | ------- | ---------------------------------------- |
-| addr | address | Address to get the authorized status of. |
+| addr | address | Address to get the authorized status of. |

docs/Resources/contract-documentation/bridge/IBridge.md → docs/Contract-Documentation/Bridge-Contract-Documentation/I-Bridge.md

@@ -1,4 +1,8 @@
-## IBridge
+---
+sidebar_position: 6
+---
+
+# I Bridge
 
 Bridge interface.
 
@@ -106,4 +110,4 @@ Returns the bridge state context.
 
 ```solidity
 function hashMessage(struct IBridge.Message message) external pure returns (bytes32)
-```
+```