Merge branch 'main' into private_udp

Author: jdries

.gitignore

@@ -15,3 +15,5 @@ venv*
 package-lock.json
 package.json
 node_modules
+
+**/*.quarto_ipynb

_quarto.yml

@@ -21,32 +21,32 @@ website:
 
   sidebar:
     style: "floating"
-    collapse-level: 2
     contents:
       - href: index.qmd
         text: Welcome
       #      - href: eo_service_usage.qmd
-      - text: On-demand EO services
+      - section: On-demand EO services
         contents:
           - href: eo_service_usage/openeo_usage.md
             text: Using openEO service
           - href: propagation/platforms.md
       - href: instantiation/index.md
-        text: Project Environments
+        section: Project Environments
         contents:
           - href: instantiation/usecases.qmd
             text: Use Cases
           - href: instantiation/customisation.md
           - href: instantiation/accessibility.md
           - href: instantiation/geospatial_explorer.md
           - href: instantiation/project_portal.md
-          - href: instantiation/user_workspace.md
-          - href: instantiation/ide.md
+          - href: instantiation/app_code_server.md
+          - href: instantiation/app_jupyterlab.md
+          - href: instantiation/app_qgis.md
           - href: instantiation/catalog.qmd
           - href: instantiation/documentation.qmd
           - href: instantiation/forum.md
       - href: propagation/index.qmd
-        text: Algorithm Support
+        section: Algorithm Support
         contents:
           - href: propagation/ondemandservices.qmd
           - href: propagation/usecases.md
@@ -57,29 +57,55 @@ website:
           - href: propagation/enhancement.md
           - href: propagation/toolboxcloud.md
           - href: propagation/intercomparison.md
-      - text: Guides
+      - section: Guides
         contents:
-          - href: guides/account.md
-          - href: guides/token.md
-            text: Creating APEx single sign-on token
-          - href: guides/udp_writer_guide.qmd
-            text: Creating openEO based services
-          - href: guides/eoap_writer_guide.md
-            text: Creating EOAP based services
-          - href: guides/upscaling_openeo.ipynb
-            text: Upscaling openEO based services
-          - href: guides/stac_catalog_ingest.ipynb
-            text: Ingesting STAC metadata in APEx Product Catalogue
-          - href: guides/catalog_openeo.ipynb
-            text: Linking APEx STAC catalogue with an openEO service
-          - href: guides/file_formats.qmd
-            text: File format recommendations
-          - href: guides/project_portal/index.qmd
+          - section: Developer Guides
             contents:
-              - auto: guides/project_portal/tutorials/*.qmd
+              - section: Authentication
+                contents:
+                  - href: guides/account.md
+                  - href: guides/token.md
+                    text: Creating APEx single sign-on token
+              - section: openEO
+                contents:
+                  - href: guides/udp_writer_guide.qmd
+                    text: Creating openEO based services
+                  - href: guides/upscaling_openeo.ipynb
+                    text: Upscaling openEO based services
+              - section: EOAP
+                contents:
+                  - href: guides/eoap_writer_guide.md
+                    text: Creating EOAP based services
+              - section: APEx Product Catalogue
+                contents:
+                  - href: guides/stac_catalog_ingest.ipynb
+                    text: Ingesting STAC metadata in APEx Product Catalogue
+                  - href: guides/catalog_openeo.ipynb
+                    text: Linking APEx Product Catalogue with an openEO service
+              - section: APEx Algorithm Services Catalogue
+                contents:
+                  - href: guides/algorithm_services_catalogue.qmd
+                  - href: guides/algorithm_services_catalogue_benchmarks.qmd
+              - href: guides/file_formats.qmd
+                text: File format recommendations
+          - section: Admin Guides
+            contents:
+              - href: guides/account.md
+              - href: guides/custom_domain.md
+                text: Custom domains for your project environment
+              - href: guides/geospatial_explorer/index.qmd
+                contents:
+                  - auto: guides/geospatial_explorer/tutorials/*.qmd
+              - href: guides/project_portal/index.qmd
+                contents:
+                  - auto: guides/project_portal/tutorials/*.qmd
+
+          - section: Consumer Guides
+            contents:
+              - href: guides/geospatial_explorer/geospatial_explorer_guide.qmd
 
       - href: interoperability/index.md
-        text: Interoperability and Compliance Guidelines
+        section: Interoperability and Compliance Guidelines
         contents:
           - href: interoperability/definitions.qmd
           - href: propagation/service_development.qmd

eo_service_usage/openeo_usage.md

@@ -2,13 +2,13 @@
 title: openEO based services
 ---
 
-APEx services that follow the [openEO](https://openeo.org/) standard are implemented as openEO processes.
+Context: use of APEx services that expose the [openEO](https://openeo.org/) interface standard, when implemented as openEO processes.
 
 
-Services can be executed through the tools that are provided by the different processing platforms.
-For OpenEO based services, there is an online user interface, web editor, Client Libraries (JavaScript, Python, R) and API.
+In general, services can be executed through the tools that are provided by the APEx supported platforms ("processing platforms" hereafter).
+For OpenEO based services, this is supported by an online user interface, web editor, Client Libraries (JavaScript, Python, R) and API.
 
-There are several ways to discover how a service can be executed. When publishing a service on the APEx, a service provider can choose to provide the following information in the service details:
+There are several ways to discover how a service can be executed. When publishing a service on the APEx Algorithm Services Catalogue, a service provider can choose to provide the following information in the service details:
 
 * An executable link which redirects the user to the user interface of the processing platform. If this is the case, an **Access app** button will appear when opening an EOplaza service.
 * Sample code in the service description on how to execute a service.

guides/algorithm_services_catalogue.qmd

@@ -0,0 +1,20 @@
+---
+title: Registering your service
+jupyter: python3
+execute:
+  echo: false
+---
+
+```{python}
+#| output: asis
+import requests
+url = "https://raw.githubusercontent.com/ESA-APEx/apex_algorithms/main/docs/catalogue.md"
+r = requests.get(url)
+r.raise_for_status()
+
+# Convert images to use absolute URLs
+base_url = "https://raw.githubusercontent.com/ESA-APEx/apex_algorithms/main/docs/"
+content = r.text.replace("](images/", f"]({base_url}images/")
+
+print(content)
+```

guides/algorithm_services_catalogue_benchmarks.qmd

@@ -0,0 +1,20 @@
+---
+title: Creating benchmarks for your service
+jupyter: python3
+execute:
+  echo: false
+---
+
+```{python}
+#| output: asis
+import requests
+url = "https://raw.githubusercontent.com/ESA-APEx/apex_algorithms/main/docs/benchmarking.md"
+r = requests.get(url)
+r.raise_for_status()
+
+# Convert images to use absolute URLs
+base_url = "https://raw.githubusercontent.com/ESA-APEx/apex_algorithms/main/docs/"
+content = r.text.replace("](images/", f"]({base_url}images/")
+
+print(content)
+```