Merge pull request #158 from HerveCaumont/separated_app_pages

entries in _quarto.yml file

Author: HerveCaumont

_quarto.yml

@@ -40,8 +40,9 @@ website:
           - 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

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.

propagation/platforms.md

@@ -21,16 +21,18 @@ as identified the following platforms as compliant with the APEx guidelines:
 * [openEO platform](https://openeo.cloud)
 * [CDSE openEO federation](https://documentation.dataspace.copernicus.eu/APIs/openEO/federation/openeo_federation.html)
 
-## OGC Processes/Application Package
+## OGC Earth Observation Application Package (EOAP) processes
 
-To develop and test an OGC Application Package, you can use one of the following environments, which include the necessary
-tools and basic infrastructure to support the development process:
+To develop and test an OGC Earth Observation Application Package, you can use one of the following environments, 
+which include the necessary tools and basic infrastructure to support the development process:
 
 * [ELLIP Studio](https://ellip.terradue.com/)
 * [APEx Code Server IDE](../instantiation/app_code_server.md) 
 * [APEx JupyterLab IDE](../instantiation/app_jupyterlab.md)
 
-To offer your algorithm as an OGC API Process, APEx has identified the following platforms as compliant with the APEx guidelines:
+### OGC API - Processes
+
+To offer your algorithm as an on-demand processing service, exposed via an "OGC API - Processes" standard interface, the following platforms are compliant with the APEx guidelines:
 
 * [Geohazards TEP](https://geohazards-tep.eu/)