From 169a1909d441e69bb6845c1099b4cb51fe5e7720 Mon Sep 17 00:00:00 2001
From: Chase Fleming <chasefleming@users.noreply.github.com>
Date: Tue, 16 Jan 2024 17:12:27 -0800
Subject: [PATCH] Add EVM page (#515)

* Add EVM page

* Remove cadence in top nav

* Change to "EVM"

* Fix url

* Remove

* Move to own page

* Remove page and add redirect

* Add slash to url

* Change old links

* Fix grammar

* Remove unused category

* Fix links

* Add positioni

* Add to sidebars

---------

Co-authored-by: Chase Fleming <1666730+chasefleming@users.noreply.github.com>
---
 docs/build/basics/transactions.md             |   2 +-
 .../cadence-reference/_category_.yml          |   1 -
 .../cadence-reference/json-cadence-spec.md    | 871 ------------------
 docs/evm/about.md                             |  45 +
 docs/networks/node-ops/nodes/access-api.md    |  10 +-
 .../node-ops/nodes/archive-access-api.md      |   4 +-
 .../flow-cli/accounts/account-add-contract.md |   4 +-
 .../accounts/account-update-contract.md       |   4 +-
 docs/tools/flow-cli/flix.md                   |   2 +-
 .../tools/flow-cli/scripts/execute-scripts.md |   4 +-
 .../transactions/build-transactions.md        |   4 +-
 .../transactions/send-transactions.md         |   4 +-
 docs/tutorials/dapp-infrastructure.md         |   4 +-
 docusaurus.config.js                          |   5 +-
 sidebars.js                                   |   1 +
 vercel.json                                   |   5 +
 16 files changed, 75 insertions(+), 895 deletions(-)
 delete mode 100644 docs/build/smart-contracts/cadence-reference/_category_.yml
 delete mode 100644 docs/build/smart-contracts/cadence-reference/json-cadence-spec.md
 create mode 100644 docs/evm/about.md

diff --git a/docs/build/basics/transactions.md b/docs/build/basics/transactions.md
index 050d560ccf..4b558ec492 100644
--- a/docs/build/basics/transactions.md
+++ b/docs/build/basics/transactions.md
@@ -40,7 +40,7 @@ transaction(greeting: String) {
 
 **Arguments**
 
-Transactions may declare parameters it needs during execution, these must be provided as input arguments when sending a transaction. You can think of them as function arguments. Currently, we provide [arguments in the JSON-Cadence Data Interchange Format](../smart-contracts/cadence-reference/json-cadence-spec.md). Which is a human-readable JSON format. The sample script from above accepts a single `String` argument.
+Transactions may declare parameters it needs during execution, these must be provided as input arguments when sending a transaction. You can think of them as function arguments. Currently, we provide [arguments in the JSON-Cadence Data Interchange Format](https://cadencelang.dev/docs/1.0/json-cadence-spec). Which is a human-readable JSON format. The sample script from above accepts a single `String` argument.
 
 **Reference Block**
 
diff --git a/docs/build/smart-contracts/cadence-reference/_category_.yml b/docs/build/smart-contracts/cadence-reference/_category_.yml
deleted file mode 100644
index e50ac98c5b..0000000000
--- a/docs/build/smart-contracts/cadence-reference/_category_.yml
+++ /dev/null
@@ -1 +0,0 @@
-label: Cadence Reference
\ No newline at end of file
diff --git a/docs/build/smart-contracts/cadence-reference/json-cadence-spec.md b/docs/build/smart-contracts/cadence-reference/json-cadence-spec.md
deleted file mode 100644
index 69541262c6..0000000000
--- a/docs/build/smart-contracts/cadence-reference/json-cadence-spec.md
+++ /dev/null
@@ -1,871 +0,0 @@
----
-title: JSON-Cadence Data Interchange Format
-sidebar_label: JSON-Cadence format
----
-
-# JSON-Cadence Data Interchange Format
-
-> Version 0.3.1
-
-JSON-Cadence is a data interchange format used to represent Cadence values as language-independent JSON objects.
-
-This format includes less type information than a complete [ABI](https://en.wikipedia.org/wiki/Application_binary_interface), and instead promotes the following tenets:
-
-- **Human-readability** - JSON-Cadence is easy to read and comprehend, which speeds up development and debugging.
-- **Compatibility** - JSON is a common format with built-in support in most high-level programming languages, making it easy to parse on a variety of platforms.
-- **Portability** - JSON-Cadence is self-describing and thus can be transported and decoded without accompanying type definitions (i.e. an ABI).
-
-## Values
-
----
-
-### Void
-
-```json
-{
-  "type": "Void"
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Void"
-}
-```
-
----
-
-### Optional
-
-```json
-{
-  "type": "Optional",
-  "value": null | <value>
-}
-```
-
-#### Example
-
-```json
-// Non-nil
-
-{
-  "type": "Optional",
-  "value": {
-    "type": "UInt8",
-    "value": "123"
-  }
-}
-
-// Nil
-
-{
-  "type": "Optional",
-  "value": null
-}
-```
-
----
-
-### Bool
-
-```json
-{
-  "type": "Bool",
-  "value": true | false
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Bool",
-  "value": true
-}
-```
-
----
-
-### String
-
-```json
-{
-  "type": "String",
-  "value": "..."
-}
-
-```
-
-#### Example
-
-```json
-{
-  "type": "String",
-  "value": "Hello, world!"
-}
-```
-
----
-
-### Address
-
-```json
-{
-  "type": "Address",
-  "value": "0x0" // as hex-encoded string with 0x prefix
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Address",
-  "value": "0x1234"
-}
-```
-
----
-
-### Integers
-
-`[U]Int`, `[U]Int8`, `[U]Int16`, `[U]Int32`,`[U]Int64`,`[U]Int128`, `[U]Int256`,  `Word8`, `Word16`, `Word32`, or `Word64`
-
-Although JSON supports integer literals up to 64 bits, all integer types are encoded as strings for consistency.
-
-While the static type is not strictly required for decoding, it is provided to inform client of potential range.
-
-```json
-{
-  "type": "<type>",
-  "value": "<decimal string representation of integer>"
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "UInt8",
-  "value": "123"
-}
-```
-
----
-
-### Fixed Point Numbers
-
-`[U]Fix64`
-
-Although fixed point numbers are implemented as integers, JSON-Cadence uses a decimal string representation for readability.
-
-```json
-{
-    "type": "[U]Fix64",
-    "value": "<integer>.<fractional>"
-}
-```
-
-#### Example
-
-```json
-{
-    "type": "Fix64",
-    "value": "12.3"
-}
-```
-
----
-
-### Array
-
-```json
-{
-  "type": "Array",
-  "value": [
-    <value at index 0>,
-    <value at index 1>
-    // ...
-  ]
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Array",
-  "value": [
-    {
-      "type": "Int16",
-      "value": "123"
-    },
-    {
-      "type": "String",
-      "value": "test"
-    },
-    {
-      "type": "Bool",
-      "value": true
-    }
-  ]
-}
-```
-
----
-
-### Dictionary
-
-Dictionaries are encoded as a list of key-value pairs to preserve the deterministic ordering implemented by Cadence.
-
-```json
-{
-  "type": "Dictionary",
-  "value": [
-    {
-      "key": "<key>",
-      "value": <value>
-    },
-    ...
-  ]
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Dictionary",
-  "value": [
-    {
-      "key": {
-        "type": "UInt8",
-        "value": "123"
-      },
-      "value": {
-        "type": "String",
-        "value": "test"
-      }
-    }
-  ],
-  // ...
-}
-```
-
----
-
-### Composites (Struct, Resource, Event, Contract, Enum)
-
-Composite fields are encoded as a list of name-value pairs in the order in which they appear in the composite type declaration.
-
-```json
-{
-  "type": "Struct" | "Resource" | "Event" | "Contract" | "Enum",
-  "value": {
-    "id": "<fully qualified type identifier>",
-    "fields": [
-      {
-        "name": "<field name>",
-        "value": <field value>
-      },
-      // ...
-    ]
-  }
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Resource",
-  "value": {
-    "id": "0x3.GreatContract.GreatNFT",
-    "fields": [
-      {
-        "name": "power",
-        "value": {"type": "Int", "value": "1"}
-      }
-    ]
-  }
-}
-```
-
----
-
-### Path
-
-```json
-{
-  "type": "Path",
-  "value": {
-    "domain": "storage" | "private" | "public",
-    "identifier": "..."
-  }
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Path",
-  "value": {
-    "domain": "storage",
-    "identifier": "flowTokenVault"
-  }
-}
-```
-
----
-
-### Type Value
-
-```json
-{
-  "type": "Type",
-  "value": {
-    "staticType": <type>
-  }
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Type",
-  "value": {
-    "staticType": {
-      "kind": "Int",
-    }
-  }
-}
-```
-
----
-
-### Capability
-
-```json
-{
-  "type": "Capability",
-  "value": {
-    "path": <path>,
-    "address": "0x0",  // as hex-encoded string with 0x prefix
-    "borrowType": <type>,
-  }
-}
-```
-
-#### Example
-
-```json
-{
-  "type": "Capability",
-  "value": {
-    "path": {
-      "type": "Path",
-      "value": {
-        "domain": "public",
-        "identifier": "someInteger"
-      }
-    },
-    "address": "0x1",
-    "borrowType": {
-      "kind": "Int"
-    }
-  }
-}
-```
-
----
-
-### Functions
-
-```json
-{
-  "type": "Function",
-  "value": {
-    "functionType": <type>
-  }
-}
-```
-
-Function values can only be exported, they cannot be imported.
-
-#### Example
-
-```json
-{
-  "type": "Function",
-  "value": {
-    "functionType": {
-      "kind": "Function",
-      "typeID": "(():Void)",
-      "parameters": [],
-      "return": {
-        "kind": "Void"
-      }
-    }
-  }
-}
-```
-
----
-
-## Types
-
-### Simple Types
-
-These are basic types like `Int`, `String`, or `StoragePath`.
-
-```json
-{
-  "kind": "Any" | "AnyStruct" | "AnyResource" | "AnyStructAttachment" | "AnyResourceAttachment" | "Type" |
-    "Void" | "Never" | "Bool" | "String" | "Character" |
-    "Bytes" | "Address" | "Number" | "SignedNumber" |
-    "Integer" | "SignedInteger" | "FixedPoint" |
-    "SignedFixedPoint" | "Int" | "Int8" | "Int16" |
-    "Int32" | "Int64" | "Int128" | "Int256" | "UInt" |
-    "UInt8" | "UInt16" | "UInt32" | "UInt64" | "UInt128" |
-    "UInt256" | "Word8" | "Word16" | "Word32" | "Word64" |
-    "Fix64" | "UFix64" | "Path" | "CapabilityPath" | "StoragePath" |
-    "PublicPath" | "PrivatePath" | "AuthAccount" | "PublicAccount" |
-    "AuthAccount.Keys" | "PublicAccount.Keys" | "AuthAccount.Contracts" |
-    "PublicAccount.Contracts" | "DeployedContract" | "AccountKey" | "Block"
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "UInt8"
-}
-```
-
----
-
-### Optional Types
-
-```json
-{
-  "kind": "Optional",
-  "type": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Optional",
-  "type": {
-    "kind": "String"
-  }
-}
-```
-
----
-
-### Variable Sized Array Types
-
-```json
-{
-  "kind": "VariableSizedArray",
-  "type": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "VariableSizedArray",
-  "type": {
-    "kind": "String"
-  }
-}
-```
-
----
-
-### Constant Sized Array Types
-
-```json
-{
-  "kind": "ConstantSizedArray",
-  "type": <type>,
-  "size": <length of array>,
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "ConstantSizedArray",
-  "type": {
-    "kind": "String"
-  },
-  "size":3
-}
-```
-
----
-
-### Dictionary Types
-
-```json
-{
-  "kind": "Dictionary",
-  "key": <type>,
-  "value": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Dictionary",
-  "key": {
-    "kind": "String"
-  },
-  "value": {
-    "kind": "UInt16"
-  },
-}
-```
-
----
-
-### Composite Types
-
-```json
-{
-  "kind": "Struct" | "Resource" | "Event" | "Contract" | "StructInterface" | "ResourceInterface" | "ContractInterface",
-  "type": "", // this field exists only to keep parity with the enum structure below; the value must be the empty string
-  "typeID": "<fully qualified type ID>",
-  "initializers": [
-    <initializer at index 0>,
-    <initializer at index 1>
-    // ...
-  ],
-  "fields": [
-    <field at index 0>,
-    <field at index 1>
-    // ...
-  ],
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Resource",
-  "type": "",
-  "typeID": "0x3.GreatContract.GreatNFT",
-  "initializers":[
-    [
-      {
-        "label": "foo",
-        "id": "bar",
-        "type": {
-          "kind": "String"
-        }
-      }
-    ]
-  ],
-  "fields": [
-    {
-      "id": "foo",
-      "type": {
-        "kind": "String"
-      }
-    }
-  ]
-}
-```
-
----
-
-### Field Types
-
-```json
-{
-  "id": "<name of field>",
-  "type": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "id": "foo",
-  "type": {
-    "kind": "String"
-  }
-}
-```
-
----
-
-### Parameter Types
-
-```json
-{
-  "label": "<label>",
-  "id": "<identifier>",
-  "type": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "label": "foo",
-  "id": "bar",
-  "type": {
-    "kind": "String"
-  }
-}
-```
-
----
-
-### Initializer Types
-
-Initializer types are encoded a list of parameters to the initializer.
-
-```json
-[
-  <parameter at index 0>,
-  <parameter at index 1>,
-  // ...
-]
-```
-
-#### Example
-
-```json
-[
-  {
-    "label": "foo",
-    "id": "bar",
-    "type": {
-      "kind": "String"
-    }
-  }
-]
-```
-
----
-
-### Function Types
-
-```json
-{
-  "kind": "Function",
-  "typeID": "<function name>",
-  "parameters": [
-    <parameter at index 0>,
-    <parameter at index 1>,
-    // ...
-  ],
-  "return": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Function",
-  "typeID": "foo",
-  "parameters": [
-    {
-      "label": "foo",
-      "id": "bar",
-      "type": {
-        "kind": "String"
-      }
-    }
-  ],
-  "return": {
-    "kind": "String"
-  }
-}
-```
-
----
-
-### Reference Types
-
-```json
-{
-  "kind": "Reference",
-  "authorized": true | false,
-  "type": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Reference",
-  "authorized": true,
-  "type": {
-    "kind": "String"
-  }
-}
-```
-
----
-
-### Restricted Types
-
-```json
-{
-  "kind": "Restriction",
-  "typeID": "<fully qualified type ID>",
-  "type": <type>,
-  "restrictions": [
-    <type at index 0>,
-    <type at index 1>,
-    //...
-  ]
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Restriction",
-  "typeID": "0x3.GreatContract.GreatNFT",
-  "type": {
-    "kind": "AnyResource",
-  },
-  "restrictions": [
-    {
-        "kind": "ResourceInterface",
-        "typeID": "0x1.FungibleToken.Receiver",
-        "fields": [
-            {
-                "id": "uuid",
-                "type": {
-                    "kind": "UInt64"
-                }
-            }
-        ],
-        "initializers": [],
-        "type": ""
-    }
-  ]
-}
-```
-
----
-
-### Capability Types
-
-```json
-{
-  "kind": "Capability",
-  "type": <type>
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Capability",
-  "type": {
-    "kind": "Reference",
-    "authorized": true,
-    "type": {
-      "kind": "String"
-    }
-  }
-}
-```
-
----
-
-### Enum Types
-
-```json
-{
-  "kind": "Enum",
-  "type": <type>,
-  "typeID": "<fully qualified type ID>",
-  "initializers":[],
-  "fields": [
-    {
-      "id": "rawValue",
-      "type": <type>
-    }
-  ]
-}
-```
-
-#### Example
-
-```json
-{
-  "kind": "Enum",
-  "type": {
-    "kind": "String"
-  },
-  "typeID": "0x3.GreatContract.GreatEnum",
-  "initializers":[],
-  "fields": [
-    {
-      "id": "rawValue",
-      "type": {
-        "kind": "String"
-      }
-    }
-  ]
-}
-```
-
-### Repeated Types
-
-When a composite type appears more than once within the same JSON type encoding, either because it is
-recursive or because it is repeated (e.g. in a composite field), the composite is instead
-represented by its type ID.
-
-#### Example
-
-```json
-{
-  "type":"Type",
-  "value": {
-    "staticType": {
-      "kind":"Resource",
-      "typeID":"0x3.GreatContract.NFT",
-      "fields":[
-        {"id":"foo",
-        "type": {
-          "kind":"Optional",
-          "type":"0x3.GreatContract.NFT" // recursive NFT resource type is instead encoded as an ID
-          }
-        }
-      ],
-      "initializers":[],
-      "type":""
-    }
-  }
-}
-```
diff --git a/docs/evm/about.md b/docs/evm/about.md
new file mode 100644
index 0000000000..b50b549cbc
--- /dev/null
+++ b/docs/evm/about.md
@@ -0,0 +1,45 @@
+---
+title: About EVM on Flow
+sidebar_label: About EVM on Flow
+sidebar_position: 1
+---
+
+# About EVM on Flow
+
+Flow is a secure Layer 1 blockchain committed to driving Web3 adoption into the mainstream. The team behind the blockchain not only coined the term NFT but made strides in opening up web3 to the world through Disney Pinnacle, NBA Topshot and Doodles. A significant milestone in this journey is the introduction of Ethereum Virtual Machine (EVM) equivalency in 2024. 
+
+### **Seamless Integration for Ethereum Developers**
+
+With EVM equivalency, Solidity developers from the Ethereum ecosystem can effortlessly deploy their smart contracts on Flow with no changes to their code. We’re currently building up partnerships so that all one’s favorite developer tools, oracles, and platforms are compatible on day one.
+
+**Key Advantages**
+
+- **Access New Markets**: Easily tap into Flow's user base and unique IPs without any implementation risk.
+- **Simplified Multi-Chain Experience**: Ideal for applications without a multi-chain approach or those wanting to ensure cross-chain compatibility.
+- **Leverage Flow’s Protocol**: Expand EVM capabilities and transcend EVM limitations using Cadence, which offers a powerful new account model, programmable resources, and hybrid ownership.
+- **No Miner Extractable Value (MEV)**: Leading to a more fair and secure environment for all participants and minimizing the risk of front running transactions.
+- **Enhanced Functionality**:
+    - Compose assets and functionality using a shared world state and [Cadence contracts](https://cadence-lang.org/).
+    - Conduct multiple contract interactions atomically.
+    - Tap in to [Capabilities](https://cadence-lang.org/docs/tutorial/capabilities) for zero-transfer access ([Account Linking](https://developers.flow.com/build/advanced-concepts/account-linking)).
+- **Gas Fees**: Transactions are extremely low-cost and denominated in FLOW.
+
+## Learn More and Join the Conversation
+
+**Interested in Partnering or Co-marketing?**
+
+Are you interested in launching an EVM project on Flow or partnering? Participate in our weekly EVM office hours for discussions on project development and co-marketing opportunities.
+
+**Further Reading and Discussions**
+
+- [Why EVM on Flow: Beyond Solidity](https://forum.flow.com/t/evm-on-flow-beyond-solidity/5260)
+- [Path to EVM Equivalence on Flow](https://forum.flow.com/t/evm-equivalence-on-flow-proposal-and-path-forward/5478)
+
+**Flow Improvement Proposals (FLIPs)**
+
+- Understanding [EVM Support on Flow](https://github.com/onflow/flips/pull/225)
+- Exploring the [Flow VM Bridge](https://github.com/onflow/flips/pull/233/files/d5bc46c4b13f0b9b168a94f994c77a5a689f6b24..122e938b7acae7e774246b1b66aaf5979ca21444)
+- Insights into the [Flow EVM Gateway](https://github.com/onflow/flips/pull/235/files)
+- Integration of the [Cadence Interface](https://github.com/onflow/flips/blob/f646491ec895442dcccdb24d80080bab1c56188e/protocol/20231116-evm-support.md)
+
+More questions? Ask on the EVM [Discord](https://discord.com/channels/613813861610684416/1167476806333513800).
\ No newline at end of file
diff --git a/docs/networks/node-ops/nodes/access-api.md b/docs/networks/node-ops/nodes/access-api.md
index f1857c983d..ecdc192c7a 100644
--- a/docs/networks/node-ops/nodes/access-api.md
+++ b/docs/networks/node-ops/nodes/access-api.md
@@ -517,7 +517,7 @@ message AccountResponse {
 
 `ExecuteScriptAtLatestBlock` executes a read-only Cadence script against the latest sealed execution state.
 
-This method can be used to read execution state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+This method can be used to read execution state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ```proto
 rpc ExecuteScriptAtLatestBlock (ExecuteScriptAtLatestBlockRequest) returns (ExecuteScriptResponse)
@@ -556,7 +556,7 @@ message ExecuteScriptResponse {
 
 `ExecuteScriptAtBlockID` executes a ready-only Cadence script against the execution state at the block with the given ID.
 
-This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ```proto
 rpc ExecuteScriptAtBlockID (ExecuteScriptAtBlockIDRequest) returns (ExecuteScriptResponse)
@@ -589,7 +589,7 @@ message ExecuteScriptResponse {
 
 `ExecuteScriptAtBlockHeight` executes a ready-only Cadence script against the execution state at the given block height.
 
-This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ```proto
 rpc ExecuteScriptAtBlockHeight (ExecuteScriptAtBlockHeightRequest) returns (ExecuteScriptResponse)
@@ -971,7 +971,7 @@ message TransactionSignature {
 | Field                         | Description                                                                                          |
 | ----------------------------- | ---------------------------------------------------------------------------------------------------- |
 | script                        | Raw source code for a Cadence script, encoded as UTF-8 bytes                                         |
-| arguments                     | Arguments passed to the Cadence script, encoded as [JSON-Cadence](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md) bytes |
+| arguments                     | Arguments passed to the Cadence script, encoded as [JSON-Cadence](https://cadencelang.dev/docs/1.0/json-cadence-spec) bytes |
 | reference_block_id            | Block ID used to determine transaction expiry                                                        |
 | [proposal_key](#proposal-key) | Account key used to propose the transaction                                                          |
 | payer                         | Address of the payer account                                                                         |
@@ -1094,7 +1094,7 @@ message Event {
 | transaction_id    | ID of the transaction the event was emitted from                           |
 | transaction_index | Zero-based index of the transaction within the block                       |
 | event_index       | Zero-based index of the event within the transaction                       |
-| payload           | Event fields encoded as [JSON-Cadence values](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md) |
+| payload           | Event fields encoded as [JSON-Cadence values](https://cadencelang.dev/docs/1.0/json-cadence-spec) |
 
 ### Execution Result
 
diff --git a/docs/networks/node-ops/nodes/archive-access-api.md b/docs/networks/node-ops/nodes/archive-access-api.md
index 37c2d5670a..aff1f20c0b 100644
--- a/docs/networks/node-ops/nodes/archive-access-api.md
+++ b/docs/networks/node-ops/nodes/archive-access-api.md
@@ -71,7 +71,7 @@ message AccountResponse {
 
 `ExecuteScriptAtBlockID` executes a ready-only Cadence script against the execution state at the block with the given ID.
 
-This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ```proto
 rpc ExecuteScriptAtBlockID (ExecuteScriptAtBlockIDRequest) returns (ExecuteScriptResponse)
@@ -104,7 +104,7 @@ message ExecuteScriptResponse {
 
 `ExecuteScriptAtBlockHeight` executes a ready-only Cadence script against the execution state at the given block height.
 
-This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+This method can be used to read account state from the blockchain. The script is executed on an execution node and the return value is encoded using the [JSON-Cadence data interchange format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ```proto
 rpc ExecuteScriptAtBlockHeight (ExecuteScriptAtBlockHeightRequest) returns (ExecuteScriptResponse)
diff --git a/docs/tools/flow-cli/accounts/account-add-contract.md b/docs/tools/flow-cli/accounts/account-add-contract.md
index 94c2769b43..a17c98b6e3 100644
--- a/docs/tools/flow-cli/accounts/account-add-contract.md
+++ b/docs/tools/flow-cli/accounts/account-add-contract.md
@@ -79,7 +79,7 @@ Path to the file containing the contract source code.
 
 ### Arguments
 - Name: `argument`
-- Valid inputs: valid [cadence values](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md)
+- Valid inputs: valid [cadence values](https://cadencelang.dev/docs/1.0/json-cadence-spec)
   matching argument type in transaction code.
 
 Input arguments values matching corresponding types in the source code and passed in the same order.
@@ -113,7 +113,7 @@ Specify the name of the account that will be used to sign the transaction.
 
 Arguments passed to the Cadence transaction in Cadence JSON format.
 Cadence JSON format contains `type` and `value` keys and is
-[documented here](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+[documented here](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ### Include Fields
 
diff --git a/docs/tools/flow-cli/accounts/account-update-contract.md b/docs/tools/flow-cli/accounts/account-update-contract.md
index 0770b334c8..50e8dca309 100644
--- a/docs/tools/flow-cli/accounts/account-update-contract.md
+++ b/docs/tools/flow-cli/accounts/account-update-contract.md
@@ -77,7 +77,7 @@ Filename of the file containing contract source code.
 
 ### Arguments
 - Name: `argument`
-- Valid inputs: valid [cadence values](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md)
+- Valid inputs: valid [cadence values](https://cadencelang.dev/docs/1.0/json-cadence-spec)
   matching argument type in transaction code.
 
 Input arguments values matching corresponding types in the source code and passed in the same order.
@@ -118,7 +118,7 @@ Shows a diff to approve before updating between deployed contract and new contra
 
 Arguments passed to the Cadence transaction in Cadence JSON format.
 Cadence JSON format contains `type` and `value` keys and is
-[documented here](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+[documented here](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ### Include Fields
 
diff --git a/docs/tools/flow-cli/flix.md b/docs/tools/flow-cli/flix.md
index e784fc454d..5fd6e070ee 100644
--- a/docs/tools/flow-cli/flix.md
+++ b/docs/tools/flow-cli/flix.md
@@ -310,7 +310,7 @@ You can pass a `nil` value to optional arguments by executing the flow FLIX exec
 
 Arguments passed to the Cadence script in the Cadence JSON format.
 Cadence JSON format contains `type` and `value` keys and is 
-[documented here](../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+[documented here](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ## Pre Fill
 
diff --git a/docs/tools/flow-cli/scripts/execute-scripts.md b/docs/tools/flow-cli/scripts/execute-scripts.md
index 3ac5d1bc38..f73dbe783c 100644
--- a/docs/tools/flow-cli/scripts/execute-scripts.md
+++ b/docs/tools/flow-cli/scripts/execute-scripts.md
@@ -39,7 +39,7 @@ script to be executed.
 
 ### Arguments
 - Name: `argument`
-- Valid inputs: valid [cadence values](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md)
+- Valid inputs: valid [cadence values](https://cadencelang.dev/docs/1.0/json-cadence-spec)
   matching argument type in script code.
 
 Input arguments values matching corresponding types in the source code and passed in the same order.
@@ -56,7 +56,7 @@ You can pass a `nil` value to optional arguments by executing the flow script li
 
 Arguments passed to the Cadence script in the Cadence JSON format.
 Cadence JSON format contains `type` and `value` keys and is 
-[documented here](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+[documented here](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ### Host
 
diff --git a/docs/tools/flow-cli/transactions/build-transactions.md b/docs/tools/flow-cli/transactions/build-transactions.md
index fb0ed897b1..569f1a1791 100644
--- a/docs/tools/flow-cli/transactions/build-transactions.md
+++ b/docs/tools/flow-cli/transactions/build-transactions.md
@@ -82,7 +82,7 @@ transaction to be executed.
 
 ### Arguments
 - Name: `argument`
-- Valid inputs: valid [cadence values](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md)
+- Valid inputs: valid [cadence values](https://cadencelang.dev/docs/1.0/json-cadence-spec)
   matching argument type in transaction code.
 
 Input arguments values matching corresponding types in the source code and passed in the same order.
@@ -133,7 +133,7 @@ Read more about authorizers [here](../../../build/basics/transactions.md).
 
 Arguments passed to the Cadence transaction in Cadence JSON format.
 Cadence JSON format contains `type` and `value` keys and is
-[documented here](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+[documented here](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ### Gas Limit
 
diff --git a/docs/tools/flow-cli/transactions/send-transactions.md b/docs/tools/flow-cli/transactions/send-transactions.md
index 219eabbea0..135d83a63d 100644
--- a/docs/tools/flow-cli/transactions/send-transactions.md
+++ b/docs/tools/flow-cli/transactions/send-transactions.md
@@ -79,7 +79,7 @@ transaction to be executed.
 
 ### Arguments
 - Name: `argument`
-- Valid inputs: valid [cadence values](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md) 
+- Valid inputs: valid [cadence values](https://cadencelang.dev/docs/1.0/json-cadence-spec) 
   matching argument type in transaction code.
 
 Input arguments values matching corresponding types in the source code and passed in the same order.
@@ -149,7 +149,7 @@ Specify the name of the account(s) that will be used as authorizer(s) in the tra
 
 Arguments passed to the Cadence transaction in Cadence JSON format.
 Cadence JSON format contains `type` and `value` keys and is 
-[documented here](../../../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+[documented here](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 ### Gas Limit
 
diff --git a/docs/tutorials/dapp-infrastructure.md b/docs/tutorials/dapp-infrastructure.md
index 1f635a51ca..316931ec25 100644
--- a/docs/tutorials/dapp-infrastructure.md
+++ b/docs/tutorials/dapp-infrastructure.md
@@ -34,7 +34,7 @@ Events are data objects emitted at the end of a transaction that describe the st
 
 Events can be used to notify your off-chain infrastructure of important state changes in your smart contracts. For example, if a user purchases an NFT from your storefront smart contract, an event will be emitted that describes this purchase. Your web application, which displays the NFTs for sale, can then capture that event and remove the NFT from the sale list.
 
-You can query events through the Flow Access API using the available [Flow SDKs](../tools/clients/index.md). Event data is returned in [JSON-Cadence format](../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+You can query events through the Flow Access API using the available [Flow SDKs](../tools/clients/index.md). Event data is returned in [JSON-Cadence format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
 
 #### Event Reflection Database
 
@@ -53,4 +53,4 @@ At any point, your dapp can execute a query to read the state of your contracts.
 
 Events follow a push model, whereas script queries follow a pull model. Your dapp may need to check the state of your contracts without waiting for an event to be emitted. 
 
-You can execute scripts through the Flow Access API using the available [Flow SDKs](../tools/clients/index.md). Like events, script results are returned in [JSON-Cadence format](../build/smart-contracts/cadence-reference/json-cadence-spec.md).
+You can execute scripts through the Flow Access API using the available [Flow SDKs](../tools/clients/index.md). Like events, script results are returned in [JSON-Cadence format](https://cadencelang.dev/docs/1.0/json-cadence-spec).
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 426a0b435b..402998cd10 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -262,9 +262,10 @@ const config = {
             activeBasePath: '/build',
           },
           {
-            href: 'https://cadence-lang.org/docs/',
+            to: 'evm/about',
             position: 'left',
-            label: 'Cadence',
+            label: 'EVM',
+            activeBasePath: '/evm',
           },
           {
             to: 'tools/flow-cli',
diff --git a/sidebars.js b/sidebars.js
index 34773b41b0..8a2a55cddb 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -89,6 +89,7 @@ const sidebars = {
     },
   ],
   build: [{ type: 'autogenerated', dirName: 'build' }],
+  evm: [{ type: 'autogenerated', dirName: 'evm' }],
   nodeOps: [{ type: 'autogenerated', dirName: 'node-ops' }],
   tutorials: [{ type: 'autogenerated', dirName: 'tutorials' }],
   tools: [{ type: 'autogenerated', dirName: 'tools' }],
diff --git a/vercel.json b/vercel.json
index b0d37a469e..cfe5486061 100644
--- a/vercel.json
+++ b/vercel.json
@@ -1025,6 +1025,11 @@
       "source": "/references/run-and-secure/node-operation/:path*",
       "destination": "/architecture/node-ops/nodes/node-operation/:path*",
       "permanent": true
+    },
+    {
+      "source": "/build/smart-contracts/cadence-reference/json-cadence-spec",
+      "destination": "https://cadencelang.dev/docs/1.0/json-cadence-spec",
+      "permanent": true
     }
   ]
 }