Optimize image sizes

docs/cloud/index.md

@@ -17,6 +17,7 @@ The documentation will always reference the Public Lobaro instance.
 ![img.png](./img/platform-frontpage.png)
 
 ## Features
+
 * Multi tenant (Organisations) with branding / white labeling
 * IoT Device Management
 * Support for all Lobaro Devices
@@ -25,14 +26,40 @@ The documentation will always reference the Public Lobaro instance.
 * Firmware updates
 * Data parsing and persistence
 * Device protocols:
-  * LoRaWAN Network Server
-  * CoAP
-  * HTTP
-  * Manufacturer specifics
+    * LoRaWAN Network Server
+    * CoAP
+    * HTTP
+    * Manufacturer specifics
 * Connect devices via:
-  * LoRaWAN
-  * NB-IoT
-  * LTE-M
-  * GSM / LTE
-  * etc.
-* APIs to access or forward data to Use-Case specific applications
+    * LoRaWAN
+    * NB-IoT
+    * LTE-M
+    * GSM / LTE
+    * etc.
+* APIs to access or forward data to Use-Case specific applications
+* Scaling to handle thousands of devices
+
+We offer free access to the platform for tests and integrations (up to 12 Month) with the purchase of any Lobaro device
+in our shared instance. In addition we offer private instance hosting or On-Premise (any Server with Root access).
+
+## Overview
+
+![img.png](img/navigation.png)
+
+You can find your organisations name next to the Logo. Admins can change their organisation by clicking the small Icon
+next to it.
+
+* **Devices:** Manage all devices of your organisation.
+* **Data:** See incoming data of all your devices.
+* **Integrations:** Manage data connections to and from other applications. (See: [Integrations](platform/integrations/index.md)).
+* **Organisation:** Manage all organisation related data.
+* **Configuration:** Platform administration of global entities independent of the Organisation (Admins only).
+* **Tools:** wMbus Parser and Hardware Activation.
+
+The platform shows device data received via various data sources like LoRaWAN, NB.IoT, GSM, etc.
+
+The connection to a device in handled by a `Datasource`. Incoming data is mapped to a matching `Device`. Raw data is saved
+as `Uplink` Message. The `Uplink` Message gets processed by a `Parser`. The result of the parser is saved as `Device Data` used
+for visualization inside the dashboard and in outgoing APIs.
+
+![img.png](img/data-pipeline.png)

docs/cloud/platform/integrations/index.md

@@ -0,0 +1,6 @@
+---
+sidebar_position: 0
+displayed_sidebar: cloudSidebar
+---
+
+# Integrations

docusaurus.config.ts

@@ -37,8 +37,8 @@ const config: Config = {
       {
         name: 'assets/images/ideal-img/[name].[hash:hex:7].[width].[ext]',
         quality: 85,
-        max: 1200, // max resized image's size.
-        min: 300, // min resized image's size. if original is lower, use that size.
+        max: 4096, // max resized image's size.
+        min: 1600, // min resized image's size. if original is lower, use that size.
         steps: 4, // the max number of images generated between min and max (inclusive)
         disableInDev: false,
       },