docs: started initial documentation

Author: JanssenBrm

algorithm_catalog/vito/biopar/openeo_udp/README.md

@@ -2,7 +2,7 @@
 
 Calculate various biophysical parameters for an area defined by a polygon. The result is a raster file
 containing the parameter values. A strict CloudMask is applied to avoid cloud contamination.
-                    
+
 The **Leaf Area Index (LAI)** is half the total area of a canopy's green elements 
 per unit of horizontal ground area. The satellite-derived value corresponds to the total green LAI 
 of all the canopy layers, including the understory, which may represent a very significant 

docs/_quarto.yml

@@ -26,6 +26,10 @@ website:
       - href: index.md
         text: Welcome
       - href: benchmarking.md
+      - text: APEx Service Records
+        contents:
+          - href: records/create.md
+          - href: records/visualise.md
 
 format:
   html:

docs/records/create.md

@@ -0,0 +1,24 @@
+---
+title: "Creating APEx Service Records"
+format: html
+---
+Each APEx Service is defined as an OGC API Record, following the [APEx Service - OGC API Record JSON schema](https://github.com/ESA-APEx/apex_algorithms/blob/main/schemas/record.json). This standardized approach ensures consistency across APEx Services, facilitating seamless integration with other tools such as the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/).
+
+## Creating a New OGC API Record
+
+To define a new APEx service as an OGC API Record, follow these steps:
+
+1. Start by creating a new branch for your service.
+
+2. Create the JSON record for your service:
+    * Use the following folder structure: `algorithm_catalog/<organization>/<service_id>/records/<service_id.json>`
+    * Structure your JSON record according to the [APEx Service - OGC API Record JSON schema](https://github.com/ESA-APEx/apex_algorithms/blob/main/schemas/record.json). 
+    * More tips on how you can ensure the proper visualization in the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) are available [here](./visualise.md).
+
+3. Before submission, ensure your record is compliant:
+    * Use an online validator like [JSON Schema Validator](https://www.jsonschemavalidator.net/).
+    * Alternatively, run unit test validation using [test_records.py](../../qa/unittests/tests/test_records.py).
+
+4. Submit your service record:
+   * Once validated, push your changes to your branch and create a GitHub pull request.
+   * After review and a successful GitHub Actions build, the APEx team will merge your pull request, officially integrating your record into the APEx catalog.

docs/records/visualise.md

@@ -0,0 +1,26 @@
+---
+title: "Visualisation of APEx Service Records in APEx Algorithm Services Catalog"
+format: html
+---
+
+Each record from the APEx catalog is visualized in the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/).
+This document provides an overview of how the different components of the service record are translated into catalog's graphical user interface.
+
+## Service Catalog
+
+![APEx Algorithm Services Catalog - Overview](images/catalog.png)
+
+The service catalog provides an overview of all the services. The entries and all of the information are dynamically loaded based on the records inside this repository.
+The following table provides an overview of how the different components are mapped to the visualization.
+
+
+| Component   | Example                        | Record Property          |
+|-------------|--------------------------------|--------------------------|
+| Title       | Best-Available-Pixel Composite | `properties.title`       |
+| Description | A compositing algorithm...     | `properties.description` |
+| Tags        | composite                      | `properties.keywords`    | 
+
+## Service Details Page
+
+
+