Improve metadata docs organization and navigation

Author: davidsemakula

versioned_docs/version-v6/background/solidity-metamask-compat.md

@@ -23,29 +23,34 @@ slug: /background/solidity-metamask-compatibility
 With ink! v6, we have introduced an `abi` field in a custom `ink-lang` table 
 in the [`package.metadata` table][package-metadata] of a contract's manifest
 file (i.e. the `Cargo.toml` file) - [more details here][abi-declaration].
-It allows building your contract in Solidity ABI compatibility mode.
+It allows building your contract in Solidity ABI compatibility mode 
+when declared as follows:
 
 ```toml
 [package.metadata.ink-lang]
 abi = "sol"
 ```
 
-The implication of supporting Solidity ABI encoding is that all types used as constructor/message argument 
-and return types, and event argument types must define a mapping to an equivalent Solidity ABI type.
+The implication of supporting Solidity ABI encoding is that all types used as 
+constructor/message argument and return types, and event argument types must 
+define a mapping to an equivalent Solidity ABI type.
 
-This mapping is defined using the [`SolEncode`][sol-trait-encode] and [`SolDecode`][sol-trait-decode] traits, 
-which are analogs to [`scale::Encode` and `scale::Decode`][scale-codec] (but for Solidity ABI encoding/decoding).
+[package-metadata]: https://doc.rust-lang.org/cargo/reference/manifest.html#the-metadata-table
+[abi-declaration]: ../basics/abi/overview.md#declaring-the-abi
+
+## Rust/ink! to Solidity ABI type mapping
+
+This mapping is defined using the [`SolEncode`][sol-trait-encode] and 
+[`SolDecode`][sol-trait-decode] traits, which are analogs to 
+[`scale::Encode` and `scale::Decode`][scale-codec] 
+(but for Solidity ABI encoding/decoding).
 You won't be able to use Rust types for which no mapping to a Solidity type exists.
 An error about a missing trait implementation for this type will be thrown.
 
-[package-metadata]: https://doc.rust-lang.org/cargo/reference/manifest.html#the-metadata-table
-[abi-declaration]: ../basics/abi#declaring-the-abi
 [sol-trait-encode]: https://docs.rs/ink/latest/ink/trait.SolEncode.html
 [sol-trait-decode]: https://docs.rs/ink/latest/ink/trait.SolEncode.html
 [scale-codec]: https://docs.rs/parity-scale-codec/latest/parity_scale_codec
 
-## Rust/ink! to Solidity ABI type mapping
-
 ### Default/provided mappings
 
 [`SolEncode`][sol-trait-encode] and [`SolDecode`][sol-trait-decode] are implemented

versioned_docs/version-v6/basics/metadata/metadata.md renamed to versioned_docs/version-v6/basics/metadata/overview.md

@@ -1,5 +1,5 @@
 ---
-title: Metadata
+title: Overview
 hide_title: true
 slug: /basics/metadata
 ---
@@ -39,8 +39,8 @@ $ cargo contract build ---metadata <ink|solidity>
 ```
 
 Generating Solidity metadata is only possible if all constructor and message 
-arguments and return types can be mapped to equivalent Solidity ABI types 
-([more details here][sol-type-mapping]).
+argument and return types, and event argument types can be mapped to 
+equivalent Solidity ABI types ([more details here][sol-type-mapping]).
 
 [ethers-js]: https://docs.ethers.org/
 [sol-compat]: ../../background/solidity-metamask-compat.md

versioned_docs/version-v6/basics/selectors.md

@@ -29,7 +29,7 @@ Selectors in ink! are a language agnostic way of identifying constructors and me
 They are four-byte hexadecimal strings which look something like: `0x633aa551`.
 
 You can find the selector of an ink! constructor or message in your
-[contract metadata](./metadata/metadata.md) by looking for the `selector` field of the dispatchable
+[contract metadata](./metadata/overview.md) by looking for the `selector` field of the dispatchable
 you're interested in.
 
 Here is an example of how you can grab the message name and selector from your contract

versioned_sidebars/version-v6-sidebars.json

@@ -40,11 +40,11 @@
       {
         "type": "category",
         "label": "Metadata",
-        "items": ["basics/metadata/ink-format", "basics/metadata/solidity-format"],
-        "link": {
-          "type": "doc",
-          "id": "basics/metadata/metadata"
-        }
+        "items": [
+          "basics/metadata/overview",
+          "basics/metadata/ink-format",
+          "basics/metadata/solidity-format"
+        ]
       },
       "basics/xcm",
       "basics/contract-verification"