Cleaned up the .gibook/assets folder

README.md

@@ -10,14 +10,14 @@ Ocean provides the next generation of tools to unlock data at a large scale. Oce
 
 Ocean uses Data NFTs (ERC721) and datatokens (ERC20) as the interface to connect data assets with blockchain and DeFi tools. Crypto wallets become data wallets, crypto exchanges become data marketplaces, DAOs for data co-ops, and more via DeFi composability.
 
-![Creating a New Data Economy](./.gitbook/assets/feature-datascience@2x.webp)
+![Creating a New Data Economy](./.gitbook/assets/architecture/feature-datascience@2x.webp)
 
 The following guides are a greate place to start if you are new to Ocean:
 
-* [Architecture Overview](core-concepts/architecture.md)
-* [Data NFTs and Datatokens](core-concepts/datanft-and-datatoken.md)
-* [Publish a data asset](using-ocean-market/marketplace-publish-data-asset.md)
-* [Download a data asset](using-ocean-market/marketplace-download-data-asset.md)
+- [Architecture Overview](core-concepts/architecture.md)
+- [Data NFTs and Datatokens](core-concepts/datanft-and-datatoken.md)
+- [Publish a data asset](using-ocean-market/marketplace-publish-data-asset.md)
+- [Download a data asset](using-ocean-market/marketplace-download-data-asset.md)
 
 ## What is our Mission?
 
@@ -37,13 +37,13 @@ Use Ocean Market to publish and sell data, or browse and buy data. Data is publi
 
 As a data scientist or AI practitioner, you can benefit from access to more data (including private data), crypto-secured provenance in data & AI training, and income opportunities for selling data and curating data.
 
-![Decentralized Exchange Marketplaces](./.gitbook/assets/feature-marketplaces@2x.webp)
+![Decentralized Exchange Marketplaces](./.gitbook/assets/architecture/feature-marketplaces@2x.webp)
 
 The following guides will help you get started with buying and selling data:
 
-* [Publish a data asset](using-ocean-market/marketplace-publish-data-asset.md)
-* [Download a data asset](using-ocean-market/marketplace-download-data-asset.md)
-* [Publishing with hosting services](using-ocean-market/asset-hosting.md)
+- [Publish a data asset](using-ocean-market/marketplace-publish-data-asset.md)
+- [Download a data asset](using-ocean-market/marketplace-download-data-asset.md)
+- [Publishing with hosting services](using-ocean-market/asset-hosting.md)
 
 ### Build Your Own Data Market
 
@@ -53,9 +53,9 @@ Use Ocean Protocol software tools to build your own data marketplace, by either
 
 If you're interested in starting your own marketplace checkout the following guides:
 
-* [Forking Ocean Market](building-with-ocean/build-a-marketplace/forking-ocean-market.md)
-* [Customising your market](building-with-ocean/build-a-marketplace/customising-your-market.md)
-* [Deploying your market](building-with-ocean/build-a-marketplace/deploying-market.md)
+- [Forking Ocean Market](building-with-ocean/build-a-marketplace/forking-ocean-market.md)
+- [Customising your market](building-with-ocean/build-a-marketplace/customising-your-market.md)
+- [Deploying your market](building-with-ocean/build-a-marketplace/deploying-market.md)
 
 ### Manage datatokens and data NFTs for use in DeFi
 
