Merge branch 'main' into feature/get-started

Author: Le-Caignec

.vitepress/config.mts

@@ -91,7 +91,7 @@ export default defineConfig({
       { text: 'Core Concept', link: '/core-concept/glossary' },
     ],
     outline: {
-      level: [2, 3],
+      level: [2, 4],
     },
 
     sidebar: getSidebar(),

.vitepress/sidebar.ts

@@ -65,7 +65,6 @@ export function getSidebar() {
           },
           {
             text: '📖 Guides',
-            link: '/manage-data/guides',
             items: [
               {
                 text: 'Create and Share Access to Protected Data',
@@ -76,24 +75,19 @@ export function getSidebar() {
                 link: '/manage-data/guides/handle-schemas-dataset-types',
               },
               {
-                text: 'Manage Data Monetization',
-                link: '/manage-data/guides/manage-data-monetization',
+                text: 'Monetize Protected Data',
+                link: '/manage-data/guides/monetize-protected-data',
               },
             ],
           },
           {
             text: '🔐 DataProtector',
             link: '/manage-data/dataProtector',
-            collapsed: true,
             items: [
               {
                 text: 'Getting Started',
                 link: '/manage-data/dataProtector/getting-started',
               },
-              {
-                text: 'Guides',
-                link: '/manage-data/dataProtector/guides',
-              },
               {
                 text: 'DataProtector Core',
                 link: '/manage-data/dataProtector/dataProtectorCore',

README.md

@@ -97,6 +97,7 @@ Fork this repository and ensure you're working on the `main` branch:
    ```
 
 3. Start the development server:
+
    ```bash
    npm run dev
    ```
@@ -138,14 +139,24 @@ Fork this repository and ensure you're working on the `main` branch:
 > - All pull requests are reviewed by our team before being merged
 > - Feel free to ask questions in the pull request if you need clarification
 
-## 📄 License
-
-This project is part of the iExec ecosystem. Please refer to the main iExec
-repositories for licensing information.
-
 ## 🆘 Support
 
 - 📖 [Documentation](https://docs.iex.ec)
 - 💬 [Discord Community](https://discord.com/invite/pbt9m98wnU)
 - 🐛
   [Issue Tracker](https://github.com/iExecBlockchainComputing/documentation/issues)
+
+## TODO
+
+- Add Arbitrum support
+- On arbitrum hide : Oracle Factory ? , DataProtector Sharing ??
+- Adapt hardcoded address to feat with new contracts deployed on arbitrum
+- Add link to the new explorer feature Asset_Types in the guide =>
+  `handle-schemas-dataset-types`
+- Add link to remix for deploying whitelist
+- Move `manage-data/dataProtector/advanced/iApp` (Deserializer doc) in an other
+  way to be more visible (may in build-iApp section)
+- complete `use-iapp` section
+- complete `explorer` section
+- complete `build-iapp` section
+- complete `deep-dive`section

package-lock.json

@@ -25,7 +25,7 @@ features:
     details:
       Secure your data with advanced encryption and control access while
       maintaining privacy using DataProtector
-    link: /manage-data/dataProtector/what-is-protected-data
+    link: /manage-data/what-is-protected-data
   - icon: 🤖
     title: Build iApps
     details:
@@ -43,7 +43,7 @@ features:
     details:
       Create revenue streams from your data while maintaining full control and
       privacy
-    link: /manage-data/guides/manage-data-monetization
+    link: /manage-data/guides/monetize-protected-data
   - icon: 🧠
     title: Core Concepts
     details:

src/index.md

@@ -44,7 +44,8 @@ import { type GrantAccessParams } from '@iexec/dataprotector';
 
 **Type:** `AddressOrENS`
 
-The ethereum address of the protected data supplied by the user.
+The ethereum address of the protected data supplied by the user (returned when
+you created it). **You must own this data** to grant access.
 
 ```ts twoslash
 import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
@@ -68,9 +69,9 @@ The address of the application you wish to authorize to process the
 single application or an application whitelist. To specify a whitelist, you
 provide the ETH address of an
 [iExec Whitelist Smart Contract](https://github.com/iExecBlockchainComputing/whitelist-smart-contract/tree/main).
-This smart contract aggregates multiple application versions. This allows you to
-introduce new versions of your application without needing to grant access for
-the `protectedData` each time you do so.
+This smart contract should aggregates multiple application versions. This allows
+you to introduce new versions of your application without needing to grant
+access for the `protectedData` each time you do so.
 
 ```ts twoslash
 import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
@@ -180,12 +181,14 @@ used.
 It is not technically possible to set an unlimited number of accesses, but you
 can set `numberOfAccess` to `10000` for example.
 
-::: info Important Notes: If you attempt to process the protected data more
-times than specified in `numberOfAccess`, you will encounter a **"no dataset
-orders"** error.
+::: info
+
+If you attempt to process the protected data more times than specified in
+`numberOfAccess`, you will encounter a **"no dataset orders"** error.
 
 To prevent this error, ensure the `numberOfAccess` is properly set when calling
-the `grantAccess` method.  
+the `grantAccess` method.
+
 :::
 
 ```ts twoslash