Fix/redirect and typo (#300)

* fix redirection and typo from other sections * add redirection links * remove comma * update redirect type * updated button color
matter-labs · Feb 16, 2023 · ce24791 · ce24791
1 parent d155893
commit ce24791
Show file tree

Hide file tree

Showing 5 changed files with 66 additions and 6 deletions.
diff --git a/docs/.vuepress/config.ts b/docs/.vuepress/config.ts
@@ -17,7 +17,7 @@ export default defineUserConfig({
     "/": {
       lang: "en-US",
       title: "",
-      description: "zkSync is a user-centric zk rollup platform from Matter Labs. It is a scaling solution for Ethereum, already live on Ethereum mainnet.",
+      description: "zkSync Era is a user-centric zk rollup platform from Matter Labs. It is a scaling solution for Ethereum, already live on Ethereum mainnet.",
     }
   },
 

diff --git a/docs/.vuepress/sidebar/en.ts b/docs/.vuepress/sidebar/en.ts
@@ -154,7 +154,7 @@ export const enSidebar = sidebar({
       ],
     },
     {
-      text: "zkSync CLI", // required
+      text: "zkSync Era CLI", // required
       link: "/api/tools/zksync-cli/", // optional, which should be a absolute path.
       children: []    
     },

diff --git a/docs/.vuepress/styles/index.scss b/docs/.vuepress/styles/index.scss
@@ -409,4 +409,8 @@ a.brand {
 
 span.contributor:nth-child(n+5) {
     display: none !important;
+}
+
+.newsletter-button {
+    color: #1e69ff;
 }
diff --git a/docs/api/api.md b/docs/api/api.md
@@ -6,7 +6,7 @@ As long as the code does not involve deploying new smart contracts (they can onl
 
 It is possible to continue using the SDK that is currently in use. Users will continue paying fees in ETH, and the UX will be identical to the one on Ethereum.
 
-However, zkSync has its specifics, which this section describes.
+However, zkSync Era has its specifics, which this section describes.
 
 ## EIP712
 
@@ -82,7 +82,7 @@ Returns the fee for the transaction. The token in which the fee is calculated is
 
 ### `zks_getMainContract`
 
-Returns the address of the zkSync contract.
+Returns the address of the zkSync Era contract.
 
 ### Input parameters
 
@@ -106,7 +106,7 @@ None.
 
 ### `zks_getConfirmedTokens`
 
-Given `from` and `limit` return information about the confirmed tokens with IDs in the interval `[from..from+limit-1]`. "Confirmed" is the wrong word here, since a confirmed token has already been bridged through the default zkSync bridge.
+Given `from` and `limit` return information about the confirmed tokens with IDs in the interval `[from..from+limit-1]`. "Confirmed" is the wrong word here, since a confirmed token has already been bridged through the default zkSync Era bridge.
 
 The tokens are returned in alphabetical order by their symbols, so a token's id is just its place in an array of tokens that has been sorted by symbols.
 
@@ -176,7 +176,7 @@ Otherwise, the object of the following format is returned:
 
 The `id` is the position of the leaf in the Merkle tree of L2->L1 messages for the block. The `proof` is the Merkle proof for the message, while the `root ` is the root of the Merkle tree of L2->L1 messages. Please note, that the Merkle tree uses _sha256_ for the trees.
 
-You do not need to care about the intrinsics, since the returned `id` and `proof` can be used right away for interacting with the zkSync smart contract.
+You do not need to care about the intrinsics, since the returned `id` and `proof` can be used right away for interacting with the zkSync Era smart contract.
 
 A nice example of using this endpoint via our SDK can be found [here](../dev/developer-guides/bridging/l2-l1.md).
 

diff --git a/firebase.json b/firebase.json
@@ -77,6 +77,62 @@
         "source": "/",
         "destination": "/docs/",
         "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/contracts/system-contracts.html",
+        "destination": "/dev/building-on-zksync/contracts/system-contracts.html",
+        "type": "302"
+      },
+
+      {
+        "source": "/dev/developer-guides/contracts/system-contracts.html",
+        "destination": "/dev/building-on-zksync/contracts/system-contracts.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/zksync-v2/aa.html",
+        "destination": "/dev/developer-guides/aa.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/hello-world.html",
+        "destination": "/dev/building-on-zksync/hello-world.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/contracts/contract-verification.html",
+        "destination": "/dev/building-on-zksync/contracts/contract-verification.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/building-on-zksync/events.html",
+        "destination": "/dev/building-on-zksync/events.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/building-on-zksync/events.html",
+        "destination": "/dev/building-on-zksync/events.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/contracts/contracts.html",
+        "destination": "/dev/building-on-zksync/contracts/contracts.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/contracts/contract-deployment.html",
+        "destination": "/dev/building-on-zksync/contracts/contract-deployment.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/building-on-zksync/bridging/l1-l2-interop.html",
+        "destination": "/dev/developer-guides/bridging/l1-l2-interop.html",
+        "type": "302"
+      },
+      {
+        "source": "/dev/developer-guides/contracts/contract-deployment.html",
+        "destination": "/dev/building-on-zksync/contracts/contract-deployment.html",
+        "type": "302"
       }
     ]
     }