@@ -65,7 +65,7 @@ Use Ocean [JavaScript](https://github.com/oceanprotocol/ocean.js) or [Python](ht
 
 Ocean-based apps make data asset on-ramps and off-ramps easy for end users. Ocean smart contracts and libraries make this easy for developers. The data itself does not need to be on-chain, just the access control.
 
-![New Data on-ramp and off-ramp](./.gitbook/assets/new-ramp-on-crypto-ramp-off.webp)
+![New Data on-ramp and off-ramp](./.gitbook/assets/architecture/new-ramp-on-crypto-ramp-off.webp)
 
 Data NFTs are ERC721 tokens representing the unique asset and datatokens are ERC20 tokens to access data services. Each data service gets its own data NFT and one or more type of datatokens.
 
@@ -73,10 +73,9 @@ To access the dataset, you send 1.0 datatokens to the data provider (running Oce
 
 Since datatokens are ERC20, and live on Ethereum mainnet, there's a whole ecosystem to leverage.
 
-* _Publish and access data services:_ downloadable files or compute-to-data. Use Ocean to deploy a new [ERC721](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md) and [ERC20](https://github.com/ethereum/EIPs/blob/7f4f0377730f5fc266824084188cc17cf246932e/EIPS/eip-20.md) datatoken contract for each data service, then mint datatokens.
-* _Transfer datatokens_ to another owner (or approve & transferFrom).
-* _And more._ Use ERC20 support in [web3.js](https://web3js.readthedocs.io/), [web3.py](https://web3py.readthedocs.io/en/stable/examples.html#working-with-an-erc20-token-contract) and Solidity to connect datatokens with crypto wallets and other DeFi services.
-
+- _Publish and access data services:_ downloadable files or compute-to-data. Use Ocean to deploy a new [ERC721](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md) and [ERC20](https://github.com/ethereum/EIPs/blob/7f4f0377730f5fc266824084188cc17cf246932e/EIPS/eip-20.md) datatoken contract for each data service, then mint datatokens.
+- _Transfer datatokens_ to another owner (or approve & transferFrom).
+- _And more._ Use ERC20 support in [web3.js](https://web3js.readthedocs.io/), [web3.py](https://web3py.readthedocs.io/en/stable/examples.html#working-with-an-erc20-token-contract) and Solidity to connect datatokens with crypto wallets and other DeFi services.
 
 ### Compute-to-Data
 
@@ -86,7 +85,7 @@ Compute-to-data resolves the tradeoff between the benefits of using private data
 
 The most valuable data is private data — using it can improve research and business outcomes. But concerns over privacy and control make it hard to access. With Compute-to-Data, private data isn’t directly shared but rather specific access to it is granted.
 
-![Compute-to-data](./.gitbook/assets/feature-compute@2x.webp)
+![Compute-to-data](./.gitbook/assets/architecture/feature-compute@2x.webp)
 
 It can be used for data sharing in science or technology contexts, or in marketplaces for selling private data while preserving privacy, as an opportunity for companies to monetize their data assets.
 
@@ -94,11 +93,12 @@ Private data can help research, leading to life-altering innovations in science
 
 Checkout these guides if you are aiming to get a deeper understanding on how compute-to-data works:
 
-* [Architecture](building-with-ocean/compute-to-data/compute-to-data-architecture.md)
-* [Datasets & Algorithms](building-with-ocean/compute-to-data/compute-to-data-datasets-algorithms.md)
-* [Minikube Environment](building-with-ocean/compute-to-data/compute-to-data-minikube.md)
-* [Writing Algorithms](building-with-ocean/compute-to-data/compute-to-data-algorithms.md)
-* [Private docker registry](building-with-ocean/compute-to-data/compute-to-data-docker-registry.md)
+- [Architecture](building-with-ocean/compute-to-data/compute-to-data-architecture.md)
+- [Datasets & Algorithms](building-with-ocean/compute-to-data/compute-to-data-datasets-algorithms.md)
+- [Minikube Environment](building-with-ocean/compute-to-data/compute-to-data-minikube.md)
+- [Writing Algorithms](building-with-ocean/compute-to-data/compute-to-data-algorithms.md)
+- [Private docker registry](building-with-ocean/compute-to-data/compute-to-data-docker-registry.md)
+
 ## How does it work?
 
 In Ocean Protocol, each asset gets its own ERC721 **data NFT** and one(or more) ERC20 **datatokens**. This enables data wallets, data exchanges, and data co-ops by directly leveraging crypto wallets, exchanges, and more.
@@ -107,23 +107,23 @@ Ocean Protocol provides tools for developers to _build data markets_, and to _ma
 
 If you are new to web3 and blockchain technologies then we suggest you first read these introductory guides:
 
-* [Wallet Basics](building-with-ocean/wallets.md)
-* [Set Up MetaMask Wallet](orientation/metamask-setup.md)
-* [Manage Your OCEAN Tokens](building-with-ocean/wallets-and-ocean-tokens.md)
+- [Wallet Basics](building-with-ocean/wallets.md)
+- [Set Up MetaMask Wallet](orientation/metamask-setup.md)
+- [Manage Your OCEAN Tokens](building-with-ocean/wallets-and-ocean-tokens.md)
 
 If ou are looking to get to grips with the inner workings of Ocean, then you'll be interested in the following guides:
 
-* [Architecture Overview](./core-concepts/architecture.md)
-* [Data NFTs and Datatokens](./core-concepts/datanft-and-datatoken.md)
-* [Networks](./core-concepts/networks.md)
-* [Fees](./core-concepts/fees.md)
-* [Asset pricing](./core-concepts/asset-pricing.md)
-* [DID & DDO](./core-concepts/did-ddo.md)
-* [Roles](./core-concepts/roles.md)
-* [Set Up a Marketplace](./building-with-ocean/marketplace.md)
-* [Compute-to-Data](./building-with-ocean/compute-to-data/README.md)
-* [Deploying components](building-with-ocean/deploying-components/README.md)
-* [Contributing](core-concepts/contributing.md)
+- [Architecture Overview](./core-concepts/architecture.md)
+- [Data NFTs and Datatokens](./core-concepts/datanft-and-datatoken.md)
+- [Networks](./core-concepts/networks.md)
+- [Fees](./core-concepts/fees.md)
+- [Asset pricing](./core-concepts/asset-pricing.md)
+- [DID & DDO](./core-concepts/did-ddo.md)
+- [Roles](./core-concepts/roles.md)
+- [Set Up a Marketplace](./building-with-ocean/marketplace.md)
+- [Compute-to-Data](./building-with-ocean/compute-to-data/README.md)
+- [Deploying components](building-with-ocean/deploying-components/README.md)
+- [Contributing](core-concepts/contributing.md)
 
 ## Supporters
 

building-with-ocean/build-a-marketplace/customising-your-market.md

@@ -28,25 +28,25 @@ It’s now time to open up your favorite code editor and start getting stuck int
 
 Let’s start by searching and replacing “Ocean Marketplace”. In VS Code there is a magnifying glass symbol in the left-hand panel (arrow 1 in the image below) that will open up the interface for searching and replacing text. Type “Ocean Marketplace” into the first textbox, and the name of your marketplace into the second textbox (arrow 2). To make things simple, there is a button to the right of the second textbox (arrow 3) that will replace all instances at once. You can take a moment to review all the text you’re changing if you wish, and then click this button.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-3.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-3.png)
 
 Next up, we need to repeat the process but this time we’ll be searching and replacing “Ocean Market”. As you can see in the screenshot below, we have called our fork “Crypto Photos Market”.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-4.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-4.png)
 
-![Market Customisation](../../.gitbook/assets/market-customisation-4.1.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-4.1.png)
 
-![Market Customisation](../../.gitbook/assets/market-customisation-4.2.jpg)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-4.2.jpg)
 
 Now let’s change the tagline of your site. Open up the folder called “content” and then open the file called “site.json”.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-5.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-5.png)
 
 On line 3 in this file you can enter the tagline that you want for your marketplace.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-6.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-6.png)
 
-![Market Customisation](../../.gitbook/assets/market-customisation-6.1.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-6.1.png)
 
 ## Change the Logo
 
@@ -60,7 +60,7 @@ Delete the “logo.svg” file from that folder and paste your own logo in the s
 
 At this point, it’s a good idea to check how things are looking. First check that you have saved all of your changes, then cancel the build that’s running in your terminal (Ctrl + C OR Cmnd + C) and start it again `npm start`. Once the build has finished, navigate to http://localhost:8000/ and see how things look.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-7.1.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-7.1.png)
 
 Awesome! Our logo is looking great!
 
@@ -78,18 +78,18 @@ src/components/App/index.module.css
 
 You’ll notice in the screenshot above that we are setting our “wave” background on line 3. Here, you’ll want to use your own background color or image. For this example, we’ll use an SVG background from [here](https://www.svgbackgrounds.com/). First, we save the new background image into the src/images/ folder (same folder as the logo), then we change the CSS to the file location of the new background (see line 3 in the image below).
 
-![Market Customisation](../../.gitbook/assets/market-customisation-8.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-8.png)
 
 If we save this file and view the site at this point, we get a white section at the top (see image below). And you’ll also notice that the background doesn’t fill all the way down to the bottom of the screen.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-10.1.png)
-![Market Customisation](../../.gitbook/assets/market-customisation-10.2.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-10.1.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-10.2.png)
 
 To fix this, we need to change the starting position of the background image and change it from no-repeat to repeat. We can do this on line 3.
 
 When we view our marketplace, we can see that the new background starts at the top and fills the whole page. Perfect!
 
-![Market Customisation](../../.gitbook/assets/market-customisation-11.1.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-11.1.png)
 
 ## Brand Colors
 
@@ -97,7 +97,7 @@ Next up, let’s change the background colors to match your individual style. Op
 
 You can change these colors as much as you wish until you’re happy with how everything looks. Each time you save your changes, the site will immediately update so you can see how things look. You can see the styles chosen for this example in the image below.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-12.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-12.png)
 
 ## Change Fonts
 
