Merge branch 'main' into develop

Author: imadarai

.github/ISSUE_TEMPLATE/broken-link.yaml

@@ -1,7 +1,7 @@
 name: Broken link
 description: Report a broken link to help us fix them.
 title: "[Broken Link]: "
-labels: ["fixlink"]
+labels: ["broken link"]
 body:
   - type: markdown
     attributes:

.netlify/_redirects_production

@@ -73,6 +73,8 @@ https://substrate-docs.netlify.app/* https://docs.substrate.io/:splat 301!
 /docs/en/knowledgebase/learn-substrate/*      /v3/concepts/:splat        301!
 /docs/en/knowledgebase/runtime                /v3/concepts/runtime       301!
 /docs/en/knowledgebase/runtime/               /v3/concepts/runtime       301!
+/docs/en/knowledgebase/runtime/pallets        /v3/runtime/frame#pallets  301!
+/docs/en/knowledgebase/runtime/origin         /v3/runtime/origins        301!
 
 ### Knowledge Base: Runtime Development
 /docs/en/knowledgebase/runtime/fees           /v3/runtime/weights-and-fees  301!
@@ -95,6 +97,10 @@ https://substrate-docs.netlify.app/* https://docs.substrate.io/:splat 301!
 /docs/en/knowledgebase/advanced/no-hash-collections/  /v3/advanced/hash-collections  301!
 /docs/en/knowledgebase/advanced/*             /v3/advanced/:splat           301!
 
+## Awesome Substrate Redirect 
+/awesome-substrate                            https://substrate.io/ecosystem/resources/awesome-substrate/
+/awesome-substrate/                           https://substrate.io/ecosystem/resources/awesome-substrate/
+
 ## Production: rustdocs
 /rustdocs/*          https://paritytech.github.io/substrate/:splat             200
 

gatsby-node.js

@@ -12,6 +12,10 @@ const redirects = [
   { fromPath: '/v3/integration/', toPath: '/v3/integration/polkadot-js/' },
   { fromPath: '/v3/advanced/', toPath: '/v3/advanced/account-info/' },
   { fromPath: '/tutorials/v3/kitties/', toPath: `/tutorials/v3/kitties/pt1/` },
+  {
+    fromPath: '/tutorials/v3/cumulus/',
+    toPath: `/tutorials/v3/cumulus/start-relay/`,
+  },
   {
     fromPath: '/how-to-guides/basics/',
     toPath: `/how-to-guides/v3/basics/pallet-integration/`,

v3/docs/03-runtime/c-metadata/index.mdx

@@ -9,16 +9,16 @@ keywords:
 
 Blockchains that are built on Substrate expose metadata in order to make it easier to interact with
 them. This metadata is separated by the different [pallets](/v3/runtime/frame#pallets) that inform your blockchain.
-For each module, the metadata provides information about the [storage items](../storage),
-[extrinsic calls](../../concepts/extrinsics), [events](../events-and-errors), constants, and errors that are
+For each module, the metadata provides information about the [storage items](/v3/runtime/storage),
+[extrinsic calls](/v3/concepts/extrinsics), [events](/v3/runtime/events-and-errors), constants, and errors that are
 exposed by that module. Substrate automatically generates this metadata for you and makes it
 available through RPC calls.
 
 Since the runtime of a Substrate blockchain is an evolving part of the blockchain's state,
 blockchain metadata is stored on a per-block basis. Be aware that querying the metadata for an older
 block (with an archive node, for example) could result in acquiring out-of-date metadata that is not
 compatible with a blockchain's current state. As described in the
-[Upgrades documentation](../upgrades), developers building on top of Substrate chains can
+[Upgrades documentation](/v3/runtime/upgrades), developers building on top of Substrate chains can
 expect that the metadata for a chain should _only_ change when the chain's
 [runtime `spec_version`](/rustdocs/latest/sp_version/struct.RuntimeVersion.html#structfield.spec_version)
 changes.
@@ -264,7 +264,7 @@ about the module's storage:
 ```
 
 Every storage item that is defined in a pallet will have a corresponding metadata entry. 
-Metadata entries like these are generated from [macros](../macros) using associated types from the [`frame-system`](/rustdocs/latest/frame_system/pallet/trait.Config.html) crate. For example:
+Metadata entries like these are generated from [macros](/v3/runtime/macros) using associated types from the [`frame-system`](/rustdocs/latest/frame_system/pallet/trait.Config.html) crate. For example:
 
 ```rust
 #[pallet::config]
@@ -450,11 +450,11 @@ the [`InvalidSpecName` error](/rustdocs/latest/frame_system/pallet/enum.Error.ht
 
 ### Learn more
 
-- [Storage](../storage)
+- [Storage](/v3/runtime/storage)
 - [SCALE](/v3/advanced/scale-codec)
-- [Macros](../macros)
-- [Events](../events-and-errors)
-- [Extrinsics](../../concepts/extrinsics)
+- [Macros](/v3/runtime/macros)
+- [Events](/v3/runtime/events-and-errors)
+- [Extrinsics](/v3/concepts/extrinsics)
 
 ### References
 

v3/docs/03-runtime/h-weights-and-fees/index.mdx

@@ -59,7 +59,7 @@ You can also use the Transaction Payment pallet to:
 
 * Manage the withdrawal, refund, and deposit of transaction fees using `Config::OnChargeTransaction`.
 
-You can learn more about these configuration traits in the [Transaction Payment](https://substrate.dev/rustdocs/latest/pallet_transaction_payment/index.html) documentation. 
+You can learn more about these configuration traits in the [Transaction Payment](/rustdocs/latest/pallet_transaction_payment/index.html) documentation. 
 
 You should note that transaction fees are withdrawn before the transaction is executed. 
 After the transaction is executed, the transaction weight can be adjusted to reflect the actual resources the transaction used. 
@@ -102,10 +102,10 @@ However, this scenario would be a rare occurrence because the transaction queue
 
 The inclusion fee formula always results in the same fee for the same input. 
 However, weight can be dynamic and—based on how
-[`WeightToFee`](https://substrate.dev/rustdocs/latest/pallet_transaction_payment/pallet/trait.Config.html#associatedtype.WeightToFee)
+[`WeightToFee`](/rustdocs/latest/pallet_transaction_payment/pallet/trait.Config.html#associatedtype.WeightToFee)
 is defined—the final fee can include some degree of variability. 
 
-To account for this variability, the Transaction Payment pallet provides the [`FeeMultiplierUpdate`](https://substrate.dev/rustdocs/latest/pallet_transaction_payment/pallet/trait.Config.html#associatedtype.FeeMultiplierUpdate) configurable parameter.
+To account for this variability, the Transaction Payment pallet provides the [`FeeMultiplierUpdate`](/rustdocs/latest/pallet_transaction_payment/pallet/trait.Config.html#associatedtype.FeeMultiplierUpdate) configurable parameter.
 
 The default update function is inspired by the Polkadot network and implements a targeted adjustment in which a target saturation level of block weight is defined. 
 If the previous block is more saturated, then the fees are slightly increased. 

v3/docs/03-runtime/i-benchmarking/index.mdx

@@ -22,7 +22,7 @@ large overhead such a process would introduce. Instead, Substrate expects benchm
 approximate maximum for the worst case scenario of executing an extrinsic. Users are charged assuming
 this worst case scenario path was taken, and if the extrinsic turns out needing less resources, some of 
 the estimated weight and fees can be returned. This is further explained in the 
-[Transaction Weights and Fees](../weights-and-fees) chapter.
+[Transaction Weights and Fees](/v3/runtime/weights-and-fees) chapter.
 
 ## Why benchmark a pallet
 

v3/docs/05-integrate/c-substrate-connect/index.mdx

@@ -7,77 +7,66 @@ category: tools
 keywords: client, wasm, rpc, node
 ---
 
-Rather than a single tool, [Substrate Connect](https://paritytech.github.io/substrate-connect/) is
-more of a tool-kit, or bundle of tools, that enable developers to build application specific light
-clients for Substrate based chains. It provides a more secure alternative than connecting to
-a JSON-RPC node to interact with the chain.
+[Substrate Connect](https://paritytech.github.io/substrate-connect/) is
+a JavaScript library and browser extension that builds on the [Polkadot JS 
+API](/v3/integration/polkadot-js#polkadot-js-api) to enable developers to build application 
+specific light clients for Substrate chains. By using light clients available to all 
+Substrate built blockchains, application developers no longer need to rely on single RPC 
+nodes to allow end-users to interact with their applications. This introduces 
+a new paradigm for decentralization: instead of specifying a centralized RPC node, developers 
+just need to specify the blockchain's [chain specification](/v3/runtime/chain-specs) for 
+their application to synchronize with the chain.
 
-Substrate Connect builds on the Polkadot JS API so building an app has the same experience as with
-using a traditional RPC server node. Its components are also part of the Substrate building
-framework and available for every Substrate based project.
 
 ## What it enables
 
-Substrate Connect provides the necessary infrastructure to run a Substrate light client in any
-Javascript or Node environment, from in-browser applications and extensions, to Electron apps,
+Substrate Connect provides application developers ways to run a Substrate light client in any 
+NodeJS environment, from in-browser applications and extensions, to Electron apps, 
 IOT devices, and mobile phones.
 
-Substrate Connect enables Substrate runtime engineers to:
+For in-browser end-users, Substrate Connect is a browser extension designed to facilitate 
+using applications with multiple blockchains, where all light clients can run in a single tab. 
 
--  Generate a light client of their chain in a single command.
--  Create an interface to run light nodes of different chains.
--  Create an interface to add runtimes and genesis configurations of their own chains.
+This implies two key features:
 
-For in-browser use, Substrate Connect provides a Browser Extension built upon the
-`@substrate/extension` node module. It is designed to give end-users the ability to contain all
-running light clients in one browser tab.
+1. **Ready-to-use light clients for Substrate chains.** Light clients are 
+part of the Substrate framework and with that, available for every Substrate based blockchain. This 
+means that all you need in order to connect a Substrate chain to your application is provide the
+[chain specification](/v3/runtime/chain-specs) of the chain you want to connect to.
 
-The extension runs a single light client, [Smoldot](https://github.com/paritytech/smoldot) that
-manages connecting to different blockchains. Whenever a user opens an app in a new browser tab it
-asks the extension to connect to whatever blockchains the app is interested in. The light client is
-smart enough to share resources so that it only connects to a network once even if there are
-multiple apps talking to it.
+2. **Bundling light-clients of multiple chains.** With the browser extension, end-users are able to 
+interact with applications connected to multiple blockchains or connect their own blockchains to
+applications that support it.
 
 ## Motivation
 
-1. Interacting with a Substrate chain via an RPC server requires a layer of 3rd party trust which
+Interacting with a Substrate chain via an RPC server requires a layer of third party trust which
 can be avoided. Substrate Connect uses a Wasm light client which connects to a Substrate chain
 without any unecessary intermediary.
 
-2. Due to browser limitations on websockets from HTTPS pages, establishing a good number of peers
-is difficult as many nodes need to be available with TLS (Transport Layer Security). Substrate
-Connect provides a browser extension to overcome this limitation and to keep the chains synced in
+In addition, due to browser limitations on websockets from HTTPS pages, establishing a good number of peers
+is difficult as nodes are reachable only if they provide a TLS (Transport Layer Security) certificate. 
+Substrate Connect provides a browser extension to overcome this limitation and to keep the chains synced in
 the background, making applications on a Substrate chain faster.
 
 ## How it works
 
-### Modules
-
-Substrate Connect currently has
-[4 different modules](https://paritytech.github.io/substrate-connect/api/modules.html):
-
-- `@substrate/connect`: provides a `Detector` class to detect whether a user has the Substrate
-Connect browser extension installed. If it isn't installed, it falls back to instantiating a WASM
-light client directly in the page.
-
-- `@substrate/connect-extension-protocol`: handles receiving and listening for messages from the
-browser extension and provider.
-
-- `@substrate/extension`: manages an app's connection to multiple blockchains, creating an instance
-of Smoldot and connecting the app to it.
+The extension runs a single light client, [Smoldot](https://github.com/paritytech/smoldot) that
+manages connecting to different blockchains. Whenever a user opens an app in a new browser tab it
+asks the extension to connect to whatever blockchains the app is interested in. The light client is
+smart enough to share resources so that it only connects to a network once even if there are
+multiple apps talking to it.
 
-- `@substrate/smoldot-test-utils`: utility functions for testing purposes.
+The [`@substrate/connect`](https://www.npmjs.com/package/@substrate/connect) library has the following 
+capabilities:
 
-The combination of these modules result in: 
+- It detects whether a user has the Substrate Connect browser extension installed. If it 
+isn't installed, it falls back to instantiating a light client directly in the page.
 
-1. **Ready-to-use Substrate Wasm Light-Clients to be executed in the browser.** They are part of
-the Substrate framework and with that, available for every Substrate based project. If developers
-want to generate a light client of their chain, all it takes is just one command to compile a
-library that contains everything that's needed to run a light client in the browser.
+- It handles receiving and listening for messages from the browser extension and provider.
 
-2. **A node module that bundles the light-clients of different chains.** It provides an interface
-that allows developers to run light nodes of different chains and to add runtimes and genesis
-configurations of their own chain.
+- It manages an app's connection to multiple blockchains, creating an instance of Smoldot 
+and connecting the app to it.
 
 ### Usage
 
@@ -87,15 +76,7 @@ extension. Only if the extension is not installed will it start a light client i
 
 ### Ways to use it 
 
-When building an app with Substrate Connect, it will detect whether the user has the extension and
-use it, or create the WASM light client in-page for them. If developers want to generate a light
-client of their chain, all it takes is just one command to compile a library that contains
-everything needed to run a light client in the browser.
-
-Refer to these guides to get started with Substrate Connect:
-
-- [Installation](https://github.com/paritytech/substrate-connect#getting-started)
-- [Launching the browser extension](https://github.com/paritytech/substrate-connect/tree/master/projects/extension)
+Learn how to integrate Substrate Connect in your applications [here](https://paritytech.github.io/substrate-connect/).
 
 ## Next steps
 

v3/how-to-guides/01-basics/g-weights/index.mdx

@@ -15,7 +15,7 @@ difficulty: 1
     "This guide shows a basic procedure for configuring weights. There are more
     advanced methods that suit different use cases. For simple functions with fixed amounts
     of storage reads, this method works well. For any other use cases, see the section 
-    [on weights](../../weights/calculate-fees).
+    [on weights](/how-to-guides/v3/weights/calculate-fees).
     "
 />
 

v3/how-to-guides/02-pallet-design/a-add-contracts-pallet/index.mdx

@@ -47,7 +47,7 @@ difficulty: 1
 
 ### 1. Import the dependencies
 
-Refer to [this guide](../../basics/pallet-integration) to properly include Contracts in your runtime.
+Refer to [this guide](/how-to-guides/v3/basics/pallet-integration) to properly include Contracts in your runtime.
 
 This includes **updating `runtime/Cargo.toml` and `runtime/Cargo.toml`** with:
 

v3/how-to-guides/04-testing/a-basic-pallet-testing/index.mdx

@@ -2,7 +2,7 @@
 title: Setting up Tests for Your Pallet
 slug: /how-to-guides/v3/testing/basics
 keywords: basics, testing, runtime
-version: 3.0 
+version: 3.0
 section: how to guides
 category: testing
 difficulty: 1
@@ -16,16 +16,16 @@ difficulty: 1
     },
     {
       title: 'Use Cases',
-      description:
-        `Writing and running unit tests for a pallet.`,
+      description: `Writing and running unit tests for a pallet.`,
     },
     {
       title: 'Overview',
-      description:
-        `This guide steps through how to use \`mock.rs\` and \`test.rs\` as a basis for testing your pallet. We'll be
-		using the node template for the scaffolding of the \`mock.rs\` file and an arbitrary pallet — called \`pallet-testing\`
-		— to give this guide some context. This pallet will contain a single function called \`add_value\`, that takes an origin and
-		a \`u32\` and returns \`Ok(())\` if the value is less than or equal to a constant called \`MaxValue\` that we specify in the mock runtime.`,
+      description: `This guide steps through how to use \`mock.rs\` and \`test.rs\` as a basis for
+      testing your pallet. We'll be using the node template for the scaffolding of the \`mock.rs\`
+      file and an arbitrary pallet — called \`pallet-testing\` — to give this guide some
+      context. This pallet will contain a single function called \`add_value\`, that takes an origin
+      and a \`u32\` and returns \`Ok(())\` if the value is less than or equal to a constant called
+      \`MaxValue\` that we specify in the mock runtime.`,
     },
   ]}
 />
@@ -36,7 +36,7 @@ difficulty: 1
 
 Inside `pallet-testing/src`, the first thing we need to do is create two empty files: `mock.rs` and `tests.rs`.
 
-Paste in the contents from [`template/src/mock.rs`][template-node-mock-rs]. We'll use this as boilerpate
+Paste in the contents from [`template/src/mock.rs`][template-node-mock-rs]. We'll use this as boilerplate
 which we'll customize for our `pallet-testing` pallet.
 
 ### 2. Create a mock runtime to test your pallet
@@ -153,8 +153,8 @@ cargo test
 
 #### How-to guides
 
-- [Testing a transfer function](../transfer-function)
-- [Migration tests](../../storage-migrations/tests)
+- [Testing a transfer function](/how-to-guides/v3/testing/transfer-function)
+- [Migration tests](/how-to-guides/v3/storage-migrations/tests)
 
 #### Docs