docs: integrate ChainNotSupportedBadge across data protector documentation

Added ChainNotSupportedBadge to various sections of the data protector documentation, including sharing, renting, and subscription methods, to indicate unsupported chains. Removed the obsolete dps-smart-contract documentation and updated the README with a new development workflow section. Enhanced clarity by importing the badge component in relevant script sections.

Author: Le-Caignec

.vitepress/sidebar.ts

@@ -429,10 +429,6 @@ export function getSidebar() {
                 text: 'Advanced Configuration',
                 link: '/references/dataProtector/advanced/advanced-configuration',
               },
-              {
-                text: 'Sharing smart contract',
-                link: '/references/dataProtector/advanced/dps-smart-contract',
-              },
               {
                 text: 'Apps whitelist',
                 link: '/references/dataProtector/advanced/apps-whitelist',

README.md

@@ -168,19 +168,15 @@ for input parameters:
 ## TODO
 
 - Add an audit section for smart contracts
-- Add Arbitrum support
 - On arbitrum hide : 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
-- complete `use-iapp` section
-- Maybe split input and output in two diff sub section in build your iapp guide
 - SGX vs TDX need review
 - Explorer l'intégration de codeSpace
-- complete `Protocol`section
-- Add a Development workflow
-- Update context7 when doc will be deployed
+- Add a Development workflow pahe (1 - ProtectData, 2- ...)
+- Update context7 when doc will be deployed (Martin)
 - Check theGraph Images with design Team
 - Update the Dune Dashboard to the final version
 - Add new section in `iexec-explorer.md` file to talk about: available chain on
@@ -189,7 +185,7 @@ for input parameters:
 - Check how to pay guide to update with the launch on Arbitrum (RLC vs xRLC)
 - framework AI supporté TDX vs SGX
 - check glossary
-- migrate github SDK doc here
+- migrate github iexec SDK doc here
 - migrate pay-per-task page into a guide
 - check pages (introduction & getting-started) for use-iapp guide
 - explain TDX vs SGX

src/references/dataProtector/advanced/advanced-configuration.md

@@ -22,7 +22,7 @@ section.
 import { type DataProtectorConfigOptions } from '@iexec/dataprotector';
 ```
 
-### dataprotectorContractAddress
+### dataprotectorContractAddress <ChainNotSupportedBadge />
 
 `AddressOrENS`
 
@@ -164,3 +164,7 @@ const dataProtector = new IExecDataProtector(web3Provider, {
 discontinuity.
 
 :::
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>

src/references/dataProtector/advanced/apps-whitelist.md

@@ -6,7 +6,7 @@ description:
   Environment (TEE) dApp and whitelist usage for secure data delivery.
 ---
 
-# Apps Whitelist
+# Apps Whitelist <ChainNotSupportedBadge />
 
 In order to consume a protected data, an iExec TEE dApp needs to be provided.
 
@@ -78,3 +78,7 @@ See it in
 
 See it in
 [https://blockscout-bellecour.iex.ec/](https://blockscout-bellecour.iex.ec/address/0x1cb7D4F3FFa203F211e57357D759321C6CE49921)
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>

src/references/dataProtector/advanced/apps-whitelist/addAppToAddOnlyAppWhitelist.md

@@ -5,7 +5,7 @@ description:
   data access control.
 ---
 
-# addAppToAddOnlyAppWhitelist
+# addAppToAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
 Method to add an app (iExec TEE dApp) into the `AddOnlyAppWhitelist`.
 
@@ -99,4 +99,5 @@ See [`SuccessWithTransactionHash`](../../types.md#successwithtransactionhash)
 
 <script setup>
 import RequiredBadge from '@/components/RequiredBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>

src/references/dataProtector/advanced/apps-whitelist/createAddOnlyAppWhitelist.md

@@ -5,7 +5,7 @@ description:
   becomes the owner by default, with transferable ownership as an ERC721.
 ---
 
-# createAddOnlyAppWhitelist
+# createAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
 Method to create an `AddOnlyAppWhitelist`. By default, the owner will be the
 caller of the `createAddOnlyAppWhitelist` method, but as the
@@ -31,3 +31,7 @@ const isAddedToAddAppToAddOnlyAppWhitelist =
 ```ts twoslash
 import { type CreateAppWhitelistResponse } from '@iexec/dataprotector';
 ```
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>

src/references/dataProtector/advanced/apps-whitelist/getUserAddOnlyAppWhitelist.md

@@ -5,7 +5,7 @@ description:
   app access control management.
 ---
 
-# getUserAddOnlyAppWhitelist
+# getUserAddOnlyAppWhitelist <ChainNotSupportedBadge />
 
 Method to get `AddOnlyAppWhitelist`, you can filter by user ethereum address.
 
@@ -62,4 +62,5 @@ import { type AddOnlyAppWhitelist } from '@iexec/dataprotector';
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
 </script>

src/references/dataProtector/advanced/dps-smart-contract.md

@@ -160,7 +160,7 @@ sufficient funds for this transfer to proceed.
 
 :::
 
-### voucherOwner <OptionalBadge />
+### voucherOwner <ChainNotSupportedBadge /> <OptionalBadge />
 
 **Type:** `Address`
 

src/references/dataProtector/dataProtectorCore/processProtectedData.md

@@ -6,7 +6,7 @@ description:
   maintaining control and privacy.
 ---
 
-# DataProtector Sharing
+# DataProtector Sharing <ChainNotSupportedBadge />
 
 The DataProtector Sharing module includes a set of methods for distributing and
 monetizing your protected data. These work seamlessly in your own applications
@@ -63,3 +63,7 @@ additional activity from the data owner. This has several key benefits
   distribution, only the consumer of the data signs their transaction
 - The data owner doesn't manage access, the Data Sharing smart contract
   automatically enforces the distribution and monetization choices
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>