@@ -111,41 +111,41 @@ If you are importing fonts, such as from Google fonts, you need to make sure tha
 
 As with the color changes, it’s a good idea to save the file with each change and check if the site is looking the way that you expected it to. You can see our eclectic choices below.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-13.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-13.png)
 
 ## Customize the Publish Form
 
 Let’s head to the publish page to see what it looks like with our new styling - so far, so good. But there is one major issue, the publish form is still telling people to publish datasets. On our new marketplace, we want people to publish and sell their photos, so we’re going to have to make some changes here.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-14.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-14.png)
 
 Open up the index.json file from content/publish/index.json - here we change the text to explain that this form is for publishing photos.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-15.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-15.png)
 
 Additionally, the asset type current says dataset, and we need to change this so that it says photo. The simplest way to do this is to change the title of the asset type without changing anything else. Ocean can handle selling any digital asset that can be accessed via a URL, so no further changes are needed to accommodate selling photos.
 
 Open up src/components/Publish/Metadata/index.tsx and change line 28 so that it says ‘Photo’
 
-![Market Customisation](../../.gitbook/assets/market-customisation-18.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-18.png)
 
 Great, now our publish page explains that users should be publishing photos and photo is provided as an asset type option. We’ll also leave algorithm as an option in case some data scientists want to do some analysis or image transformation on the photos.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-19.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-19.png)
 
 There is one more thing that is fun to change before we move away from the publish form. You’ll notice that Ocean Market V4 now has a cool SVG generation feature that creates the images for the Data NFT. It creates a series of pink waves. Let’s change this so that it uses our brand colors in the waves!
 
 Open up /src/@utils/SvgWaves.ts and have a look at lines 27 to 30 where the colors are specified. Currently, the pink color is the one used in the svg generator. You can replace this with your own brand color:
 
