Dogemos docs

docs/.vuepress/config.js

@@ -42,15 +42,35 @@ module.exports = {
       auto: false,
       nav: [
         {
-          title: "API",
+          title: "Getting Started",
           children: [
             {
-              title: "Keplr API",
+              title: "Getting Started",
+              directory: true,
+              path: "/getting-started",
+            },
+          ],
+        },
+        {
+          title: "Keplr APIs",
+          children: [
+            {
+              title: "Keplr APIs",
               directory: true,
               path: "/api",
             },
           ],
         },
+        {
+          title: "Using Cosmos Singing Libraries",
+          children: [
+            {
+              title: "Using Cosmos Signing Libraries",
+              directory: true,
+              path: "/signing-lib",
+            },
+          ],
+        }
       ],
     },
   },

docs/README.md

@@ -11,19 +11,23 @@ order: 1
 
 ## Introduction
 
-Keplr is a non-custodial blockchain wallets for webpages that allow users to interact with blockchain applications.
+Keplr Wallet is an advanced, non-custodial web-based wallet tailored for the Cosmos ecosystem. Developers working with the Cosmos-based chains can utilize tools like cosmos-kit and CosmJS for seamless integration with the Keplr Wallet. Keplr stands out for its extensibility, security features, and intuitive interface, all of which enable fluid multi-chain operations for dApps desiring seamless multichain operations.
 
 ## Why Keplr?
 
-- Private keys are stored locally. This removes the friction and risk of webpages having to manage user private keys safely and securely.
-- As the user's private key is not managed by the website, users do not have to worry about the level of security of the website. The user only has to trust the security guarantees of Keplr, and freely interact with various web applications as they wish (and verify the contents of the transaction).
-- Keplr can easily connect to libraries such as CosmJS, simplifying the process of connecting webpages to blockchains.
+- **Frontend dApp Integration**: Keplr Wallet is expressly designed with frontend applications in mind, ensuring dApps can provide users with a seamless and intuitive blockchain interaction experience.
 
-## Sections
-[Integrate with Keplr](./api) describes how to integrate with Keplr in the webpage.  
+- **Enhanced Security & Extensibility**: Because the user's keys are stored locally, and only used to sign transactions requested by dApps, it allows dApps to provide a much more secure user path than storing private keys or mnemonics on the website.
 
-[Use with cosmjs](./api/cosmjs.md) describes how to use cosmjs with Keplr.
+- **User-Centric, multichain Design**: Keplr stands out with its user-focused interface for a multichain environment, simplifying asset management and transactions, which in turn enhances user adoption and trust in dApps integrated with it.
 
-[Use with secretjs](./api/secretjs.md) describes how to use secretjs with Keplr if you need to use secret-wasm feature.
-
-[Suggest chain](./api/suggest-chain.md) describes how to suggest the chain to Keplr if the chain is not supported natively in Keplr.
+Keplr's approach of allowing users to interact with multiple chains without setting an "active" chain contrasts with the traditional Ethereum wallet's model where users have to switch to a specific network to interact with it.
+
+1. **Seamless Cross-Chain Interactions**: 
+    - By permitting interactions across multiple chains simultaneously, users can effortlessly perform cross-chain activities without needing to constantly switch their active chain. This is especially pertinent in the Cosmos ecosystem, where IBC (Inter-Blockchain Communication) enables tokens to move between chains.
+
+2. **User Experience**: 
+    - The user doesn't have to be constantly aware of which chain they're interacting with, reducing cognitive load and improving the UX. It can be more intuitive, especially for newcomers who might not understand the concept of switching chains.
+
+3. **DApp Integration**: 
+    - For dApps that span multiple chains, integration can be smoother, as there's no need to prompt users to switch networks.