no atomicdex in paths/names

Author: gcharang

STYLE_GUIDE.md

@@ -26,7 +26,7 @@ Be mindful of any feedback you receive from users, and let it guide you to impro
   - Where a request includes optional parameters which will result in different response structures, the file should contain a code block for each possible request variation, followed by a code block for the response of each example.
   - Below the request/response examples, include code blocks for each potential error response, along with details on what causes the error and how it might be resolved.
 - In some cases, it may be appropriate to group related methods together in a single `index.mdx` file. For example, the `index.mdx` file within the `task_init_trezor` folder contains documentation for all methods for initialisation and authentication with a Trezor hardware wallet.
-- Where common structures exist in the request or response of mulitple methods, these should be documented in the `index.mdx` file in the base folder for a section (e.g. [src/pages/atomicdex/api/v20/index.mdx](src/pages/atomicdex/api/v20/index.mdx)), and linked to from request/response parameter tables where required.
+- Where common structures exist in the request or response of mulitple methods, these should be documented in the `index.mdx` file in the base folder for a section (e.g. [src/pages/komodo-defi-framework/api/v20/index.mdx](src/pages/komodo-defi-framework/api/v20/index.mdx)), and linked to from request/response parameter tables where required.
 - Where a method or parameter is deprecated, this should be communicated in the method heading or request parameters table.
 - Separate sections of content with subheadings to make scanning and finding the information they need easier. Two line breaks should be used before and one line break after each subheading.
 
@@ -44,7 +44,7 @@ Be mindful of any feedback you receive from users, and let it guide you to impro
 - Use simple language: Where possible, avoid jargon or technical terms that may be unfamiliar to the reader. When unavoidable, provide a link to a definition or explanation of the term.
 - Proofread and test your content: Make sure to proofread your MDX file for errors and test any code snippets or examples to ensure they work as expected.
 - Be generous with hyperlinks: Link to relevant documentation or resources, whether to somewhere else within our internal docs or to a respected external source. This will provide additional context and help users better understand the content.
-- Use absolute links for internal docs: The `pages` folder is the root directory for internal docs. Use absolute links to reference other pages within the `pages` folder, for example: `[AtomicDEX API methods](/atomicdex/api/#sub-section-header)`. The url must end with a slash.
+- Use absolute links for internal docs: The `pages` folder is the root directory for internal docs. Use absolute links to reference other pages within the `pages` folder, for example: `[Komodo DeFi Framework API methods](/komodo-defi-framework/api/#sub-section-header)`. The url must end with a slash.
 - Use bullet points and numbered lists to break up long paragraphs to make the content more readable.
 
 ## Syntax
@@ -68,23 +68,23 @@ Be mindful of any feedback you receive from users, and let it guide you to impro
 
 For example:
 
