fixup! Update mdBook GitHub deployment, fix API links

Author: zehnm

doc/README.md

@@ -1,13 +1,44 @@
-# Remote Two API Documentation
+# Remote Two/3 API Documentation
 
 - [Remote Two user interface](remote-ui.md)
+- [Remote Two entities](entities/README.md)
 - [Bluetooth HID peripheral support](bt/README.md)
 - [Remote Two DNS-SD lookup](discovery.md)
 
+## Core API
+
+The Unfolded Circle Remote WebSocket & REST Core-APIs allow you to interact with the Unfolded Circle remote-core service
+and take full control of its features.
+
+The focus of the Core-APIs is to provide all functionality for the UI application and the web-configurator.
+The APIs are specialized for certain tasks, but otherwise contain the same functionality and data models.
+
+- The UCR REST Core-API adds:
+    - Custom resource handling for uploading icons, images etc.
+    - Installing custom remote-ui and web-configurator components.
+    - Installing custom integration drivers.
+    - User management and authentication handling.
+- The UCR WS Core-API adds:
+    - Event subscription with asynchronous notifications.
+
+The Core-APIs may also be used by other external systems and integration drivers, if specific configuration or
+interaction features are required, which are not present in the UCR Integration-API.
+
+The API specifications are defined with [OpenAPI](https://swagger.io/specification/) & [AsyncAPI](https://www.asyncapi.com/)
+in YAML format.
+
+- [REST Core-API](https://unfoldedcircle.github.io/core-api/rest/)
+- [WebSocket Core-API](https://unfoldedcircle.github.io/core-api/ws/)
+
 ## Integration API
 
-- [Integration AsyncAPI YAML definition](https://unfoldedcircle.github.io/core-api/integration/)
-- [Remote Two entities](entities/README.md)
+- [Integration AsyncAPI definition](https://unfoldedcircle.github.io/core-api/integration/)
+- View with [AsyncAPI Studio online tool](https://studio.asyncapi.com/?url=https://raw.githubusercontent.com/unfoldedcircle/core-api/main/integration-api/UCR-integration-asyncapi.yaml).  
+  The link will directly load the yaml definition file from GitHub and display it together with the HTML documentation in
+  the browser.
+
+### Integration Driver
+
 - [How to write an integration driver](integration-driver/write-integration-driver.md)
 - [WebSockets handling](integration-driver/websocket.md)
 - [Driver registration](integration-driver/driver-registration.md)

doc/integration-driver/driver-installation.md

@@ -215,7 +215,7 @@ curl --location 'http://$IP/api/intg/install' \
 --form 'file=@"custom-intg.tar.gz"'
 ```
 
-See [REST Core API](../../core-api/rest/README.md) for more details.
+See [REST Core API](https://unfoldedcircle.github.io/core-api/rest/) for more details.
 
 ## Delete driver
 
@@ -225,7 +225,7 @@ These are the same endpoints as for an external network integration driver:
 - Delete integration instance `DELETE /api/intg/instances/:intgId`.
 - Delete driver and installation files: `DELETE /api/intg/drivers/:driverId`.
 
-See [REST Core API](../../core-api/rest/README.md) for more details.
+See [REST Core API](https://unfoldedcircle.github.io/core-api/rest/) for more details.
 
 The instance and driver can also be deleted in the web-configurator.
 
@@ -236,7 +236,7 @@ Output to stdout and stderr are automatically stored with a timestamp and access
 - Get log services: `GET /api/system/logs/services`.
 - Query logs: `GET /api/system/logs?...`.
 
-See [REST Core API](../../core-api/rest/README.md) for more details.
+See [REST Core API](https://unfoldedcircle.github.io/core-api/rest/) for more details.
 
 Log files can also be downloaded in the web-configurator: _Settings, Development: Logs_
 
@@ -249,7 +249,7 @@ near real time.
 
 - URL: `http://$IP/log/`
 - This function is deactivated by default and the endpoint returns 503.
-- The log viewer must be started using the [REST Core API](../../core-api/rest/README.md)
+- The log viewer must be started using the [REST Core API](https://unfoldedcircle.github.io/core-api/rest/)
   with the `/api/system/logs/web` endpoint:
   - `GET` request returns the current state.
   - `PUT` request allows to start, stop or to permanently enable the log app. A password can be set to restrict access