-![Market Customisation](../../.gitbook/assets/market-customisation-21.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-21.png)
 
 If you’re interested in doing some further customization, take a look at lines 53 to 64. You can change these properties to alter how the image looks. Feel free to play around with it. We’ve increased the number of layers from 4 to 5.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-22.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-22.png)
 
 And now your customized publish page is ready for your customers:
 
-![Market Customisation](../../.gitbook/assets/market-customisation-20.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-20.png)
 
 ## Change the Fee Address
 
@@ -153,7 +153,7 @@ At this point, we have made a lot of changes and hopefully you’re happy with t
 
 When someone sets the pricing for their photos in your marketplace, they are informed that a commission will be sent to the owner of the marketplace. You see that at the moment this fee is set to zero, so you’ll want to increase that. And in order to receive the fees you’ll you need to set the address that you want to recieve these fees in.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-23.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-23.png)
 
 This important step is the last thing that we will change in this guide. To set the marketplace fees and address, you’ll need to save them as environmental variables. Create a new file called .env in the root of your repository.
 
@@ -175,8 +175,8 @@ Go to [Fees page](https://docs.oceanprotocol.com/concepts/fees/) to know more de
 
 It is important that the file is saved in the right place at the root of your repository, your file structure should look the same as below.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-24.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-24.png)
 
 Now that’s it; you now have a fully functioning photo marketplace that operates over the blockchain. Everytime someone uses it, you will receive revenue.
 
