multiversx · bogdan-rosianu · Feb 3, 2026 · Feb 2, 2026 · Feb 2, 2026 · Feb 3, 2026
diff --git a/docs/bridge/architecture.md b/docs/bridge/architecture.md
@@ -1,6 +1,7 @@
 ---
 id: architecture
 title: Architecture
+description: "High-level architecture of the Ad‑Astra Bridge: core contracts on MultiversX and EVM chains, relayer quorum, and how cross‑chain transfers are coordinated."
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';

diff --git a/docs/bridge/axelar.md b/docs/bridge/axelar.md
@@ -1,3 +1,9 @@
+---
+id: axelar
+title: Axelar Amplifier Setup
+description: "Set up an Axelar Amplifier verifier for MultiversX: prerequisites, tofnd and ampd services, configuration, and verification steps."
+---
+
 # Axelar Amplifier setup for MultiversX
 
 ## Prerequisites

diff --git a/docs/bridge/token-types.md b/docs/bridge/token-types.md
@@ -1,6 +1,7 @@
 ---
 id: token-types
 title: Token Types
+description: "Bridge token configurations across MultiversX and EVM chains: mint/burn, lock/unlock, native vs non‑native, and their operational implications."
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';

diff --git a/docs/bridge/transfer-flows.md b/docs/bridge/transfer-flows.md
@@ -1,6 +1,7 @@
 ---
 id: transfer-flows
 title: Transfer Flows
+description: "Step‑by‑step token transfer flows for the MultiversX bridge: EVM↔MultiversX directions, smart‑contract call path, refund scenarios, and relayer processing."
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';

diff --git a/docs/bridge/whitelist-requirements.md b/docs/bridge/whitelist-requirements.md
@@ -1,6 +1,7 @@
 ---
 id: whitelist-requirements
 title: Whitelist Requirements
+description: "Whitelist requirements for the Ad‑Astra bridge: prerequisites, token branding, and assigning roles to wrapper or safe contracts."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/account-storage.md b/docs/developers/account-storage.md
@@ -1,6 +1,7 @@
 ---
 id: account-storage
 title: Account storage
+description: "Learn about account storage in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/best-practices/best-practices-basics.md b/docs/developers/best-practices/best-practices-basics.md
@@ -1,6 +1,7 @@
 ---
 id: best-practices-basics
 title: Basics
+description: "Learn about basics in MultiversX."
 ---
 
 [comment]: # (mx-context-auto)

diff --git a/docs/developers/best-practices/biguint-operations.md b/docs/developers/best-practices/biguint-operations.md
@@ -1,6 +1,7 @@
 ---
 id: biguint-operations
 title: BigUint Operations
+description: "Learn about biguint operations in MultiversX."
 ---
 
 [comment]: # (mx-context-auto)

diff --git a/docs/developers/best-practices/managed-decimal.md b/docs/developers/best-practices/managed-decimal.md
@@ -1,6 +1,7 @@
 ---
 id: managed-decimal
 title: Managed Decimal
+description: "Learn about managed decimal in MultiversX."
 ---
 
 [comment]: # (mx-context-auto)

diff --git a/docs/developers/best-practices/prepare-sc-supernova.md b/docs/developers/best-practices/prepare-sc-supernova.md
@@ -1,9 +1,9 @@
 ---
 id: prepare-sc-supernova
 title: Preparing SCs for Supernova
+description: "Learn about preparing scs for supernova in MultiversX."
 ---
 
-
 The MultiversX Supernova upgrade reduces block time from **6 seconds to 0.6 seconds**, enabling sub-second blocks. While this is a major improvement, it can impact existing smart contracts, especially those relying on assumptions about timestamp behavior.
 
 This guide explains how to prepare your contracts for Supernova safely.

diff --git a/docs/developers/best-practices/the-dynamic-allocation-problem.md b/docs/developers/best-practices/the-dynamic-allocation-problem.md
@@ -1,6 +1,7 @@
 ---
 id: the-dynamic-allocation-problem
 title: The dynamic allocation problem