-| Parameter | Type    | Description                                                                             |
-| --------- | ------- | --------------------------------------------------------------------------------------- |
-| coin      | string  | The name of the coin the user desires to activate.                                      |
-| fee       | object  | Optional. A standard [FeeInfo](/atomicdex/api/common_structures/#FeeInfo) object.                     |
-| amount    | float   | Required, unless `max` is `true`. The amount of balance to send.                        |
-| max       | boolean | Optional, defaults to `false`. Send whole balance.                                      |
-| memo      | string  | Optional, used for ZHTLC and Tendermint coins only. Attaches a memo to the transaction. |
+| Parameter | Type    | Description                                                                                   |
+| --------- | ------- | --------------------------------------------------------------------------------------------- |
+| coin      | string  | The name of the coin the user desires to activate.                                            |
+| fee       | object  | Optional. A standard [FeeInfo](/komodo-defi-framework/api/common_structures/#FeeInfo) object. |
+| amount    | float   | Required, unless `max` is `true`. The amount of balance to send.                              |
+| max       | boolean | Optional, defaults to `false`. Send whole balance.                                            |
+| memo      | string  | Optional, used for ZHTLC and Tendermint coins only. Attaches a memo to the transaction.       |
 
 ## Variables
 
-- For AtomicDEX-API methods, the userpass variable should always be `testpsw`
+- For Komodo DeFi Framework API methods, the userpass variable should always be `testpsw`
 
 ## Templates
 
 Use the linked templates below as a starting point for new documentation pages.
 
-- [AtomicDEX API methods](templates/atomicdex_method.mdx)
+- [Komodo DeFi Framework API methods](templates/komodefi_method.mdx)
 
 ## How to contribute
 
@@ -166,12 +166,13 @@ MDX supports standard markdown by default [CommonMark](https://commonmark.org/).
 
 The `CodeGroup` acts as a wrapper around code blocks. It allows us to have tabbed content (or not, if it's a single block) with properties such as **title, tags, labels and more**. An example would look something like this:
 
-```mdx
+````mdx
 <CodeGroup title="Code Sample" tag="post" label="/kmd/jwt/post" >
 
 ```ts
 // ...
 ```
+````
 
 ```python
 
@@ -204,7 +205,7 @@ And you'll still have it rendered correctly:
 
 ![Single code block UI](style-guide-images/single-code-block.png) -->
 
-It is important to **note that**, "**AtomicDEX methods**" should be wrapped with `CodeGroup` tags, using the **method name** as the **label value**, and the **tag value** set to **POST**, an additional **mm2MethodDecorate property** with the value **"true"**. This will generate code blocks for:
+It is important to **note that**, "**Komodo DeFi Framework methods**" should be wrapped with `CodeGroup` tags, using the **method name** as the **label value**, and the **tag value** set to **POST**, an additional **mm2MethodDecorate property** with the value **"true"**. This will generate code blocks for:
 
 - **JSON**: The pure request body.
 - **Python3**: Using the requests library.
@@ -218,7 +219,7 @@ You only need to include the `json` data, and the additional **mm2MethodDecorate
 
 A working code sample would look like this:
 
-```mdx
+````mdx
 <CodeGroup title="Generate Invoice" tag="POST" label="generate_invoice" mm2MethodDecorate="true">
 
 ```json
@@ -233,6 +234,7 @@ A working code sample would look like this:
   "id": 56
 }
 ```
+````
 
 </CodeGroup>
 ```
@@ -287,7 +289,7 @@ This renders a button with a specified text based on its state (expanded or coll
 
 You'll mostly use this for API, Commands, etc. Responses, which should be wrapped with the `CollapsibleSection` tags, for example:
 
-```mdx
+````mdx
 <CollapsibleSection expandedText='Hide Response' collapsedText='Show Response'>
   #### Response (ready, successful)
 
@@ -300,13 +302,13 @@ You'll mostly use this for API, Commands, etc. Responses, which should be wrappe
     ```
 
 </CollapsibleSection>
-```
+````
 
 The `CollapsibleSection` tags should also wrap all error responses (as a group), with the `expandedText` and `collapsedText` values set to '**Show Error Responses**' and '**Hide Error Responses' respectively**.
 
 A working code would look like this:
 
-```mdx
+````mdx
 <CollapsibleSection expandedText='Hide code' collapsedText='Show code'>
 
 ```json
@@ -318,6 +320,7 @@ A working code would look like this:
   "date": "2078-05-16"
 }
 ```
+````
 
 </CollapsibleSection>
 ```
@@ -330,13 +333,13 @@ Rendered as:
 
 Images should be added to the related subfolder within the `src/images` folder, and rendered using the `OptimizedImage` component. To render an image in the `src/image` folder, you'd have to import the image using the following syntax:
 
-`import atomicManiq from "@/public/images/atomic-dex-maniq.webp";`
+`import atomicManiq from "@/public/images/komodefi-maniq.webp";`
 
 Now you can render the image using the `OptimizedImage` component, for example:
 
 `<OptimizedImage title="Atomic Dex" src={atomicManiq} alt="atomic dex" classNaming="w-full" />`
 
-![Atomic Maniq](style-guide-images/atomic-maniq.png)
+![Atomic Maniq](style-guide-images/komodefi-maniq.png)
 
 <!-- [You can read more about the magic behind OptimizedImage](https://github.com/Niels-IO/next-image-export-optimizer#readme) -->
 

data-for-gpts/atomicdex-content.txt data-for-gpts/komodo-defi-framework-content.txt

@@ -2,9 +2,9 @@ export const title = "Get telegram notifications for your AtomicDEX LP";
 export const description =
   "This document describes how to become a Liquidity Provider for AtomicDEX with telegram notifications using docker.";
 
-import rickmorty from "@/public/images/atomicdex-api/tg-bot-rickmorty.png";
-import passphrase from "@/public/images/atomicdex-api/tg-bot-passphrase.png";
-import orderbook from "@/public/images/atomicdex-api/tg-RICKMORTYorderbook.png";
+import rickmorty from "@/public/images/api-images/tg-bot-rickmorty.png";
+import passphrase from "@/public/images/api-images/tg-bot-passphrase.png";
+import orderbook from "@/public/images/api-images/tg-RICKMORTYorderbook.png";
 
 # How To Become a Liquidity Provider for AtomicDEX with Telegram Notifications using Docker
 

src/images/atomicdex-api/tg-RICKMORTYorderbook.png src/images/api-images/tg-RICKMORTYorderbook.png

@@ -2,16 +2,16 @@ export const title = "AtomicDEX Metrics";
 export const description =
   "Monitor and analyze the performance and activity of your AtomicDEX API sessions with various metrics.";
 
-import prometheus1 from "@/public/images/atomic-dex-tutorials/prometheus1.png";
-import graphana1 from "@/public/images/atomic-dex-tutorials/graphana1.png";
-import graphana2 from "@/public/images/atomic-dex-tutorials/graphana2.png";
-import graphana3 from "@/public/images/atomic-dex-tutorials/graphana3.png";
-import graphana4 from "@/public/images/atomic-dex-tutorials/graphana4.png";
-import graphana5 from "@/public/images/atomic-dex-tutorials/graphana5.png";
-import graphana6 from "@/public/images/atomic-dex-tutorials/graphana6.png";
-import graphana7 from "@/public/images/atomic-dex-tutorials/graphana7.png";
-import graphana8 from "@/public/images/atomic-dex-tutorials/graphana8.png";
-import graphana9 from "@/public/images/atomic-dex-tutorials/graphana9.png";
+import prometheus1 from "@/public/images/komodo-defi-framework-tutorials/prometheus1.png";
+import graphana1 from "@/public/images/komodo-defi-framework-tutorials/graphana1.png";
+import graphana2 from "@/public/images/komodo-defi-framework-tutorials/graphana2.png";
+import graphana3 from "@/public/images/komodo-defi-framework-tutorials/graphana3.png";
+import graphana4 from "@/public/images/komodo-defi-framework-tutorials/graphana4.png";
+import graphana5 from "@/public/images/komodo-defi-framework-tutorials/graphana5.png";
+import graphana6 from "@/public/images/komodo-defi-framework-tutorials/graphana6.png";
+import graphana7 from "@/public/images/komodo-defi-framework-tutorials/graphana7.png";
+import graphana8 from "@/public/images/komodo-defi-framework-tutorials/graphana8.png";
+import graphana9 from "@/public/images/komodo-defi-framework-tutorials/graphana9.png";
 
 # AtomicDEX Metrics
 

src/images/atomicdex-api/tg-bot-passphrase.png src/images/api-images/tg-bot-passphrase.png

@@ -19,7 +19,7 @@ function readFileAndAddContentToFIle(filePath, contentHolder) {
     contentHolder.content += fileContent;
 }
 
-const pathsNames = [["", "all"], ["atomicdex", "atomicdex"], ["historical", "historical"], ["smart-chains", "smart-chains"], ["antara", "antara"], ["start-here", "start-here"], ["atomicdex/api", "komodefi-api/all-api"], ["atomicdex/api/legacy", "komodefi-api/legacy-api"], ["atomicdex/api/v20", "komodefi-api/v20-api"], ["atomicdex/api/v20-dev", "komodefi-api/v20-dev-api"]]
+const pathsNames = [["", "all"], ["komodo-defi-framework", "komodo-defi-framework"], ["historical", "historical"], ["smart-chains", "smart-chains"], ["antara", "antara"], ["start-here", "start-here"], ["komodo-defi-framework/api", "komodefi-api/all-api"], ["komodo-defi-framework/api/legacy", "komodefi-api/legacy-api"], ["komodo-defi-framework/api/v20", "komodefi-api/v20-api"], ["komodo-defi-framework/api/v20-dev", "komodefi-api/v20-dev-api"]]
 
 for (let index = 0; index < pathsNames.length; index++) {
     const element = pathsNames[index];