Refacto the api.md and downloads.md

docs/components/custom-apps/web-app/dataset/api.md

@@ -25,11 +25,3 @@ Here is an example of the page.
 
 For each service you have the possibility to create a custom reequest (exception for the `SOS` service) and change the options such as the output formats, the projection system or the regions. From that you can copy the custom request, or download the resources that link will give you.
 In the previous example in the picture, I would be able to download the image of the 'arbres d'alignement' dataset from the WMS (Web Map Service).
-
-## Static resources
-
-![Static resources](../../../../assets/webapp/download-resources.png)
-
-## Other resources
-
-![Other resources](../../../../assets/webapp/other-resources.png)

docs/components/custom-apps/web-app/dataset/dataset-detail.md

@@ -9,4 +9,4 @@ It's cut into one to four tabs:
 * [Data tab](./data.md): only if geographical data. It displays the data into a table and a map.
 * [Information](./info.md): always display. It presents the metadata and other important information of the dataset.
 * [Downloads](./downloads.md): a list of files available to download
-* [API](./api.md):
+* [API](./api.md): access to the geographical services available for the dataset
\ No newline at end of file

docs/components/custom-apps/web-app/dataset/downloads.md

 # Downloads
 
-![Information](../../../../assets/webapp/downloads.png)
+## From API
\ No newline at end of file
+
+In the first section, the files are created by using the API.
+
+![Downloads query](../../../../assets/webapp/downloads.png)
+
+For example a PNG file is created by querying the WMS service with specific paramameters. Then the response is converted into a `blob` to allow the browser launch the download.
+
+## Static and other resources
+
+![Downloads other](../../../../assets/webapp/downloads-2.png)
+
+Any other resources like static files (eg a `.csv` or `.tiff`) or an url are listed in two other sections as seen in the figure above.
\ No newline at end of file

docs/components/custom-apps/web-app/dataset/info.md

@@ -7,15 +7,13 @@ This tab shows metadata related to the visited dataset.
 Let us note that metadata:
 
 * are originally filled in by the back-office team via the [GeoNetwork](https://www.geonetwork-opensource.org/) off-the-shelf application;
-* comply to two different templates: 
-* ISO19139 for geographical datasets;
-* Dublin Core for non-geographical datesets;
+* comply to two different templates:
+  * ISO19139 for geographical datasets;
+  * Dublin Core for non-geographical datesets;
 * are indexed in Elasticsearch by a [custom indexer](https://forge.grandlyon.com/web-et-numerique/web-et-numerique-internet/data.grandlyon.com/web-portal/components/indexers/metadata-and-data), in order to enable full-text searches.
 
 This Web Application retrieves metadata from Elasticsearch, by applying a filter on the `slug` field.
 
-*QUESTION: do you confirm that such a filter is the right one?*
-
 ## Parent and children datasets
 
 Between datasets can exist a relationship of parents and children. It usually happens when many datasets share the same metadata, and then are separated in multiple datasets for the data.