+description: "Learn about the dynamic allocation problem in MultiversX."
 ---
 
 [comment]: # (mx-context-auto)

diff --git a/docs/developers/best-practices/time-types.md b/docs/developers/best-practices/time-types.md
@@ -1,9 +1,9 @@
 ---
 id: time-types
 title: Time-related Types
+description: "Learn about time-related types in MultiversX."
 ---
 
-
 The Supernova release introduces increased block frequency and encourages transitioning to millisecond timestamps, instead of seconds. To support this, the SpaceCraft SDK (starting with `v0.63.0`) provides strong type wrappers for time values to prevent common bugs.
 
 

diff --git a/docs/developers/built-in-functions.md b/docs/developers/built-in-functions.md
@@ -1,6 +1,7 @@
 ---
 id: built-in-functions
 title: Built-In Functions
+description: "Learn about built-in functions in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/constants.md b/docs/developers/constants.md
@@ -1,7 +1,9 @@
 ---
 id: constants
 title: Constants
+description: "Learn about constants in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 MultiversX uses some constants, which are specific to each chain (Mainnet, Testnet or Devnet). The updated values can be found at these sources:
 

diff --git a/docs/developers/contract-api-limits.md b/docs/developers/contract-api-limits.md
@@ -1,6 +1,7 @@
 ---
 id: contract-api-limits
 title: MultiversX Smart Contracts API limits
+description: "Learn about multiversx smart contracts api limits in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/creating-wallets.md b/docs/developers/creating-wallets.md
@@ -1,7 +1,9 @@
 ---
 id: creating-wallets
 title: Creating Wallets
+description: "Learn about creating wallets in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 How to create wallets using the CLI or programmatically

diff --git a/docs/developers/data/abi.md b/docs/developers/data/abi.md
@@ -1,6 +1,7 @@
 ---
 id: abi
 title: ABI
+description: "Learn about abi in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/data/code-metadata.md b/docs/developers/data/code-metadata.md
@@ -1,6 +1,7 @@
 ---
 id: code-metadata
 title: Code Metadata
+description: "Learn about code metadata in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/data/composite-values.md b/docs/developers/data/composite-values.md
@@ -1,7 +1,9 @@
 ---
 id: composite-values
 title: Composite Values
+description: "Learn about composite values in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 We often need to group simple values into more complex ones, without splitting them into [several arguments](/developers/data/multi-values).
@@ -24,6 +26,7 @@ Then, all nested encodings of the items, concatenated.
 **Examples**
 
 | Type             | Value                | Top-level encoding    | Nested encoding                | Explanation                                                                                                                               |
+|
 | ---------------- | -------------------- | --------------------- | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
 | `Vec<u8>`        | `vec![1, 2]`         | `0x0102`              | `0x00000002 0102`              | Length = `2`                                                                                                                              |
 | `Vec<u16>`       | `vec![1, 2]`         | `0x00010002`          | `0x00000002 00010002`          | Length = `2`                                                                                                                              |

diff --git a/docs/developers/data/custom-types.md b/docs/developers/data/custom-types.md
@@ -1,7 +1,9 @@
 ---
 id: custom-types
 title: Custom Types
+description: "Learn about custom types in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 We sometimes create new types that we want to serialize and deserialize directly when interacting with contracts. For `struct`s and `enum`s it is very easy to set them up, with barely any code.

diff --git a/docs/developers/data/defaults.md b/docs/developers/data/defaults.md
@@ -1,7 +1,9 @@
 ---
 id: defaults
 title: Defaults
+description: "Learn about defaults in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 Smart contracts occasionally need to interact with uninitialized data. Most notably, whenever a smart contract is deployed, its entire storage will be uninitialized.

diff --git a/docs/developers/data/multi-values.md b/docs/developers/data/multi-values.md
@@ -1,7 +1,9 @@
 ---
 id: multi-values
 title: Multi-Values