-![Market Customisation](../../.gitbook/assets/market-customisation-25.png)
+![Market Customisation](../../.gitbook/assets/market-customisation/market-customisation-25.png)

building-with-ocean/compute-to-data/user-defined-parameters.md

@@ -12,8 +12,8 @@ Ocean Protocol allows dataset buyers to provide custom parameters that can be us
 
 There 2 are types of parameters that asset publishers can support:
 
-* User defined parameters
-* Algorithm custom parameters
+- User defined parameters
+- Algorithm custom parameters
 
 ### Publish a dataset that uses custom parameters
 
@@ -25,8 +25,8 @@ For example, if the publisher has published an URL `https://example.com` which s
 
 Suppose the publisher defines the following 2 parameters:
 
-* `location`: A string indicating region code
-* `type`: A string indicating the type of weather data. It can be temperature/humidity/pressure.
+- `location`: A string indicating region code
+- `type`: A string indicating the type of weather data. It can be temperature/humidity/pressure.
 
 Suppose the buyer wants to download the temperature data in the region code `XYZ`. While downloading the data, the buyer enters the desired parameter values using ocean.py.
 
@@ -63,7 +63,7 @@ def serve_content():
 
 The publisher now must provide the file URL as `https://example.org` while publishing the asset, as shown in the below image.
 
-![](../../.gitbook/assets/compute-to-data-parameters-publish-dataset.png)
+![](../../.gitbook/assets/c2d/compute-to-data-parameters-publish-dataset.png)
 
 For a complete tutorial on publishing asset using Ocean Marketplace read [our guide on publishing with Ocean Market](../../using-ocean-market/marketplace-publish-data-asset.md).
 
@@ -105,7 +105,7 @@ with open(os.path.join(output_dir, "result"), "w") as f:
 
 The publisher now must provide the file URL as `https://example.org` while publishing the algorithm asset, as shown in the below image.
 
-![](../../.gitbook/assets/compute-to-data-parameters-publish-algorithm.png)
+![](../../.gitbook/assets/c2d/compute-to-data-parameters-publish-algorithm.png)
 
 For a complete tutorial on publishing asset using Ocean Marketplace read [our guide on publishing with Ocean Market](../../using-ocean-market/marketplace-publish-data-asset.md).
 
