Update What is Msgport Section (#18)

* Update config

* Update homepage

* Add key features

* Add architecture

docs/index.md

@@ -1,26 +1,17 @@
-# What is Msgport
+# What is Msgport?
 
-In the evolving landscape of blockchain technology, the need for interoperability and seamless communication between diverse blockchains has never been more critical. Msgport, stands at the forefront of this challenge, offering a robust solution for cross-chain messaging. With a focus on facilitating effortless asset and information transfer across blockchains, Msgport is revolutionizing the way applications communicate in web 3.0.
+Msgport gets its name from hubs of connectivity, such as airports, seaports, and spaceports, because it serves as a gateway for messages between different blockchain systems. By acting as a crucial hub, Msgport enables the connection of various blockchain systems with minimal changes to their underlying architecture. Specifically, Msgport defines a set of [essential interfaces](./build/interfaces.md) for cross-chain communication, including sending, receiving, and verifying messages. This is similar to a superclass or abstract class in programming, which outlines a template for functionality. Concrete implementations of Msgport, known as [messaging protocols](./learn/messaging-protocols/overview.md), may vary to accommodate the unique designs of different underlying blockchains. However, as long as an implementation adheres to the Msgport interfaces, it can be used interchangeably, making it easier for developers to create cross-chain decentralized applications.
 
-## Core Components and Innovations
+## Key features
 
-The Msgport encompasses a collection of smart contracts that outline standardized interfaces for facilitating a cross-chain messaging protocol. 
+### Flexible and extensible
+
+The [core interfaces](./build/interfaces.md) of Msgport are intentionally created with a broad and adaptable design to accommodate diverse implementations. With flexibility as a key principle, our roadmap includes various messaging protocols such as [ORMP](./learn/messaging-protocols/ormp.md), [LCMP](./learn/messaging-protocols/lcmp.md), and [XCMP](./learn/messaging-protocols/xcmp.md). While each protocol implements the foundational interfaces of Msgport, they leverage distinct cross-chain technologies to achieve interoperability. This design strategy ensures that the Msgport framework can support a wide array of cross-chain communication methods, allowing for robust and flexible blockchain messaging solutions.
 
-At the heart of this system is the core interface, [IMessagePort](./build/interfaces.md#imessageport), which is designed with flexibility to support various implementations. 
+### Developers friendly
 
-![msgport-overview-1](./images/msgport-overview-1.png)
+For application developers looking to enhance their dApps with cross-chain functionality, mastering the [core interfaces](./build/interfaces.md) for sending and receiving messages is essential. There's no need for in-depth knowledge of the underlying messaging infrastructure. Additionally, we offer various tools such as a message scanner and a cross-chain message fee calculator to streamline cross-chain activities.
 
-Highlighting Msgport's versatility are its flagship integrations:
+### Decentralized and Open Source
 
-  - [ORMP](./learn/messaging-protocols/ormp.md): Oracle Relayer Messaging Protocol leverages chain-independent components, such as oracles and DApp-preferred relayers, to verify cross-chain messages. This approach integrates diverse verification mechanisms, ensuring robust and flexible cross-chain communication.
-  - [LCMP](./learn/messaging-protocols/lcmp.md): Light Client Cross-Chain Messaging Protocol employs blockchain consensus mechanisms and light clients as decentralized verifiers. This ensures the integrity and accuracy of message verification across different blockchains, fostering a secure and trustless environment for message passing.
-  - [XCMP](./learn/messaging-protocols/xcmp.md): Developed by Polkadot, Cross-Consensus Message Passing facilitates seamless messaging between various parachains within the Polkadot network. Messages are exchanged directly by parachains, relayed and verified by the relay chain, exemplifying efficient inter-parachain communication and interoperability.
-
-These implementations underscore Msgport's commitment to fostering interoperability, ensuring that assets and information can navigate the complex landscape of blockchain technology smoothly.
-
-## Integration and Understanding
-For developers and applications eager to leverage the power of Msgport, the journey begins with the [Msgport Workflow Documentation](./build/workflow.md) and a series of comprehensive [Tutorials](./build/tutorial/remix-demo.md). These resources are meticulously crafted to demystify the complexities of Msgport, offering a clear path to integration. From foundational knowledge to step-by-step guides, developers can expect a seamless onboarding experience, enabling them to harness the full potential of cross-chain messaging.
-
-## Embracing the Future
-
-As the digital world continues to evolve, Msgport stands as a beacon of innovation, guiding the way towards a more interconnected and efficient blockchain ecosystem. Whether you are looking to bridge assets or enhance the capabilities of your blockchain application, Msgport offers the tools and support needed to transcend traditional boundaries and embrace the future of cross-chain communication.
+All projects related to Msgport are open-source and governed by the members of RingDAO. Unlike many cross-chain solutions that utilize centralized trust models with histories of vulnerabilities to exploits and hacks, Msgport offers a more secure alternative, reducing the need for concern regarding such issues.

docs/learn/architecture.md

@@ -0,0 +1,17 @@
+# Architecture
+
+The current Web3 landscape is characterized by a multitude of innovative blockchain solutions, each boasting unique features and fee models based on their respective architectures. This proliferation of solutions has significantly increased the difficulty of designing a universal cross-chain messaging protocol that can seamlessly integrate with all existing blockchain systems.
+
+As a result, applications seeking to provide services across multiple chains must often customize their approach for each chain, increasing development complexity and costs. To mitigate this issue, Msgport offers a standardized interface for cross-chain messaging, comprising a collection of smart contracts outlining standardized interfaces for facilitating a cross-chain messaging protocol.
+
+![architecture](../images/architecture.png)
+
+At the heart of this system is the core interface, [IMessagePort](./build/interfaces.md#imessageport), designed with flexibility to support various implementations, known as messaging protocols. Applications integrated with Msgport can quickly switch between different messaging protocols, leveraging the benefits of each, such as lower cross-chain message fees or enhanced security.
+
+Highlighting the three messaging protocols:
+
+  - [ORMP](./learn/messaging-protocols/ormp.md): Oracle Relayer Messaging Protocol leverages chain-independent components, such as oracles and DApp-preferred relayers, to verify cross-chain messages. This approach integrates diverse verification mechanisms, ensuring robust and flexible cross-chain communication.
+  - [LCMP](./learn/messaging-protocols/lcmp.md): Light Client Cross-Chain Messaging Protocol employs blockchain consensus mechanisms and light clients as decentralized verifiers. This ensures the integrity and accuracy of message verification across different blockchains, fostering a secure and trustless environment for message passing.
+  - [XCMP](./learn/messaging-protocols/xcmp.md): Developed by Polkadot, Cross-Consensus Message Passing facilitates seamless messaging between various parachains within the Polkadot network. Messages are exchanged directly by parachains, relayed and verified by the relay chain, exemplifying efficient inter-parachain communication and interoperability.
+
+These implementations underscore Msgport's commitment to fostering interoperability, ensuring that assets and information can navigate the complex landscape of blockchain technology smoothly.

mkdocs.yml

@@ -19,10 +19,11 @@ theme:
     - content.code.copy
     - content.tooltips
     - navigation.footer
-    - navigation.indexes
     - navigation.sections
     - navigation.tabs
     - navigation.top
+    - navigation.path
+    - navigation.expand
     - navigation.tracking
     - search.highlight
     - search.share
@@ -136,9 +137,10 @@ plugins:
         "build/use-cases/xaccount.md": "learn/use-cases/xaccount.md"
         "build/use-cases/xdao.md": "learn/use-cases/xdao.md"
 nav:
-  - What is Msgport:
-      - What is Msgport: "index.md"
-      - Supported Protocols:
+  - Learn:
+      - What is Msgport?: "index.md"
+      - Architecture: "learn/architecture.md"
+      - Messaging Protocols:
           - Overview: "learn/messaging-protocols/overview.md"
           - ORMP Protocol: "learn/messaging-protocols/ormp.md"
           - XCMP Protocol: "learn/messaging-protocols/xcmp.md"
@@ -158,6 +160,7 @@ nav:
       - Message Scan: "build/scan.md"
       - API Documentation: "build/api.md"
       - Tutorial:
-        - Send Cross-Chain Messages Using Remix: "build/tutorial/remix-demo.md"
-        - Send Cross-Chain Messages Using Script: "build/tutorial/script-demo.md"
+        - Sending Messages:        
+          - Using Remix: "build/tutorial/remix-demo.md"
+          - Using Script: "build/tutorial/script-demo.md"
   - Community: "community/ringdao.md"