+description: "Learn about multi-values in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 ## Single values vs. multi-values
@@ -245,4 +247,3 @@ where
 ```
 
 To create a custom multi-value type, one needs to manually implement these two traits for the type. Unlike for single values, there is no [equivalent derive syntax](/developers/data/custom-types).
-
diff --git a/docs/developers/data/serialization-overview.md b/docs/developers/data/serialization-overview.md
@@ -1,7 +1,9 @@
 ---
 id: serialization-overview
 title: The MultiversX Serialization Format
+description: "Learn about the multiversx serialization format in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 In MultiversX, there is a specific serialization format for all data that interacts with a smart contract. The serialization format is central to any project because all values entering and exiting a contract are represented as byte arrays that need to be interpreted according to a consistent specification.
@@ -48,4 +50,3 @@ This guide is split into several sections:
 - [The code metadata flag](/developers/data/code-metadata)
 
 There is a special section about [uninitialized data and how defaults relate to serialization](/developers/data/defaults).
-
diff --git a/docs/developers/data/simple-values.md b/docs/developers/data/simple-values.md
@@ -1,7 +1,9 @@
 ---
 id: simple-values
 title: Simple Values
+description: "Learn about simple values in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 We will start by going through the basic types used in smart contracts:
@@ -33,6 +35,7 @@ Even when simulating smart contract execution on 64-bit systems, they must still
 **Examples**
 
 | Type    | Number                | Top-level encoding   | Nested encoding      |
+|
 | ------- | --------------------- | -------------------- | -------------------- |
 | `u8`    | `0`                   | `0x`                 | `0x00`               |
 | `u8`    | `1`                   | `0x01`               | `0x01`               |

diff --git a/docs/developers/developer-reference/sc-annotations.md b/docs/developers/developer-reference/sc-annotations.md
@@ -1,6 +1,7 @@
 ---
 id: sc-annotations
 title: Smart contract annotations
+description: "Learn about smart contract annotations in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/developer-reference/sc-api-functions.md b/docs/developers/developer-reference/sc-api-functions.md
@@ -1,6 +1,7 @@
 ---
 id: sc-api-functions
 title: Smart Contract API Functions
+description: "Learn about smart contract api functions in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/developer-reference/sc-messages.md b/docs/developers/developer-reference/sc-messages.md
@@ -1,6 +1,7 @@
 ---
 id: sc-messages
 title: Messages
+description: "Learn about messages in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/developer-reference/sc-modules.md b/docs/developers/developer-reference/sc-modules.md
@@ -1,6 +1,7 @@
 ---
 id: sc-modules
 title: Smart contract modules
+description: "Learn about smart contract modules in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/developer-reference/sc-payments.md b/docs/developers/developer-reference/sc-payments.md
@@ -1,6 +1,7 @@
 ---
 id: sc-payments
 title: Smart contract payments
+description: "Learn about smart contract payments in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/developer-reference/sc-random-numbers.md b/docs/developers/developer-reference/sc-random-numbers.md
@@ -1,6 +1,7 @@
 ---
 id: sc-random-numbers
 title: Random Numbers in Smart Contracts
+description: "Learn about random numbers in smart contracts in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/developer-reference/sc-to-sc-calls.md b/docs/developers/developer-reference/sc-to-sc-calls.md
@@ -1,7 +1,9 @@
 ---
 id: sc-to-sc-calls
 title: SC to SC Calls
+description: "Learn about sc to sc calls in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 This guide provides an overview of the different types of smart contract calls that originate from other smart contract calls.

diff --git a/docs/developers/developer-reference/storage-mappers.md b/docs/developers/developer-reference/storage-mappers.md
@@ -1,7 +1,9 @@
 ---
 id: storage-mappers
 title: Storage Mappers
+description: "Learn about storage mappers in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 The Rust framework provides various storage mappers you can use. Deciding which one to use for every situation is critical for performance. There will be a comparison section after each mapper is described.

diff --git a/docs/developers/developer-reference/upgrading-smart-contracts.md b/docs/developers/developer-reference/upgrading-smart-contracts.md
@@ -1,6 +1,7 @@
 ---
 id: upgrading-smart-contracts
 title: Upgrading smart contracts
+description: "Learn about upgrading smart contracts in MultiversX."
 ---
 
 [comment]: # (mx-abstract)

diff --git a/docs/developers/esdt-tokens.md b/docs/developers/esdt-tokens.md
@@ -1,6 +1,7 @@
 ---
 id: esdt-tokens
 title: ESDT tokens
+description: "Learn about esdt tokens in MultiversX."
 ---
 
 The Fungible Tokens documentation has been moved [here](/tokens/fungible-tokens).
diff --git a/docs/developers/event-logs/contract-call-events.md b/docs/developers/event-logs/contract-call-events.md
@@ -1,5 +1,5 @@
 ---
 id: contract-call-events
 title: Smart Contract Call Events
+description: "Learn about smart contract call events in MultiversX."
 ---
-
diff --git a/docs/developers/event-logs/contract-deploy-events.mdx b/docs/developers/event-logs/contract-deploy-events.mdx
@@ -1,6 +1,7 @@
 ---
 id: contract-deploy-events
 title: Smart Contract Deploy Events
+description: "Learn about smart contract deploy events in MultiversX."
 ---
 
 import Tabs from '@theme/Tabs';

diff --git a/docs/developers/event-logs/esdt-events.mdx b/docs/developers/event-logs/esdt-events.mdx
@@ -1,6 +1,7 @@
 ---
 id: esdt-events
 title: ESDT Operations Events
+description: "Learn about esdt operations events in MultiversX."
 ---
 
 import Tabs from '@theme/Tabs';

diff --git a/docs/developers/event-logs/execution-events.mdx b/docs/developers/event-logs/execution-events.mdx
@@ -1,6 +1,7 @@
 ---
 id: execution-events
 title: Execution Events
+description: "Learn about execution events in MultiversX."
 ---
 
 import Tabs from '@theme/Tabs';

diff --git a/docs/developers/event-logs/system-delegation-events.md b/docs/developers/event-logs/system-delegation-events.md
@@ -1,5 +1,5 @@
 ---
 id: system-delegation-events
 title: System Delegation Events
+description: "Learn about system delegation events in MultiversX."
 ---
-
diff --git a/docs/developers/gas-and-fees/egld-transfers.md b/docs/developers/gas-and-fees/egld-transfers.md
@@ -1,6 +1,7 @@
 ---
 id: egld-transfers
 title: EGLD transfers (move balance transactions)
+description: "Learn about egld transfers (move balance transactions) in MultiversX."
 ---
 
 [comment]: # (mx-context-auto)

diff --git a/docs/developers/gas-and-fees/overview.md b/docs/developers/gas-and-fees/overview.md
@@ -1,7 +1,9 @@
 ---
 id: overview
 title: Overview
+description: "Learn about overview in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 The processing cost of a MultiversX transaction is determined by its gas limit, the actual gas consumption, and the gas price per gas unit, leading to a processing fee in EGLD that may be subject to a gas refund in certain cases.
 

diff --git a/docs/developers/gas-and-fees/system-smart-contracts.md b/docs/developers/gas-and-fees/system-smart-contracts.md
@@ -1,6 +1,7 @@
 ---
 id: system-smart-contracts
 title: System Smart Contracts
+description: "Learn about system smart contracts in MultiversX."
 ---
 
 For transactions which call System Smart Contracts, the **actual gas cost** of processing contains the two previously mentioned cost components - and they are easily computable.

diff --git a/docs/developers/gas-and-fees/user-defined-smart-contracts.md b/docs/developers/gas-and-fees/user-defined-smart-contracts.md
@@ -1,7 +1,9 @@
 ---
 id: user-defined-smart-contracts
 title: User-defined Smart Contracts
+description: "Learn about user-defined smart contracts in MultiversX."
 ---
+
 [comment]: # (mx-abstract)
 
 For user-defined Smart Contract deployments and function calls, the **actual gas consumption** of processing contains both of the previously mentioned cost components - though, while the **value movement and data handling** component is easily computable (using the previously depicted formula), the **contract execution** component is hard to determine precisely _a priori_. Therefore, for this component we have to rely on _simulations_ and _estimations_.