@@ -113,15 +113,16 @@ For a complete tutorial on publishing asset using Ocean Marketplace read [our gu
 
 In this example, the buyer wants to run the algorithm with certain parameters on a selected dataset. The code snippet below shows how the buyer can start the compute job with custom parameter values. Before embarking on this tutorial you should familiarize yourself with how to:
 
-* Search for a dataset using [Ocean market](https://market.oceanprotocol.com/) or [Aquarius API](../../api-references/aquarius-rest-api.md)
-* [Allow an algorithm to run on the dataset](https://github.com/oceanprotocol/ocean.py/blob/6eb068df338abc7376430cc5ba7fe2d381508328/READMEs/c2d-flow.md#5-alice-allows-the-algorithm-for-c2d-for-that-data-asset)
-* Buy datatokens using [Ocean market](https://market.oceanprotocol.com/) or [ocean.py](https://github.com/oceanprotocol/ocean.py)
-* [Set up ocean.py](../using-ocean-libraries/configuration.md)
+- Search for a dataset using [Ocean market](https://market.oceanprotocol.com/) or [Aquarius API](../../api-references/aquarius-rest-api.md)
+- [Allow an algorithm to run on the dataset](https://github.com/oceanprotocol/ocean.py/blob/6eb068df338abc7376430cc5ba7fe2d381508328/READMEs/c2d-flow.md#5-alice-allows-the-algorithm-for-c2d-for-that-data-asset)
+- Buy datatokens using [Ocean market](https://market.oceanprotocol.com/) or [ocean.py](https://github.com/oceanprotocol/ocean.py)
+- [Set up ocean.py](../using-ocean-libraries/configuration.md)
 
 For configuring ocean.py/ocean.js, please refer this [guide](../using-ocean-libraries/configuration.md). Copy the below code snippet to a file locally after completing required configurations and execute the script.
 
 {% tabs %}
 {% tab title="Python" %}
+
 <pre class="language-python" data-title="start_compute.py"><code class="lang-python"># Import dependencies
 from config import web3_wallet, ocean, config, web3_wallet
 from ocean_lib.models.compute_input import ComputeInput
@@ -182,5 +183,6 @@ Execute script
 ```bash
 python start_compute.py
 ```
+
 {% endtab %}
 {% endtabs %}

building-with-ocean/deploying-components/setup-server.md

@@ -18,23 +18,23 @@ Go to [https://www.digitalocean.com/](https://www.digitalocean.com/) and create
 
 Click on **`Create`** button and choose **`Droplets`** options from dropdown.
 
-![](../../.gitbook/assets/image.png)
+![](../../.gitbook/assets/server-setup/image.png)
 
 #### Configure droplet
 
 Select Ubuntu OS and choose a plan. The required CPU, Memory depends on the number of requests Aquarius is expected to serve.
 
-![Configure droplet](<../../.gitbook/assets/image (8).png>)
+![Configure droplet](<../../.gitbook/assets/server-setup/image (8).png>)
 
 Also, select the region where you want Aquarius to be hosted and a root password.
 
 ![](<../../.gitbook/assets/image (10).png>)
 
-![Click Create Droplet](<../../.gitbook/assets/image (7).png>)
+![Click Create Droplet](<../../.gitbook/assets/server-setup/image (7).png>)
 
 Finalize the parameters for the server, click on `Create Droplet.` After the server is ready, select the `Access console` option from the dropdown.
 
-![Click Access Console](<../../.gitbook/assets/image (3).png>)
+![Click Access Console](<../../.gitbook/assets/server-setup/image (3).png>)
 
 ![Click Launch Droplet Console](<../../.gitbook/assets/image (9).png>)
 
@@ -60,5 +60,5 @@ sudo apt-get install docker-compose-plugin
 
 Now that, the server is ready with all the required dependencies are installed for hosting Ocean Components, follow the instructions given in Component specific guide.
 
-* [Deploying Marketplace](deploying-marketplace.md)
-* [Deploying Aquarius](deploying-aquarius.md)
+- [Deploying Marketplace](deploying-marketplace.md)
+- [Deploying Aquarius](deploying-aquarius.md)

using-ocean-market/asset-hosting.md

@@ -35,13 +35,13 @@ If at any point you need more AR tokens, you can fund your wallet from one of Ar
 
 Open [arweave.app](https://arweave.app/) in a browser. Select the '+' icon in the bottom left corner of the screen. Import the JSON key file from step 1.
 
-![Arweave.app import key file](../.gitbook/assets/arweave-1.png)
+![Arweave.app import key file](../.gitbook/assets/arweave/arweave-1.png)
 
 **Step 3 - Upload file**
 
 Select the newly imported wallet by clicking the "blockies" style icon in the top left corner of the screen. Select **Send.** Click the **Data** field and select the file you wish to upload.
 
-![Arweave.app upload file](../.gitbook/assets/arweave-2.png)
+![Arweave.app upload file](../.gitbook/assets/arweave/arweave-2.png)
 
 The fee in AR tokens will be calculated based on the size of the file and displayed near the bottom middle part of the screen. Select **Submit** to submit the transaction.
 
@@ -51,11 +51,11 @@ After submitting the transaction, select **Transactions** and wait until the tra
 
 Once the transaction finalizes, select it, and copy the transaction ID.
 
-![Arweave.app transaction ID](../.gitbook/assets/arweave-3.png)
+![Arweave.app transaction ID](../.gitbook/arweave/assets/arweave-3.png)
 
 **Step 5 - Publish the asset with the transaction ID**
 
-![Ocean Market - Publish with arweave transaction ID](../.gitbook/assets/arweave-4.png)
+![Ocean Market - Publish with arweave transaction ID](../.gitbook/assets/arweave/arweave-4.png)
 
 ## Centralized hosting
 

using-ocean-market/marketplace-download-data-asset.md

@@ -10,7 +10,7 @@ description: Tutorial to download assets using Ocean Market
 2. Search for the data asset. The Ocean Marketplace provides features to search the Data/Algorithms by text, and users can also sort the result by published date.
 3. Connect wallet.
 
-![Connect wallet](../.gitbook/assets/consume-connect-wallet.png)
+![Connect wallet](../.gitbook/assets/consume-assets/consume-connect-wallet.png)
 
 ```
 In this tutorial, we will be using the Polygon Mumbai test network.
@@ -22,22 +22,22 @@ In this tutorial, we will be using the Polygon Mumbai test network.
 
 The buy button is enabled only if the connected wallet address has enough OCEAN tokens to exchange them with 1 datatoken.
 
-![Buy](../.gitbook/assets/consume-1.png)
+![Buy](../.gitbook/assets/consume-assets/consume-1.png)
 
 #### Step 2 - Allow access to OCEAN token(s)
 
-![Transaction 1: Permissions to access OCEAN tokens](../.gitbook/assets/consume-2.png)
+![Transaction 1: Permissions to access OCEAN tokens](../.gitbook/assets/consume-assets/consume-2.png)
 
 #### Step 3 - Buy a datatoken by exchanging it with OCEAN token(s)
 
-![Transaction 2: Buy datatoken](../.gitbook/assets/consume-3.png)
+![Transaction 2: Buy datatoken](../.gitbook/assets/consume-assets/consume-3.png)
 
 #### Step 4 - Click download
 
-![Download asset](../.gitbook/assets/consume-4.png)
+![Download asset](../.gitbook/assets/consume-assets/consume-4.png)
 
 #### Step 5 - Sign message
 
 After signing the message, the file download will start.
 
-![Sign](../.gitbook/assets/consume-5.png)
+![Sign](../.gitbook/assets/consume-assets/consume-5.png)

using-ocean-market/marketplace-publish-data-asset.md

@@ -29,49 +29,57 @@ Fill in the metadata.
 
 _Mandatory fields are marked with \*_
 
-*   **Asset type**\*
+- **Asset type**\*
 
   An asset can be a _dataset_ or an _algorithm_. The asset type cannot be changed after publication.
-*   **Title**\*
+
+- **Title**\*
 
   The descriptive name of the asset. This field is editable after the asset publication.
-*   **Description**\*
+
+- **Description**\*
 
   Description of the asset. Ocean Marketplace supports plain text and Markdown format for the description field. This field is editable after the asset publication.
-*   **Author**\*
+
+- **Author**\*
 
   The author of the asset. The author can be an individual or an organization. This field is editable after the asset publication.
-*   **Tags**
+
+- **Tags**
 
   Tags help the asset to be discoverable. If not provided, the list of tags is empty by default.
 
-![Asset metadata](../.gitbook/assets/publish-1.png)
+![Asset metadata](../.gitbook/assets/publish/publish-1.png)
 
 #### Step 2 - Access details
 
 _Mandatory fields are marked with \*_
 
-*   **Access Type**\*
+- **Access Type**\*
 
   An asset can be a downloadable file or a compute service on which buyers can run their algorithm. Through **download**, buyers will be able to download the dataset. Through **compute**, buyers will be able to use the dataset in a compute-to-data environment.
-*   **Provider URL**\*
+
+- **Provider URL**\*
 
   Provider facilitates the asset download to buyers or for computing jobs and much more.
-*   **File**\*
+
+- **File**\*
 
   The direct URL of the dataset to be published. The file needs to be publicly accessible to be downloadable by buyers. If the file is hosted on services like Google Drive, the URL provided needs to point directly to the data asset file. Also, the file needs to have the proper permissions to be downloaded by anybody.
 
   **Provider** encrypts this field before publishing the asset on-chain.
-*   **Sample file**
+
+- **Sample file**
 
   An optional field through which publishers provide a sample file of the dataset they want to publish. The buyers can access it before buying the dataset. This field is editable after the asset publication.
 
   **Provider** encrypts this field before publishing the asset on-chain.
-*   **Timeout**\*
+
+- **Timeout**\*
 
   This field specifies how long the buyer can access the dataset after the dataset is purchased. This field is editable after the asset publication.
 
-![Access details](../.gitbook/assets/publish-2.png)
+![Access details](../.gitbook/assets/publish/publish-2.png)
 
 #### Step 3 - Pricing
 
@@ -90,24 +98,23 @@ For more information on the pricing models, please refer this [document](../core
 
 For a deep dive into the fee structure, please refer to this [document](../core-concepts/fees.md).
 
-![Asset pricing](../.gitbook/assets/publish-3.png)
+![Asset pricing](../.gitbook/assets/publish/publish-3.png)
 
 #### Step 4 - Preview
 
-![Preview](../.gitbook/assets/publish-4.png)
+![Preview](../.gitbook/assets/publish/publish-4.png)
 
 #### Step 5 - Blockchain transactions
 
-![Transaction 1 - Deploy data NFT and datatoken](../.gitbook/assets/publish-5.png)
+![Transaction 1 - Deploy data NFT and datatoken](../.gitbook/assets/publish/publish-5.png)
 
-
-![Transaction 2 - Deploy data NFT and datatoken](../.gitbook/assets/publish-6.png)
+![Transaction 2 - Deploy data NFT and datatoken](../.gitbook/assets/publish/publish-6.png)
 
 #### Confirmation
 
 Now, the asset is successfully published and available in the Ocean Market.
 
-![Successful publish](../.gitbook/assets/publish-7.png)
+![Successful publish](../.gitbook/assets/publish/publish-7.png)
 
 On the [profile page](https://v4.market.oceanprotocol.com/profile), the publisher has access to all his published assets.
 

using-ocean-market/remove-liquidity-using-etherscan.md

@@ -10,32 +10,32 @@ In previous versions of Ocean liquidity pools and dynamic pricing were supported
 2. Click _View All_ and look for Ocean Pool Token (OPT) transfers. Those transactions always come from the pool contract, which you can click on.
 3. On the pool contract page, go to _Contract_ -> _Read Contract_.
 
-![](<../.gitbook/assets/remove-liquidity-1 (1).png>)
+![](<../.gitbook/assets/liquidity/remove-liquidity-1 (1).png>)
 
 4\. Go to field `20. balanceOf` and insert your ETH address. This will retrieve your pool share token balance in wei.
 
-![](../.gitbook/assets/remove-liquidity-2.png)
+![](../.gitbook/assets/liquidity/remove-liquidity-2.png)
 
 5\. Copy this number as later you will use it as the `poolAmountIn` parameter.
 
 6\. Go to field `55. totalSupply` to get the total amount of pool shares, in wei.
 
-![](../.gitbook/assets/remove-liquidity-3.png)
+![](../.gitbook/assets/liquidity/remove-liquidity-3.png)
 
 7\. Divide the number by 2 to get the maximum of pool shares you can send in one pool exit transaction. If your number retrieved in former step is bigger, you have to send multiple transactions.
 
 8\. Go to _Contract_ -> _Write Contract_ and connect your wallet. Be sure to have your wallet connected to network of the pool.
 
-![](../.gitbook/assets/remove-liquidity-4.png)
+![](../.gitbook/assets/liquidity/remove-liquidity-4.png)
 
 9\. Go to the field `5. exitswapPoolAmountIn`
 
-* For `poolAmountIn` add your pool shares in wei
-* For `minAmountOut` use anything, like `1`
-* Hit _Write_
+- For `poolAmountIn` add your pool shares in wei
+- For `minAmountOut` use anything, like `1`
+- Hit _Write_
 
-![](../.gitbook/assets/remove-liquidity-5.png)
+![](../.gitbook/assets/liquidity/remove-liquidity-5.png)
 
 10\. Confirm transaction in Metamask
 
-![](../.gitbook/assets/remove-liquidity-6.png)
+![](../.gitbook/assets/liquidity/remove-liquidity-6.png)