refactor: enhance documentation for guides and improve visibility of features

Author: Le-Caignec

README.md

@@ -150,6 +150,9 @@ Fork this repository and ensure you're working on the `main` branch:
 
 - Add Arbitrum support
 - 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`
+- 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

src/manage-data/guides/create-and-share-access.md

@@ -229,8 +229,3 @@ steps:
   [schemas and dataset types](/manage-data/guides/handle-schemas-dataset-types)
 - **Monetize data**: Explore
   [data monetization strategies](/manage-data/guides/manage-data-monetization)
-
----
-
-**TL;DR**: Protect data → Grant access to specific app + user → Data stays
-encrypted except inside authorized secure enclaves. You keep full control. 🔒

src/manage-data/guides/handle-schemas-dataset-types.md

@@ -6,11 +6,12 @@ description:
 
 # 🏷️ Handle Schemas and Dataset Types
 
-**Schemas are like TypeScript for your protected data.** They define the
-structure and types of your data automatically when you protect it, making it
-easy for iApps to know what they're working with.
+**Schemas are like content labels that describe what's inside your protected data.**
 
-Think of schemas as **data labels** - they tell iApps "this protected data
+They define the structure and types of your data automatically when you protect
+it, making it easy for iApps to know what they're working with.
+
+Think of schemas as **data fingerprints** - they tell iApps "this protected data
 contains an email address and a phone number" without revealing the actual
 values.
 
@@ -20,12 +21,12 @@ When you protect data with DataProtector, the SDK automatically analyzes your
 JSON object and generates a schema. **No manual schema definition needed** -
 it's all handled for you.
 
-```ts
+```ts twoslash
 import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
 
 const web3Provider = getWeb3Provider('PRIVATE_KEY');
 const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
-
+// ---cut---
 const protectedData = await dataProtectorCore.protectData({
   name: 'User Contact',
   data: {
@@ -38,20 +39,27 @@ const protectedData = await dataProtectorCore.protectData({
   },
 });
 
-// The schema is automatically generated:
-console.log(protectedData.schema);
-/* Output:
+console.log('✅ Protected data created!');
+console.log('📍 Address:', protectedData.address);
+```
+
+**🏷️ Generated Schema:**
+
+```json
 {
-  email: 'string',
-  phoneNumber: 'string', 
-  preferences: {
-    newsletter: 'bool',
-    notifications: 'bool'
+  "email": "string",
+  "phoneNumber": "string", 
+  "preferences": {
+    "newsletter": "bool",
+    "notifications": "bool"
   }
 }
-*/
 ```
 
+::: info Schema Structure
+The schema automatically maps your data structure to types that iApps can understand and validate.
+:::
+
 ## Supported Data Types
 
 The schema automatically detects these types:
@@ -65,16 +73,22 @@ The schema automatically detects these types:
 | `application/octet-stream`      | Binary data    | File contents         |
 | `image/jpeg`, `image/png`, etc. | Media files    | Images, videos        |
 
-::: tip Auto-Detection The SDK automatically detects file types based on
-content. No need to specify MIME types manually. :::
+::: tip Auto-Detection
+The SDK automatically detects file types based on
+content. No need to specify MIME types manually.
+:::
 
 ## Why Schemas Matter
 
 ### 🎯 **For iApp Development**
 
 Schemas let your iApps validate and process data safely:
 
