Merge pull request #747 from Dr-Electron/update-wiki-cli

Update wiki cli

documentation/.yarnrc.yml

@@ -1,3 +1 @@
 nodeLinker: node-modules
-
-yarnPath: .yarn/releases/yarn-3.2.0.cjs

documentation/docs/explanations/services/audit-trail-gateway/use-cases.md

@@ -28,7 +28,7 @@ infrastructure to alert all other systems connected to the same infrastructure.
 
 You could implement the following workflow:
 
-1. **Company X** has [registered and verified](../SSI-bridge/API-definition) its [Identity](../../identity.md) as
+1. **Company X** has [registered and verified](../SSI-bridge/API-definition.md) its [Identity](../../identity.md) as
    well as an identity for **employee Y** and **device (sensor) Z**.
 2. **Company A** has been registered and verified its identity as well as the identity of an **employee B** and **tool
    C**.

documentation/docs/how_tos/integration-services-sdk/introduction.mdx

@@ -20,7 +20,7 @@ import TabItem from "@theme/TabItem";
 The following sections will guide you in how to use the [Integration Services SDK](https://www.npmjs.com/package/iota-is-sdk).
 The Integration Services SDK makes it easy to manage decentralized identities and secure channels (Audit Trail).
 
-You should have a basic understanding of [decentralized identities](../../explanations/identity)
+You should have a basic understanding of [decentralized identities](../../explanations/identity.md)
 to get the most out of the following examples.
 
 ## Install
@@ -79,10 +79,10 @@ The Integration Services SDK has two different clients you can use:
 
 You can use `IdentityClient` to manage decentralized identities. This includes, but is not limited to:
 
-- [Creating an identity and verifiable credentials](create-identity-and-credentials)
-- [Updating users](update-users)
-- [Deleting users](delete-users)
-- [Adding Trusted Authorities](trusted-authorities)
+- [Creating an identity and verifiable credentials](create-identity-and-credentials.mdx)
+- [Updating users](update-users.mdx)
+- [Deleting users](delete-users.mdx)
+- [Adding Trusted Authorities](trusted-authorities.mdx)
 
 :::info
 You can test your implementation on our public API which is connected to the IOTA Mainnet.
@@ -95,9 +95,9 @@ You can test your implementation on our public API which is connected to the IOT
 
 You can use the `ChannelClient` to access Audit Trail features. These include, but are not limited to:
 
-- [Creating a channel](create-channel)
-- [Subscribing or approving access to a channel](authorize-to-channel#subscribe-to-a-channel)
-- [Reading and Writing on a channel](create-channel#write-on-a-channel)
+- [Creating a channel](create-channel.mdx)
+- [Subscribing or approving access to a channel](authorize-to-channel.mdx#subscribe-to-a-channel)
+- [Reading and Writing on a channel](create-channel.mdx#write-on-a-channel)
 
 <Tabs groupId={"programmingLanguage"}>
 <TabItem value="Java" label={'Java'}>

documentation/docs/how_tos/integration-services-sdk/run-how-tos.mdx

@@ -99,7 +99,7 @@ Please note the Java SDK assumes that an instance of the API, including its Mong
 1. Set Integration Service API's endpoint by setting the `API_KEY` and `API_URL` in `.env` file.
 2. Set the MongoDB endpoint for the API by setting `MONGO_URL`, `DB_NAME` and `SECRET_KEY` in `.env` file.
 
-If you started the API locally using [kubernetes](../../getting_started/installation/kubernetes/local_setup), you can write
+If you started the API locally using [kubernetes](../../getting_started/installation/kubernetes/local_setup.md), you can write
 the following `.env` file:
 
 ```bash

documentation/docs/how_tos/integration-services-sdk/search-channel-and-validate-data.mdx

@@ -15,7 +15,7 @@ import TabItem from "@theme/TabItem";
 
 # Search Channel and Validate Data
 
-The **example-7** script is similar to previous example ([Authorize Channel](authorize-to-channel)) that creates a
+The **example-7** script is similar to previous example ([Authorize Channel](authorize-to-channel.mdx)) that creates a
 channel as `Owner` and authorizes a `User` to write on it but:
 
 

documentation/docs/troubleshooting.md

@@ -9,7 +9,7 @@ keywords:
 ---
 # Troubleshooting
 
-The best source for sorting out problems is the IOTA [Discord](https://discord.gg/iota). Join the [#iota-cloud-tools](https://discord.com/channels/397872799483428865/910192737842790400) channel and ask your questions there. Additionally, the [FAQ](./faq) might have the answer to your problem. You can check if others are facing similar problems in the [issues](https://github.com/iotaledger/integration-services/issues) section in our repository.
+The best source for sorting out problems is the IOTA [Discord](https://discord.gg/iota). Join the [#iota-cloud-tools](https://discord.com/channels/397872799483428865/910192737842790400) channel and ask your questions there. Additionally, the [FAQ](./faq.md) might have the answer to your problem. You can check if others are facing similar problems in the [issues](https://github.com/iotaledger/integration-services/issues) section in our repository.
 
 Please make sure to have the latest version of the Integration Services installed and all other packages up to date.
 

documentation/docs/welcome.md

@@ -46,8 +46,8 @@ This documentation has eight sections.
     * [Self Sovereign Identity(SSI) Bridge API Reference](references/ssi_bridge_api_reference.md) 
     * [Audit Trail API Reference](references/audit_trail_gw_api_reference.md).
 5. [Troubleshooting](troubleshooting.md): Instructions on how to resolve any issues you may encounter while using the services.
-6. [FAQ](faq): Answers to the most common doubts.
-7. [Contribute](contribute): Find ways to help the project.
+6. [FAQ](faq.md): Answers to the most common doubts.
+7. [Contribute](contribute.md): Find ways to help the project.
 8. [Contact](contact.md): Get in touch with the Integration Services team.
 
 ## Join the Discussion

documentation/package.json

@@ -11,7 +11,7 @@
     "node": ">=16.14.0"
   },
   "devDependencies": {
-    "@iota-community/iota-wiki-cli": "iota-community/iota-wiki-cli#v2"
+    "@iota-wiki/cli": "latest"
   },
   "packageManager": "[email protected]"
 }