diff --git a/docs/connector/_category_.json b/docs/connector/_category_.json
index de7ae2dffa1..56820cdd742 100644
--- a/docs/connector/_category_.json
+++ b/docs/connector/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Connectors",
- "position": 5
+ "position": 6
}
diff --git a/docs/connector/overview.mdx b/docs/connector/overview.mdx
index ac262cd9d4c..f284bb1105e 100644
--- a/docs/connector/overview.mdx
+++ b/docs/connector/overview.mdx
@@ -4,7 +4,4 @@ sidebar_position: 1
# Connectors
-Introduction
-S3
-Jackal
-Create your own
+Work in Progress ⚙️
diff --git a/docs/create-ecosystem/_category_.json b/docs/create-ecosystem/_category_.json
index a4f6e885904..050fd738b6a 100644
--- a/docs/create-ecosystem/_category_.json
+++ b/docs/create-ecosystem/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Create an Ecosystem",
- "position": 2
+ "position": 3
}
diff --git a/docs/create-ecosystem/overview.mdx b/docs/create-ecosystem/overview.mdx
index de79619980b..1e5f1f71128 100644
--- a/docs/create-ecosystem/overview.mdx
+++ b/docs/create-ecosystem/overview.mdx
@@ -4,4 +4,4 @@ sidebar_position: 1
# Create an Ecosystem
-Helloworld
+Work in Progress ⚙️
diff --git a/docs/getting-started/_category_.json b/docs/getting-started/_category_.json
new file mode 100644
index 00000000000..3562d433d76
--- /dev/null
+++ b/docs/getting-started/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Getting Started",
+ "position": 1
+}
diff --git a/docs/getting-started/introduction/_category_.json b/docs/getting-started/introduction/_category_.json
new file mode 100644
index 00000000000..cb8cd30bf88
--- /dev/null
+++ b/docs/getting-started/introduction/_category_.json
@@ -0,0 +1,5 @@
+{
+ "position": 2,
+ "label": "Intro to Axone",
+ "collapsible": true
+}
diff --git a/docs/introduction/ai-factory.mdx b/docs/getting-started/introduction/ai-factory.mdx
similarity index 99%
rename from docs/introduction/ai-factory.mdx
rename to docs/getting-started/introduction/ai-factory.mdx
index 12b12287bf3..f0b081ea6d1 100644
--- a/docs/introduction/ai-factory.mdx
+++ b/docs/getting-started/introduction/ai-factory.mdx
@@ -2,9 +2,6 @@
sidebar_position: 9
---
-import Quiz from 'react-quiz-component'
-import * as quiz from './ai-factory-quiz.json'
-
# AI Factory: A Use Case Unveiling
The rapid development of AI models redefines the boundaries of what is possible in many fields. The ability to use existing open-source models or create one's own AI models to meet specific needs is becoming accessible to everyone.
@@ -213,5 +210,3 @@ It focuses on enhancing the transparency of AI models by providing explanations
### Dimensionality Reduction Tools Zone
This Zone can facilitate the management of complex datasets by reducing their dimensionality. Contributors collaborate to apply reduction techniques while preserving essential information.
-
-
diff --git a/docs/introduction/protocol-concepts.md b/docs/getting-started/introduction/protocol-concepts.md
similarity index 98%
rename from docs/introduction/protocol-concepts.md
rename to docs/getting-started/introduction/protocol-concepts.md
index cf1aedd9e8d..c14832fb4f1 100644
--- a/docs/introduction/protocol-concepts.md
+++ b/docs/getting-started/introduction/protocol-concepts.md
@@ -45,8 +45,8 @@ As a decentralized orchestration layer for off-chain resources, Axone must ensur
- Interpret the rules to ensure the law enforcement
- Execute workflow and orchestrate the resources according to the rules
-In [Rules](https://docs.okp4.network/introduction/rules) section, we describe how the protocol allows you to **define and enforce any customized rules**.
-In [Workflows](https://docs.okp4.network/introduction/workflows) section, we describe how the protocol **orchestrates the resources according to the rules**.
+In [Rules](https://docs.okp4.network/getting-started/introduction/rules) section, we describe how the protocol allows you to **define and enforce any customized rules**.
+In [Workflows](https://docs.okp4.network/getting-started/introduction/workflows) section, we describe how the protocol **orchestrates the resources according to the rules**.
Here, we'll concentrate on how Axone enables its functionalities **in the decentralized way**.
diff --git a/docs/introduction/resources.mdx b/docs/getting-started/introduction/resources.mdx
similarity index 100%
rename from docs/introduction/resources.mdx
rename to docs/getting-started/introduction/resources.mdx
diff --git a/docs/introduction/rules.mdx b/docs/getting-started/introduction/rules.mdx
similarity index 100%
rename from docs/introduction/rules.mdx
rename to docs/getting-started/introduction/rules.mdx
diff --git a/docs/introduction/who-is-it-for.mdx b/docs/getting-started/introduction/who-is-it-for.mdx
similarity index 99%
rename from docs/introduction/who-is-it-for.mdx
rename to docs/getting-started/introduction/who-is-it-for.mdx
index f017074a63f..d27590a8460 100644
--- a/docs/introduction/who-is-it-for.mdx
+++ b/docs/getting-started/introduction/who-is-it-for.mdx
@@ -2,9 +2,6 @@
sidebar_position: 8
---
-import Quiz from 'react-quiz-component'
-import * as quiz from './who-is-it-for-quiz.json'
-
# Who is it for?
Axone is often described as a protocol that enables sharing Anything as a Service under any Conditions. To illustrate the infinite possibilities opened up by the protocol, this section provides further examples of the intended audience for the protocol.
@@ -173,5 +170,3 @@ In exploring the various actors within the protocol, we observe that most are bo
The nuanced nature of Axone blurs the traditional boundaries between these roles. Entities seamlessly transition between these roles based on their context and specific objectives. As a protocol, Axone directly addresses builders and exploiters of digital resources, fostering a collaborative environment where each participant, specialized and competent in their domain, adds value to creating new knowledge.
It is not uncommon to witness entities functioning as providers in specific scenarios while assuming the role of consumers in others. This fluidity underscores the adaptability and versatility inherent in Axone. As we navigate this decentralized digital landscape, Axone emerges as a facilitator, providing a framework for a myriad of actors to engage, collaborate, and collectively contribute to generating innovative knowledge.
-
-
diff --git a/docs/introduction/workflows.mdx b/docs/getting-started/introduction/workflows.mdx
similarity index 100%
rename from docs/introduction/workflows.mdx
rename to docs/getting-started/introduction/workflows.mdx
diff --git a/docs/getting-started/overview.mdx b/docs/getting-started/overview.mdx
new file mode 100644
index 00000000000..2893ef6ee94
--- /dev/null
+++ b/docs/getting-started/overview.mdx
@@ -0,0 +1,40 @@
+---
+sidebar_position: 1
+---
+
+# Overview
+
+Explore the power of Axone by interacting with the protocol!
+
+:::info
+
+If you have never interacted with a Cosmos SDK world, you might want to check out these [guides](https://docs.okp4.network/tutorials/keplr-1) first to get familiar with Keplr and CLI before getting started with Axone.
+
+:::
+
+
diff --git a/docs/getting-started/quickstart-guides/_category_.json b/docs/getting-started/quickstart-guides/_category_.json
new file mode 100644
index 00000000000..c48c6869a51
--- /dev/null
+++ b/docs/getting-started/quickstart-guides/_category_.json
@@ -0,0 +1,5 @@
+{
+ "position": 3,
+ "label": "Quickstart Guide",
+ "collapsible": true
+}
diff --git a/docs/technical-documentation/technical-implementation/describe-resource.mdx b/docs/getting-started/quickstart-guides/describe-resource.mdx
similarity index 97%
rename from docs/technical-documentation/technical-implementation/describe-resource.mdx
rename to docs/getting-started/quickstart-guides/describe-resource.mdx
index 782ad813f98..eb21be16630 100644
--- a/docs/technical-documentation/technical-implementation/describe-resource.mdx
+++ b/docs/getting-started/quickstart-guides/describe-resource.mdx
@@ -4,9 +4,7 @@ sidebar_position: 3
# Describe a resource
-Now that you know what a DID and a Verifiable Credential are, and what they mean for the Axone protocol, let's put them into practice!
-
-You're a digital resource provider and you want to share a dataset or a service. First, you need to describe your resource and register it in the Dataverse (i.e. in the Axone protocol).
+Welcome to the Axone Quickstart Guide. In this guide, you'll learn how to interact with the Axone Protocol and harness its powerful features to manage and share AI resources effectively. We'll start by describing a resource—a fundamental step that allows you to define and register any digital asset within the Axone ecosystem. This process sets the foundation for resource governance, collaboration, and seamless integration into AI workflows. Let's begin by understanding how to describe a resource accurately to unlock the full potential of Axone Protocol.
Here are the 4 steps involved:
diff --git a/docs/technical-documentation/technical-implementation/describe-zone.mdx b/docs/getting-started/quickstart-guides/describe-zone.mdx
similarity index 100%
rename from docs/technical-documentation/technical-implementation/describe-zone.mdx
rename to docs/getting-started/quickstart-guides/describe-zone.mdx
diff --git a/docs/technical-documentation/technical-implementation/resource-governance.mdx b/docs/getting-started/quickstart-guides/resource-governance.mdx
similarity index 100%
rename from docs/technical-documentation/technical-implementation/resource-governance.mdx
rename to docs/getting-started/quickstart-guides/resource-governance.mdx
diff --git a/docs/technical-documentation/technical-implementation/zone-governance.mdx b/docs/getting-started/quickstart-guides/zone-governance.mdx
similarity index 100%
rename from docs/technical-documentation/technical-implementation/zone-governance.mdx
rename to docs/getting-started/quickstart-guides/zone-governance.mdx
diff --git a/docs/index.mdx b/docs/index.mdx
index be668375eba..92830dc6ef1 100644
--- a/docs/index.mdx
+++ b/docs/index.mdx
@@ -5,16 +5,15 @@ sidebar_position: 0
hide_table_of_contents: true
---
-# About Axone
+# Axone
-Axone is a public [dPoS](https://en.bitcoinwiki.org/wiki/DPoS) layer 1 specifically designed for connecting, sharing, and monetizing any resources in the AI stack.
-It is an open network dedicated to collaborative AI workflow management that is universally compatible with any data, model, or infrastructure.
+## Driving Collaborative AI Innovation Together
-Axone is built on the [Cosmos SDK](https://v1.cosmos.network/sdk) & [CometBFT](https://cometbft.com) consensus, and allows companies & individuals to define on-chain rules, share any off-chain resources & create a new generation of applications on top of them. With Axone, share anything digital, on your own terms. In a nutshell, Axone is:
+Axone Protocol is a **decentralized orchestration protocol** designed to transform the AI landscape. By seamlessly connecting and sharing digital resources within the AI stack, Axone empowers AI startups, tech companies, and developers to innovate and create new AI applications.
-- a solution for the trust issue related to digital resource sharing
-- sovereign, scalable, multichain & fully customizable (built on Cosmos, leveraging IBC, ICQ & ICA)
-- unlocking real-world value creation, bridging the gap between web2 & web3.
+Axone enables collaborative AI workflow orchestration, compatible with **any data, model, or infrastructure**. Share data, algorithms, storage, compute, and APIs on-chain or off-chain, **under any conditions**. Customize access rights and sharing processes to meet your needs.
+
+At its core, Axone is a decentralized layer fostering collaboration and innovation. Create custom environments with tailored rules, tokens, and governance mechanisms to incentivize resource sharing. Explore Axone to discover how you can drive AI advancements on your own terms. Dive into our documentation to get started.
@@ -28,18 +27,10 @@ Axone is built on the [Cosmos SDK](https://v1.cosmos.network/sdk) & [CometBFT](h
Get started as a Data Scientist by sharing your resources.
+
Get started with Axone!
diff --git a/docs/introduction/_category_.json b/docs/introduction/_category_.json
deleted file mode 100644
index fa1c06ac804..00000000000
--- a/docs/introduction/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Introduction",
- "position": 1
-}
diff --git a/docs/introduction/ai-factory-quiz.json b/docs/introduction/ai-factory-quiz.json
deleted file mode 100644
index 397415801bc..00000000000
--- a/docs/introduction/ai-factory-quiz.json
+++ /dev/null
@@ -1,98 +0,0 @@
-{
- "quizTitle": "Test your knowledge!",
- "nrOfQuestions": "6",
- "questions": [
- {
- "question": "What is the AI Factory?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "A zone for training and governing an AI model.",
- "A decentralized framework for creating a specialized zone in the training and governance of an AI model.",
- "A zone for making one's model available for inferences.",
- "A decentralized framework for creating a specialized zone in a marketplace of pre-trained models."
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What is the primary mission of Axone in relation to the AI Factory? ?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "To individually reconstruct each infrastructure component for AI Factory development.",
- "To create a centralized marketplace for AI-related services.",
- "To provide a decentralized orchestration layer for Training-as-a-service.",
- "To develop cutting-edge technologies for AI model training."
- ],
- "correctAnswer": "3",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "How does Axone contribute to Resilient Service-Level Agreements?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "By simplifying data provenance and sacrificing privacy considerations.",
- "By allowing flexibility in consent rules to accommodate various privacy preferences.",
- "By prioritizing computation speed over integrity to meet SLA requirements.",
- "By ensuring the transparency of the workflow and resisting censorship."
-
- ],
- "correctAnswer": "4",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "Which of these statements is false?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "The creation of a Zone via the AI Factory requires the creation of a DAO.",
- "The AI Factory allows the creation of a zone with an autocratic governance.",
- "The AI Factory allows the creation of a zone with a democratic governance.",
- "The creation of a Zone via the AI Factory necessarily needs a governance mechanism."
- ],
- "correctAnswer": "1",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "Why does Axone aim to create a Privacy-Preserving Data Labeling Service?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "To decentralize data labeling services within the Dataverse.",
- "To enable contributors to perform computations on encrypted data.",
- "To enhance privacy during collaborative model development.",
- "Axone does not intend to create specific zones but provides infrastructure and framework for such services to be implemented."
- ],
- "correctAnswer": "4",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "I didn't fully understand Beyond the AI Factory part, is it a big deal?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "Yes, it is. Axone must be at the forefront of AI technology to offer suitable zones and services for its development.",
- "Not really. As a decentralized orchestrator layer, Axone only needs to ensure communication between these zones and should not focus on research in these domains.",
- "Yes, it is. Even though Axone doesn't have to develop all these projects, it is important to understand them well to offer the most suitable governance and business templates.",
- "Not really. Axone must ensure to offer a decentralized, auditable, and modular infrastructure for communication, coordination between digital resources within Zones, while ensuring that the rules and conditions of each are respected."
- ],
- "correctAnswer": "4",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- }
- ]
- }
-
\ No newline at end of file
diff --git a/docs/introduction/installation.md b/docs/introduction/installation.md
deleted file mode 100644
index 63370c1e4de..00000000000
--- a/docs/introduction/installation.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 10
----
-
-# Installation
-
-Installation
-
-Prerequisites
-
-Helloworld
diff --git a/docs/introduction/who-is-it-for-quiz.json b/docs/introduction/who-is-it-for-quiz.json
deleted file mode 100644
index 1886b453708..00000000000
--- a/docs/introduction/who-is-it-for-quiz.json
+++ /dev/null
@@ -1,83 +0,0 @@
-{
- "quizTitle": "Test your knowledge!",
- "nrOfQuestions": "5",
- "questions": [
- {
- "question": "For Data Providers, which statement is correct?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "The provided data must be necessarily anonymized.",
- "Data must be made available in a specific format.",
- "Once access conditions are defined by the provider, they cannot be modified.",
- "The provider must initiate an on-chain transaction to input metadata and rules."
- ],
- "correctAnswer": "4",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What kind of models can AI builders share?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "Foundation models.",
- "Any kind of model.",
- "Only models governed by a DAO.",
- "Only open-source models."
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What is the main reason for Service Providers to lock tokens on services?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "To guarantee the integrity of services.",
- "To give free access to services.",
- "To offer a reduction of fees.",
- "To permit flexibility of services."
- ],
- "correctAnswer": "1",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "Which of these statements is true?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "In the execution of a workflow, there can be multiple consumers and providers.",
- "The only consumer is the entity that initiates the workflow with an on-chain transaction.",
- "In the execution of a workflow, providers must perform an on-chain transaction.",
- "All entities that use or will use the output of the workflow execution are considered consumers."
-
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "Which of these statements is false?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "Within Axone, the same entity can be both a consumer and a provider.",
- "If a consumer uses a Third-party identity service like Sign-in with Google, they will not have their own ID when interacting with the protocol.",
- "If a company uses Axone to build its XaaS, the company's clients will not necessarily interact with the protocol as consumers.",
- "Within the same workflow, the same entity can be both a consumer and a provider."
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- }
- ]
- }
-
\ No newline at end of file
diff --git a/docs/nft-tutorial/_category_.json b/docs/nft-tutorial/_category_.json
deleted file mode 100644
index c9639ad8002..00000000000
--- a/docs/nft-tutorial/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
- "label": "NFT tutorial",
- "className": "hide",
- "position": 10
-}
\ No newline at end of file
diff --git a/docs/nft-tutorial/en.md b/docs/nft-tutorial/en.md
deleted file mode 100644
index b2a1c2d3018..00000000000
--- a/docs/nft-tutorial/en.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-sidebar_position: 1
----
-
-# OKP4 NFT tutorial
-
-> [Version française](./fr.md)
-
-## Prerequisites
-
-To thank you for investing in the KNOW token of the OKP4 protocol, the team has decided to offer you a unique [NFT](https://en.wikipedia.org/wiki/Non-fungible_token)!
-
-This NFT is part of a collection of 76 NFTs that represent the first SAFT edition. It is a proof of involvement in the project at its beginning. It has no legal value. It can be exchanged, and you are free to do what you want with it. It may or may not entitle you to future benefits.
-
-This NFT is held in a personal [Stargaze](https://www.stargaze.zone/) address we created specifically for you. This address is controlled by a private key that takes the form of a [mnemonic](https://en.bitcoin.it/wiki/Seed_phrase).
-
-However, it is important to transfer it to another address! There is no guarantee that we will get rid of the private key after sharing it with you. So you need to transfer the NFT to a wallet that you created yourself.
-
-This tutorial will help you find your NFT and transfer it to your personal wallet.
-
-## Get Keplr
-
-Keplr is a wallet, a small application that allows you to create, protect and control private keys for addresses on the blockchains of the Cosmos ecosystem.
-
-Keplr allows you to store your key locally on your computer or to use a physical wallet like Ledger or Trezor.
-
-If it's not already done you should get Keplr: [https://www.keplr.app/](https://www.keplr.app/)
-You can use either of the following solutions:
-
-- [Keplr Extension](https://chrome.google.com/webstore/detail/keplr/dmkamcknogkgcdfhhbddcghachkejeap) for [Google chrome](https://www.google.com/chrome/index.html) or [Brave](https://brave.com/) browsers.
-- [Keplr wallet for Iphone](https://apps.apple.com/us/app/keplr-wallet)
-- [Keplr wallet for Android](https://play.google.com/store/apps/details?id=com.chainapsis.keplr)
-
-## Go see your NFT
-
-Connect with the address provided by OKP4
-
-- Decrypt the file received by email using the password accessible through the temporary link provided in the same email
-- Click on the Keplr icon on your browser:
- 
-- You should see the following screen:
- 
-- Click on `Import existing account`
-- Enter your 24 words mnemonic (copy/paste of all words at once is possible)
-- Enter an account name like `temporary okp4 wallet`
-- Choose a password for Keplr
-
-Now you can click on the Keplr extension icon
-
-- Select the `Stargaze` blockchain
-
-
-The Stargaze blockchain is dedicated to NFTs and is part of the Cosmos ecosystem.
-
-You should see something like this:
-
-
-
-You can then go to [https://app.stargaze.zone](https://app.stargaze.zone)
-
-- Click on `Connect Wallet`
-- Once connected click on the user icon: 
-
-You should be redirected to your NFT:
-
-
-
-## Get a wallet of your own
-
-If you already have one you can skip this part.
-
-- Open Keplr
-- Click on the user icon (up right)
-- `+ Add account`
-- Create new account
-- Follow the instructions: give a name to your wallet, remember the mnemonic and prove you can retrieve it.
-
-:::danger
-
-Watch out, the generated mnemonic and only it can give control on your wallet. Make sure to keep it safe so that:
-
-- You'll be able to recover it
-- Nobody else can access it
-
-:::
-
-## Transfer the NFT from the address provided by OKP4 to your personal address
-
-- In Keplr, when you are connected to your personal wallet (click on the icon in the upper right corner if you are not), copy the Stargaze address starting "stars1..." by clicking here
-
-
-
-- In Keplr, switch back to the temporary OKP4 wallet by clicking on the icon on the top right.
-- Go back to your NFT page: [https://app.stargaze.zone/profile](https://app.stargaze.zone/profile)
-- Select your NFT
-- Click on `Transfer`
-- Enter your home address starting with "stars1..." that you have copied
-- Validate the transaction with Keplr
-
-You now should have your NFT on your personal wallet!
diff --git a/docs/nft-tutorial/fr.md b/docs/nft-tutorial/fr.md
deleted file mode 100644
index db651d04173..00000000000
--- a/docs/nft-tutorial/fr.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-sidebar_position: 2
----
-
-# Tutoriel NFT OKP4
-
-> [English version](./en.md)
-
-## Prérequis
-
-Pour vous remercier d'avoir investi dans le jeton KNOW du protocole OKP4, l'équipe a décidé de vous offrir un [NFT](https://en.wikipedia.org/wiki/Non-fungible_token) unique !
-
-Ce NFT fait partie d'une collection de 76 NFTs qui ont été créés pour la première édition du BSJ. Il s'agit d'une preuve de participation au projet à ses débuts. Il n'a aucune valeur légale. Il peut être échangé, et vous êtes libres d'en faire ce que vous voulez. Il peut, ou non, vous donner droit à des avantages futurs.
-
-Ce NFT est conservé sur une adresse personnelle [Stargaze](https://www.stargaze.zone/) que nous avons créée spécialement pour vous. Cette adresse est contrôlée par une clé privée qui prend la forme d'un [mnémonique](https://journalducoin.com/actualites/phrases-mnemoniques/).
-
-Cependant, il est important de le transférer sur une autre adresse! Rien ne vous prouve que nous nous débarrasserons de la clé privée après vous l'avoir partagée. Vous devez donc transférer le NFT dans un portefeuille que vous avez créé vous-même.
-
-Ce tutoriel vous aidera à trouver votre NFT et à le transférer dans votre portefeuille personnel.
-
-## Installez Keplr
-
-Keplr est un wallet (ou portefeuille), une petite application qui vous permet de créer, protéger et contrôler des clé privées correspondantes à des adresses publiques sur les blockchains de l'écosystème Cosmos.
-
-Keplr vous permet de stocker votre clé en local sur votre ordinateur ou d'utiliser un portefeuille physique type Ledger ou Trezor.
-
-Si ce n'est pas déjà fait, installez Keplr : [https://www.keplr.app/](https://www.keplr.app/)
-Vous pouvez utiliser une de ces solutions:
-
-- [Extension Kepr](https://chrome.google.com/webstore/detail/keplr/dmkamcknogkgcdfhhbddcghachkejeap) pour les navigateurs [Google chrome](https://www.google.com/chrome/index.html) ou [Brave](https://brave.com/).
-- [Keplr wallet pour Iphone](https://apps.apple.com/us/app/keplr-wallet)
-- [Keplr wallet pour Android](https://play.google.com/store/apps/details?id=com.chainapsis.keplr)
-
-## Allez voir votre NFT
-
-Connectez vous avec l'adresse fournie par OKP4 en utilisant le fichier fournit dans le mail qui vous a été envoyé:
-
-- Décryptez le fichier reçu par mail à l'aide du mot de passe accessible par le lien temporaire fournit dans le même mail
-- Cliquez sur l'icône Keplr de votre navigateur :
- 
-- Vous devriez voir l'écran suivant:
- 
-- Cliquez sur `Import existing account`
-- Entrer votre mnémonique de 24 mots (le copier/coller de tous les mots d'un coup est possible)
-- Entrer un nom de compte, par exemple `nom + temporary okp4 wallet`
-- Choisissez un mot pour Keplr si cela vous est demandé.
-
-Maintenant, vous pouvez cliquer sur l'icône de l'extension Keplr
-
-- Sélectionnez la blockchain `Stargaze`
-
-
-
-La blockchain Stargaze est dédiée aux NFTs et fait partie de l'écosystème Cosmos.
-
-Vous devriez voir quelque chose comme ça :
-
-
-
-Vous pouvez maintenant aller sur [https://app.stargaze.zone](https://app.stargaze.zone)
-
-- Cliquez sur `Connect Wallet`
-- Une fois connecté vous pouvez cliquer sur l'icône utilisateur : 
-
-Vous devriez être redirigé vers la page de votre NFT :
-
-
-
-## Créez votre propre portefeuille
-
-Si vous en avez déjà un, vous pouvez sauter cette partie
-
-- Ouvrez Keplr
-- Cliquer sur l'icône utilisateur (en haut à droite)
-- `+ Add account`
-- `Create new account`
-- Suivez les instructions : donnez un nom à votre portefeuille personnel, notez précieusement le mnémonique, puis prouvez que vous pouvez le retrouver.
-
-:::danger
-
-Attention, le mnémonique généré et lui seul permet de contrôler votre portefeuille. Prenez soin de le garder en lieu sûr afin de :
-
-- De pouvoir le retrouver
-- Que personne d'autre ne puisse y accéder
-
-:::
-
-## Transférez le NFT de l'adresse fournie par OKP4 vers votre adresse personnelle
-
-- Dans Keplr, quand vous êtes connectés à votre wallet personnel (cliquez sur l'icone en haut à droite si vous n'y êtes pas), copiez l'adresse Stargaze commençant "stars1..." en cliquant ici
-
-
-
-- Dans Keplr, repassez sur le wallet temporaire OKP4 en cliquant sur l'icone en haut à droite.
-- Allez sur la page : [https://app.stargaze.zone/profile](https://app.stargaze.zone/profile)
-- Sélectionnez votre NFT
-- Cliquez sur le bouton `Transfer`
-- Entrez votre adresse personnelle commençant par "stars1..." que vous avez copié
-- Validez la transaction avec Keplr
-
-Vous devriez maintenant avoir votre NFT sur votre portefeuille personnel !
diff --git a/docs/nodes/_category_.json b/docs/nodes/_category_.json
index 20660ff3e79..4c9e0775283 100644
--- a/docs/nodes/_category_.json
+++ b/docs/nodes/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Running a Node",
- "position": 7
+ "position": 8
}
diff --git a/docs/provide-computation/_category_.json b/docs/provide-computation/_category_.json
index 946fe668c16..869e7e97ef3 100644
--- a/docs/provide-computation/_category_.json
+++ b/docs/provide-computation/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Provide Computation",
- "position": 4
+ "position": 5
}
diff --git a/docs/provide-computation/overview.mdx b/docs/provide-computation/overview.mdx
index c64d1c69037..cd762df11c4 100644
--- a/docs/provide-computation/overview.mdx
+++ b/docs/provide-computation/overview.mdx
@@ -4,4 +4,4 @@ sidebar_position: 1
# Provide Computation
-helloworld
+Work in Progress ⚙️
diff --git a/docs/share-resources/_category_.json b/docs/share-resources/_category_.json
index 51c7c0a33f9..0bf8c24af34 100644
--- a/docs/share-resources/_category_.json
+++ b/docs/share-resources/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Share Resources",
- "position": 3
+ "position": 4
}
diff --git a/docs/share-resources/overview.mdx b/docs/share-resources/overview.mdx
index 27ccd14512b..c4bae0a62cb 100644
--- a/docs/share-resources/overview.mdx
+++ b/docs/share-resources/overview.mdx
@@ -4,4 +4,4 @@ sidebar_position: 1
# Share Resources
-Helloworld
+Work in Progress ⚙️
diff --git a/docs/technical-documentation/_category_.json b/docs/technical-documentation/_category_.json
index ffe42308f3e..ed9482d3246 100644
--- a/docs/technical-documentation/_category_.json
+++ b/docs/technical-documentation/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Architecture",
- "position": 6
+ "position": 7
}
diff --git a/docs/technical-documentation/technical-implementation/decentralized-identity.mdx b/docs/technical-documentation/governance/decentralized-identity.mdx
similarity index 97%
rename from docs/technical-documentation/technical-implementation/decentralized-identity.mdx
rename to docs/technical-documentation/governance/decentralized-identity.mdx
index 3542bc3c71f..313e121ade2 100644
--- a/docs/technical-documentation/technical-implementation/decentralized-identity.mdx
+++ b/docs/technical-documentation/governance/decentralized-identity.mdx
@@ -1,10 +1,7 @@
---
-sidebar_position: 1
+sidebar_position: 7
---
-import Quiz from 'react-quiz-component'
-import * as quiz from './decentralized-identity-quiz.json'
-
# Decentralized identity
Unlike traditional identity systems, where personal identification information is centralized and often managed by a single entity (such as a company or government), **decentralized identity** enables individuals to control and operate their own identification data. This model, also known as Self-Sovereign Identity (SSI), offers several key advantages.
@@ -208,7 +205,7 @@ The limitations of the did:key method are:
# Decentralized identity in Axone Protocol
-The **[Axone ontology](/introduction/resources#ontology-how-its-represented-semantic-description)** is used to describe the dataverse. In the dataverse, resources are identified by their DID.
+The **[Axone ontology](/getting-started/introduction/resources#ontology-how-its-represented-semantic-description)** is used to describe the dataverse. In the dataverse, resources are identified by their DID.
Understanding and distinguishing key roles is essential when claiming a resource in the Axone dataverse. Although these roles are distinct, they can be exercised by the same or different entities. Here's a detailed explanation of each role:
@@ -235,5 +232,3 @@ In the case of a declaration of reputation, the roles are handled by distinct en
- The Issuer is a trusted authority
- The Holder is the Provider subject of the reputation claim
- The Registrant can be the Provider, the Issuer, or a third-party
-
-
diff --git a/docs/technical-documentation/technical-implementation/verifiable-claims.mdx b/docs/technical-documentation/governance/verifiable-claims.mdx
similarity index 93%
rename from docs/technical-documentation/technical-implementation/verifiable-claims.mdx
rename to docs/technical-documentation/governance/verifiable-claims.mdx
index 5e99d408a00..8bd274bec6d 100644
--- a/docs/technical-documentation/technical-implementation/verifiable-claims.mdx
+++ b/docs/technical-documentation/governance/verifiable-claims.mdx
@@ -1,10 +1,7 @@
---
-sidebar_position: 2
+sidebar_position: 8
---
-import Quiz from 'react-quiz-component'
-import * as quiz from './verifiable-claims-quiz.json'
-
# Verifiable Claims Principles
**Verifiable Credentials** are a key concept in the world of digital identity, particularly in decentralized identity systems. A Verifiable Credential is a form of digital evidence that attests to information or a characteristic about a person, organization, or object. A trusted entity that issues these credentials is called the **Issuer**.
@@ -60,7 +57,7 @@ The digital signature and metadata ensure enhanced security by preventing forger
## Verifiable claims in the Axone protocol
-The [Axone ontology](https://docs.okp4.network/introduction/resources#ontology-how-its-represented-semantic-description) is used to describe the Dataverse. In the Dataverse, resources are identified by their DID. Resources are described by claims referenced in the ontology as Verifiable Presentations (VPs) whose subject is the resource's DID. In this way, each resource is described by a set of associated claims.
+The [Axone ontology](https://docs.okp4.network/getting-started/introduction/resources#ontology-how-its-represented-semantic-description) is used to describe the Dataverse. In the Dataverse, resources are identified by their DID. Resources are described by claims referenced in the ontology as Verifiable Presentations (VPs) whose subject is the resource's DID. In this way, each resource is described by a set of associated claims.
It's important to note that the existence of a resource is conditional on the presence of at least one relevant claim. In other words, although the universe of potential resources is infinite, a resource only becomes concrete and tangible when a corresponding claim is established.
@@ -107,5 +104,3 @@ Recording VPs in the blockchain, rather than individual VCs, ensures the confide
style={{ maxHeight: '360px' }}
>
-
-
diff --git a/docs/technical-documentation/technical-implementation/_category_.json b/docs/technical-documentation/technical-implementation/_category_.json
deleted file mode 100644
index aea3f6a71c2..00000000000
--- a/docs/technical-documentation/technical-implementation/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
- "position": 7,
- "label": "Technical Implementation",
- "collapsible": true
-}
diff --git a/docs/technical-documentation/technical-implementation/decentralized-identity-quiz.json b/docs/technical-documentation/technical-implementation/decentralized-identity-quiz.json
deleted file mode 100644
index 2a47db9f68f..00000000000
--- a/docs/technical-documentation/technical-implementation/decentralized-identity-quiz.json
+++ /dev/null
@@ -1,83 +0,0 @@
-{
- "quizTitle": "Test your knowledge!",
- "nrOfQuestions": "5",
- "questions": [
- {
- "question": "What role does an Issuer play in decentralized identity?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "It verifies and confirms the authenticity of credentials.",
- "It receives and stores identification information.",
- "It signs reliable data in the form of Verifiable Credentials.",
- "It coordinates communication between the various players."
- ],
- "correctAnswer": "3",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "How does Zero-knowledge proof work in the context of decentralized identity?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "It reveals the all information at each verification.",
- "It allows information to be shared without revealing all details.",
- "It encrypts data in an irreversible manner.",
- "It modifies the data so as not to reveal the identity of the holder."
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What is a DID?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "A unique identifier for sovereign, verifiable digital identification.",
- "An encryption method used to protect online identities.",
- "A centralized system for managing digital identities.",
- "A communication protocol for blockchain networks."
- ],
- "correctAnswer": "1",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What is the role of the Registrant in the Axone protocol?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "It verifies and approves resource claims.",
- "It registers the Verifiable Presentation of a resource on the blockchain.",
- "It creates and manages resource DIDs.",
- "It encrypts information for enhanced security."
-
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What are the advantages of owning several DIDs?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "Lower transaction costs on the blockchain.",
- "Improved data processing speed.",
- "Separation of contexts, increased confidentiality and risk isolation.",
- "Centralized information for simpler management."
- ],
- "correctAnswer": "3",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- }
- ]
- }
-
\ No newline at end of file
diff --git a/docs/technical-documentation/technical-implementation/verifiable-claims-quiz.json b/docs/technical-documentation/technical-implementation/verifiable-claims-quiz.json
deleted file mode 100644
index 4f5dc9e9b76..00000000000
--- a/docs/technical-documentation/technical-implementation/verifiable-claims-quiz.json
+++ /dev/null
@@ -1,67 +0,0 @@
-{
- "quizTitle": "Test your knowledge!",
- "nrOfQuestions": "4",
- "questions": [
- {
- "question": "How does Verifiable Credential verification work?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "By contacting the credit issuer directly.",
- "By manually verifying its authenticity.",
- "By cryptography to confirm its origin and integrity.",
- "By using a centralized verification system."
- ],
- "correctAnswer": "3",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What is the difference between a Verifiable Credential and a Verifiable Presentation in the Axone protocol?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "A Verifiable Credential is a set of claims, whereas a Verifiable Presentation is a set of Verifiable Credentials derivations registered in the protocol.",
- "There is no significant difference between the two.",
- "A Verifiable Credential is used for financial transactions, while a Verifiable Presentation is for personal data.",
- "A Verifiable Credential is always public, while a Verifiable Presentation is always private."
- ],
- "correctAnswer": "1",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What best characterizes the Resource Governance VCs in Axone?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "They act as registries for financial transactions.",
- "They regulate and manage resources, defining how they are controlled, managed and interacted with.",
- "They are digital copies of physical documents.",
- "They serve as digital currency within the Axone ecosystem."
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- },
- {
- "question": "What is the Self-Sovereign principle of resource governance in Axone?",
- "questionType": "text",
- "answerSelectionType": "single",
- "answers": [
- "Only the government entity can make claims on resources.",
- "Any entity can make claims on a resource, with the exception of governance claims.",
- "Claims can only be issued by verified and approved entities.",
- "All claims are subject to verification by a central body."
- ],
- "correctAnswer": "2",
- "messageForCorrectAnswer": "Correct answer. Good job.",
- "messageForIncorrectAnswer": "Incorrect answer. Please try again.",
- "point": "1"
- }
- ]
- }
-
\ No newline at end of file
diff --git a/docs/tutorials/_category_.json b/docs/tutorials/_category_.json
index f019433b9ae..9a6a43319e9 100644
--- a/docs/tutorials/_category_.json
+++ b/docs/tutorials/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Guides",
- "position": 9
+ "position": 10
}
diff --git a/docs/whitepaper/_category_.json b/docs/whitepaper/_category_.json
index 5b9f5784ad1..5bd180655e8 100644
--- a/docs/whitepaper/_category_.json
+++ b/docs/whitepaper/_category_.json
@@ -1,4 +1,4 @@
{
"label": "Whitepaper",
- "position": 10
+ "position": 11
}
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 6c6a5386b1e..97c9e50b356 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -198,7 +198,7 @@ const config = {
to: '/whitepaper/abstract'
},
{
- label: 'Nodes & Validators',
+ label: 'Run a Node',
to: '/nodes/introduction'
},
{
@@ -219,8 +219,8 @@ const config = {
href: 'https://discord.gg/axone'
},
{
- label: 'Twitter',
- href: 'https://twitter.com/axonexyz'
+ label: 'X',
+ href: 'https://x.com/axonexyz'
},
{
label: 'GitHub',
@@ -228,15 +228,7 @@ const config = {
},
{
label: 'Telegram',
- href: 'https://t.me/okp4network'
- },
- {
- label: 'Zealy Program',
- href: 'https://zealy.io/c/okp4/questboard'
- },
- {
- label: 'Community discussions',
- href: 'https://github.com/axone-protocol/community/discussions'
+ href: 'https://t.me/axonexyz'
}
]
},
@@ -250,10 +242,6 @@ const config = {
{
label: 'Axone.xyz',
href: 'https://axone.xyz'
- },
- {
- label: 'OKP4 GPT',
- href: 'https://chat.openai.com/g/g-zUzcYmVbX-okp4-druid-oracle-beta'
}
]
},
diff --git a/sidebars.js b/sidebars.js
index c55faf393b1..22f4168580d 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -3,14 +3,14 @@
/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
const sidebars = {
mainSidebar: [{ type: 'autogenerated', dirName: '.' }],
- introduction: [
+ 'getting-started': [
{
type: 'category',
- label: 'Introduction',
+ label: 'Getting Started',
items: [
{
type: 'autogenerated',
- dirName: 'introduction'
+ dirName: 'getting-started'
}
]
}
@@ -92,16 +92,6 @@ const sidebars = {
}
]
},
- {
- type: 'category',
- label: 'Technical Implementation',
- items: [
- {
- type: 'autogenerated',
- dirName: 'technical-documentation/technical-implementation'
- }
- ]
- },
{
type: 'html',
value: ''
diff --git a/src/scss/card.scss b/src/scss/card.scss
index 1c313fc7970..eb7742d3deb 100644
--- a/src/scss/card.scss
+++ b/src/scss/card.scss
@@ -388,7 +388,8 @@
flex-direction: column;
min-width: 0;
word-wrap: break-word;
- background-image: url("/img/grain.webp"), linear-gradient(222.68deg, #f9f9f9 13.75%, #d3defa 76.51%);
+ background-image: url("/img/grain.webp"),
+ linear-gradient(222.68deg, #f9f9f9 13.75%, #d3defa 76.51%);
background-clip: border-box;
border-radius: 20px;
color: var(--ifm-card-font-color);
diff --git a/static/img/content/nft-tutorial/account-creation-keplr.webp b/static/img/content/nft-tutorial/account-creation-keplr.webp
deleted file mode 100644
index 1115e4554d2..00000000000
Binary files a/static/img/content/nft-tutorial/account-creation-keplr.webp and /dev/null differ
diff --git a/static/img/content/nft-tutorial/block-chain-select.webp b/static/img/content/nft-tutorial/block-chain-select.webp
deleted file mode 100644
index 17826d65c44..00000000000
Binary files a/static/img/content/nft-tutorial/block-chain-select.webp and /dev/null differ
diff --git a/static/img/content/nft-tutorial/keplr-account.webp b/static/img/content/nft-tutorial/keplr-account.webp
deleted file mode 100644
index d80c1002eff..00000000000
Binary files a/static/img/content/nft-tutorial/keplr-account.webp and /dev/null differ
diff --git a/static/img/content/nft-tutorial/keplr-icon.webp b/static/img/content/nft-tutorial/keplr-icon.webp
deleted file mode 100644
index 47b9f9479ee..00000000000
Binary files a/static/img/content/nft-tutorial/keplr-icon.webp and /dev/null differ
diff --git a/static/img/content/nft-tutorial/stargaze-account.webp b/static/img/content/nft-tutorial/stargaze-account.webp
deleted file mode 100644
index d64a5415788..00000000000
Binary files a/static/img/content/nft-tutorial/stargaze-account.webp and /dev/null differ
diff --git a/static/img/content/nft-tutorial/stargaze-nft.webp b/static/img/content/nft-tutorial/stargaze-nft.webp
deleted file mode 100644
index c6f054872c6..00000000000
Binary files a/static/img/content/nft-tutorial/stargaze-nft.webp and /dev/null differ
diff --git a/static/img/content/nft-tutorial/stargaze-wallet.webp b/static/img/content/nft-tutorial/stargaze-wallet.webp
deleted file mode 100644
index 2eefc82636e..00000000000
Binary files a/static/img/content/nft-tutorial/stargaze-wallet.webp and /dev/null differ