-```js
+```ts twoslash
+import { IExecDataProtectorDeserializer } from '@iexec/dataprotector-deserializer';
+
+const deserializer = new IExecDataProtectorDeserializer();
+// ---cut---
 // Inside your iApp
 const email = await deserializer.getValue('email', 'string');
 const preferences = await deserializer.getValue(
@@ -83,38 +97,64 @@ const preferences = await deserializer.getValue(
 );
 ```
 
+### 🛡️ **For Type Safety**
+
+Prevents your iApps from processing incompatible data types.
+
 ### 🔍 **For Data Discovery**
 
 Users can find relevant protected data without seeing the actual content:
 
-```ts
-// Find all protected data with email addresses
-const query = { schema: { email: 'string' } };
-// Returns metadata only, no actual emails revealed
-```
-
-### 🛡️ **For Type Safety**
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
 
-Prevents your iApps from processing incompatible data types.
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
+const listProtectedData = await dataProtectorCore.getProtectedData({
+  requiredSchema: {
+    email: 'string',
+  },
+});
+```
 
 ## Real Examples
 
 ### Simple User Profile
 
-```ts
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
 const userData = await dataProtectorCore.protectData({
   data: {
     email: '[email protected]',
     age: 25,
     isSubscribed: true,
   },
 });
-// Schema: { email: 'string', age: 'f64', isSubscribed: 'bool' }
+```
+
+**🏷️ Generated Schema:**
+
+```json
+{
+  "email": "string",
+  "age": "f64",
+  "isSubscribed": "bool"
+}
 ```
 
 ### Nested Contact Information
 
-```ts
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
 const contactData = await dataProtectorCore.protectData({
   data: {
     personal: {
@@ -131,15 +171,43 @@ const contactData = await dataProtectorCore.protectData({
     },
   },
 });
-// Schema reflects the full nested structure
+```
+
+**🏷️ Generated Schema:**
+
+```json
+{
+  "personal": {
+    "firstName": "string",
+    "lastName": "string"
+  },
+  "contact": {
+    "email": "string",
+    "phone": "string"
+  },
+  "preferences": {
+    "marketing": "bool",
+    "notifications": "bool"
+  }
+}
 ```
 
 ### File Data
 
-```ts
-import { createArrayBufferFromFile } from '@iexec/dataprotector';
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+// Mock function for the example
+function createArrayBufferFromFile(file: File): Promise<ArrayBuffer> {
+  return Promise.resolve(new ArrayBuffer(0));
+}
+
+// Get file from input element
+const file = new File([""], "example.jpg", { type: "image/jpeg" });
 
-const file = document.getElementById('fileInput').files[0];
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
 const fileBuffer = await createArrayBufferFromFile(file);
 
 const fileData = await dataProtectorCore.protectData({
@@ -149,20 +217,31 @@ const fileData = await dataProtectorCore.protectData({
     uploadDate: Date.now(),
   },
 });
-// Schema: { fileName: 'string', fileContent: 'image/jpeg', uploadDate: 'f64' }
+```
+
+**🏷️ Schema for file upload:**
+
+```json
+{
+  "fileName": "string",
+  "fileContent": "image/jpeg",
+  "uploadDate": "f64"
+}
 ```
 
 ## Using Schemas in iApps
 
 Once you have protected data with a schema, you'll want to process it inside an
 iApp.
 
-::: warning Type Matching **Your iApp and frontend must use the same field names
+::: warning Type Matching
+**Your iApp and frontend must use the same field names
 and types.** If they don't match, you'll get runtime errors when processing the
-data. :::
+data.
+:::
 
 → **Ready to build an iApp?** Check out our detailed
-[Inputs and Outputs guide](/build_iapp/guides/inputs-and-outputs) to learn how
+[Inputs and Outputs guide](/build-iapp/guides/inputs-and-outputs) to learn how
 to access schema fields inside your iApp using the deserializer.
 
 ## Next Steps
@@ -171,16 +250,10 @@ to access schema fields inside your iApp using the deserializer.
 explore next:
 
 - **Build an iApp**: Check out the
-  [iApp Generator guide](/build_iapp/iapp-generator) to create your first data
+  [iApp Generator guide](/build-iapp/iapp-generator) to create your first data
   processor
 - **Process data**: Learn about
   [processProtectedData](/manage-data/dataProtector/dataProtectorCore/processProtectedData)
   for running computations
 - **See it in action**: Try our [Hello World tutorial](/overview/helloWorld) for
   a complete example
-
----
-
-**TL;DR**: Schemas = auto-generated data labels. Frontend protects data → Schema
-describes structure → iApp uses schema to access fields safely. Match your field
-names and types between frontend and iApp! 🏷️